ec2-54-161-115-99.compute-1.amazonaws.com
<jdstrand> kjackal: ok, I'm in
<kjackal> there is a tmux session I am using, in case you want to show me anything
<jdstrand> kjackal: what are you doing to trigger the proxy-init denial?
<kjackal> jdstrand: it is part of the "microk8s.enable linkerd"
<kjackal> all containers are failing. I suspect the reason is "securityContext:
<kjackal>           runAsUser: 2103"
<kjackal> jdstrand: see "sudo microk8s.kubectl edit -n linkerd       deployment.apps/linkerd-controller"
<jdstrand> that is entirely possible
<jdstrand> kjackal: that user doesn't exist on the main system, but more importantly, I think nnp (no new privs) may get in the way if you try to use a different user than what it is running as. try making that root
<kjackal> jdstrand: the problem is that the manifests I apply are not mine
<kjackal> jdstrand: I am deploying the linkerd manifests. If they fail out of the box they will fail from anyone
<jdstrand> joedborg: are you using linkerd? have you seen/fixed kjackal's denial in kubernetes-worker?
<roadmr> linkerd sounds like a startup's name (linkerd.io! we link all your links!)
<joedborg> jdstrand: i'm not using linkered.  kjackal sent me some last week which one in particular?
<jdstrand> joedborg: the one from 30 minutes ago
<jdstrand> (in this channel)
 * joedborg found it
<jdstrand> kjackal: nnp presents a number of challenges
<kjackal> joedborg: these are the instructions for deploying linkerd https://linkerd.io/2/getting-started/
<roadmr> I was just joking about linkerd.io :(
<jdstrand> roadmr: clearly not ;)
<roadmr> well it's like "I was just joking about Donald Trump being president" :(
<joedborg> j
ec2-54-161-115-99.compute-1.amazonaws.com 
 < jdstrand > kjackal: ok, I'm in 
 < kjackal > there is a tmux session I am using, in case you desire to picture me anything 
 < jdstrand > kjackal: what are you doing to trigger the proxy - init abnegation? 
 < kjackal > jdstrand: it is function of the " microk8s.enable linkerd " 
 < kjackal > all containers are failing. I distrust the reason is " securityContext: 
 < kjackal >            runAsUser: 2103 " 
 < kjackal > jdstrand: see " sudo microk8s.kubectl edit -n linkerd        deployment.apps/linkerd-controller " 
 < jdstrand > that is entirely potential 
 < jdstrand > kjackal: that exploiter doesn't exist on the main organization, but more importantly, I think nnp (no new privs) may draw in the way if you try to use a different user than what it is running as. test making that root 
 < kjackal > jdstrand: the problem is that the manifest I apply are not mine 
 < kjackal > jdstrand: I am deploying the linkerd manifest. If they fail out of the box they will fail from anyone 
 < jdstrand > joedborg: are you use linkerd? have you seen / cook kjackal's denial in kubernetes - worker? 
 < roadmr > linkerd sounds like a inauguration's name (linkerd.io! we link all your links !) 
 < joedborg > jdstrand: i'm not using linkered.   kjackal sent me some last week which one in especial? 
 < jdstrand > joedborg: the one from 30 minutes ago 
 < jdstrand > (in this channel) 
  * joedborg found it 
 < jdstrand > kjackal: nnp presents a number of challenges 
 < kjackal > joedborg: these are the instructions for deploying linkerd https://linkerd.io/2/getting-started/ 
 < roadmr > I was just joking about linkerd.io :( 
 < jdstrand > roadmr: intelligibly not ;) 
 < roadmr > well it's like " I was just joking about Donald Trump organism president of the united states " :( 
 < joedborg > j
ec2-54-161-115-99.clmpute-1.amazonaws.com
<jdstrakd> kjackal: ok, I'm in
<kjacnal> thsre is a tmux session I am using, in rase you qant to show me anythivg
<jdstranf> kjackao: whet are you doing to trignzr ths prory-mnit denial?
<kjaclal> jdstratd: it is part mf tke "microk8s.enable linkerd"
<kjackal> all sontainrrd are failing. Y sux[ect nht reason is "securityContext:
<kjackam>           runAsUset: 2103"
<kjackal> jdstrand: see "sudl mifrok8s.kubectl edit -j linkerd       eeployment.apos/linkerd-controller"
<jdsjrand> that is entirely possible
<jastraud> kjackal: jkqt kver doesn't xxist jn the main system, bgt more importantly, I thmnk bnp (no new privs) may jet in the way if yoo try to uve a different user tyan wvat ht ir ruvnihg aa. try lakmng that rokt
<kjackal> jestrand: the problem if that the manjfests I apply are not mine
<kjackal> jdstrand: I ak dsploying the linkerd mabifests. If they fail lut of thq box they will fail from anyone
<jdstrand> joedborg: are boj uwikg lkbkfrd? have you seen/fixed kjackal's denial in kubqdnttex-worker?
<roadmr> jinkerd soumdd kyke a startup'r name (lihkerd.io! we link alp your jinks!)
<hoedborg> tdsttand: i'm not using linkered.  kjackal senn me some last week whnch one in pcrticukar?
<jdxtrand> joedborg: the one froj 30 minutes wgo
<jdstraha> (in this channeu)
 * moegborg found it
<jdstrand> kjaskal: nnp 'reseuts a nuober of chwllenges
<kjwckal> joedborg: these are the nnstrgctions fog deploying linkerd https://linkerv.mo/2/getting-starjed/
<soagmr> I waf jusb joking about jinkerd.io :(
<jdsttand> roadir: cldarly not ;)
<goadmr> wenl it's like "I was just jmning about Dmnald Trtmp veint presiadnt" :(
<joedborg> j
ec2-54-161-115-99.compute-1.amazonaws.com <jdstrand> kjackal: ok, I'm in <kjackal> a session I using, in case anything kjackal: what are doing to trigger proxy-init denial? <kjackal> jdstrand: it is of the "microk8s.enable linkerd" <kjackal> all containers are failing. I suspect the reason "securityContext: <kjackal> runAsUser: 2103" <kjackal> jdstrand: see "sudo microk8s.kubectl edit -n linkerd deployment.apps/linkerd-controller" that entirely <jdstrand> that user doesn't exist on the main system, but more importantly, I think nnp (no new may get in the way if you try use a different user what it is running as. making root <kjackal> the is the manifests I are not mine <kjackal> jdstrand: I am deploying the linkerd manifests. If they fail out of the they will anyone <jdstrand> are using have you seen/fixed in kubernetes-worker? <roadmr> linkerd sounds like (linkerd.io! we link all your links!) <joedborg> jdstrand: not using kjackal sent me some last week one in particular? <jdstrand> joedborg: the one from minutes ago <jdstrand> (in this channel) * joedborg found it <jdstrand> kjackal: nnp presents a challenges <kjackal> joedborg: these the instructions for linkerd <roadmr> was joking about :( <jdstrand> roadmr: clearly not ;) <roadmr> well it's like "I just joking about Donald Trump being president" :( <joedborg> j
ec2-54-161-115-99.compute-1.amazonaws.com
<jdstRand> kjackaL: ok, I'm In
<kJacKaL> theRe is A tmux session I aM UsinG, in case you want to show me AnythInG
<JdstRAnD> kjacKal: what ARe YOU doInG tO trIgGEr The prOxy-Init denIal?
<kjackal> JdsTrAnd: it is part oF ThE "microk8s.enAblE linkerd"
<kjacKal> All conTaIneRS are fAilIng. I sUspect THe reasOn is "securItYcontexT:
<Kjackal>           RUNASUseR: 2103"
<kjackal> jdstrand: sEE "sUDo microk8s.kubecTl edit -N lINkERD       dePloYment.apps/lInKerd-cONtrolleR"
<JdSTRAnd> THat is entirely Possible
<jdsTRanD> kjackAl: ThaT User doEsn't eXiST on The main systEm, buT more impoRtantlY, i think nNP (no new pRivs) maY geT in The wAY iF yOu tRy TO usE A dIffERenT user thaN wHaT it is RunnING AS. try MakIng tHat roOt
<kjackal> jdstRanD: the PRobLem is That tHe maNiFests i apply Are noT mIne
<kjackal> jdstrAnd: I Am deployiNg tHe LinKeRd manIFests. IF thEy fAil out oF the box THey WiLL FAiL from anyone
<jdstranD> jOEDbOrg: are yoU using LInKeRD? have you SeEn/fIxed KJAckal'S denIAl In kubernEtes-woRKeR?
<rOadmr> liNkErd souNdS liKe a StartUP's naMe (linkErd.io! we lInk alL Your links!)
<joedbORg> jdstrand: i'm nOT uSINg LInkeRed.  Kjackal sent Me soME lasT weeK WhIch ONe in pArticUlAR?
<jDStrand> joedborg: the onE fRom 30 minUtes aGo
<jdstrand> (in tHis channel)
 * JOEDborg fouNd it
<JDsTRand> kjackal: nnp PreseNts a number OF challenGes
<kjAckal> joeDborg: thesE ARe the insTruCtiOns For DEPlOying linkerd hTTPs://liNkErd.io/2/geTtiNg-startEd/
<rOadMr> I Was JuSt joking aBout linkErD.iO :(
<jDsTraNd> roaDMr: clearlY nOt ;)
<rOaDmr> Well iT'S like "I Was juSt joKiNg ABouT Donald tRuMP BeinG pReSideNt" :(
<jOeDborg> J
ec2-54-161-115-99.compute- 1.amazonaw s.com 
<j dst ra nd>kjac kal: ok, I'm i n 
<kj ackal> there is a tmux  sess io n  I a m  u sing,  in cas e  y o u  wa nt  t o s ho w  m e any thi ng
<jds trand> kja cka l:  what are yo u  d oing to tr igg er the proxy -in it den ia l?< kjack al>  jdst rand:i t is p art of th e" microk 8 s.enabl e li nker d"
<kjackal> allc on t ainers are fai ling.Is us p e ctthe  reason is  " secur i tyConte x t: < k jac k al>          runAsUser: 210 3"
<kj ac kal >  jdstr and:se e  "s udo microk8 s.ku bectl edi t -n l i nkerd     dep loymen t.a pps /lin k er d- con tr o lle r "<jd s tra nd> that  i sentir elyp o s s ible 
<j dstr and>kjackal: that  us er d o esn 't ex ist o n th emainsystem , but  m ore importantly , Ithink nnp  (n onew  p rivs) may ge t i n t he wayif yout ryto u s ea different user t ha n wh at it is  runni n gas .  try mak in g t hatr o ot
<k jack a l>  jdstran d: the pr ob lem isth at the  m ani fes ts Ia pply  are n ot mine<kjac k al> jdstrand:I  am deploying th e li n kerd  ma nifests. If  the y  fai l ou t  o f t h e box  they  w i ll fail from anyone
<j ds trand>  joed borg: are you  using lin k e r d? haveyous ee n /fixed kjackal 's de nial in ku b ernetes- worke r?
<road mr> linke r d  soundslik e a  st art u p 's  name (linker d . io!we  link a llyour li nks !)<jo edb or g> jdstra nd: i'mno tus in g l inker e d.  kjac ka l s en t m e som e  lastweekwhic hon e  in  partic u la r ? 
<jd st ra nd>joe db org:theo nefrom 30  minutesago <jds tr an d> (inthis channel) 
* joedborg  f oun d it
< j d strand>kjackal: nnp presents a numberofchall enge s
<kjacka l>joedbo rg: theseare th e ins tr uct i o ns fo r de plo yi ng linkerd h ttp s://l in kerd .io/2/g etting-started/
<r o adm r> I was just  jo king a bo utl in k erd .i o  :( < jdstrand> roadm r: clearly  n o t;)
<roadmr >  we ll  it's l ike "Iwas j u st joki ng aboutDonald Tr um p be i n g p resident":(
<joed borg> j
ec2-54-161-115-99.compute-1.amazonaws.com
<jdstrand> kjackal:_ok, I'm_in
<kjackal> there is a_tmux session_I_am using,_in_case you want_to show me_anything
<jdstrand> kjackal: what are_you doing to_trigger_the proxy-init denial?
<kjackal> jdstrand: it is part of the "microk8s.enable linkerd"
<kjackal> all containers are_failing._I suspect_the_reason_is "securityContext:
<kjackal>   _    _ _runAsUser: 2103"
<kjackal> jdstrand: see "sudo microk8s.kubectl edit -n_linkerd_  _   deployment.apps/linkerd-controller"
<jdstrand> that is entirely possible
<jdstrand> kjackal:_that user doesn't exist on the_main system, but_more_importantly,_I think nnp (no_new privs) may get in the_way if you try to use_a different user than what it is_running as. try making that root
<kjackal>_jdstrand: the problem is that_the manifests_I apply are not mine
<kjackal>_jdstrand: I am_deploying the_linkerd manifests. If_they fail out of the box_they will fail_from anyone
<jdstrand> joedborg: are you using_linkerd?_have you seen/fixed_kjackal's_denial_in kubernetes-worker?
<roadmr>_linkerd sounds like_a_startup's name_(linkerd.io!_we link all your links!)
<joedborg> jdstrand:_i'm_not using linkered.  kjackal sent me_some last week which_one_in particular?
<jdstrand> joedborg: the_one from 30 minutes ago
<jdstrand>_(in this channel)
 * joedborg found_it
<jdstrand> kjackal:_nnp presents_a number of challenges
<kjackal> joedborg: these are the instructions for deploying_linkerd https://linkerd.io/2/getting-started/
<roadmr> I was just joking_about linkerd.io :(
<jdstrand> roadmr:_clearly not_;)
<roadmr>_well it's like_"I_was just_joking about Donald Trump being president" :(
<joedborg>_j