[01:29] <rick_h> pmatulis:  there's a bug on that, lots of debate
[01:30] <rick_h> pmatulis:  https://bugs.launchpad.net/juju/+bug/1832160
[01:30] <mup> Bug #1832160: juju offer doesn't support -m to act on non-current model <juju:New> <https://launchpad.net/bugs/1832160>
[02:08] <pmatulis> rick_h, awesome, thx
[06:52] <hpidcock> kelvinliu: added some comments to https://github.com/juju/juju/pull/10449 looks really good otherwise
[06:55] <kelvinliu> ty4rw,
[11:26] <atdprhs> Hello everyone, I really need some help about https://github.com/jetstack/cert-manager/issues/641#issuecomment-399999436 , i don't know how to do this after conjure-up (which uses juju) kubernetes-core deployment, can anyone help me please?
[11:33] <rick_h> atdprhs:  interesting. I think the folks that work on k8s will have an idea or three. kwmonroe .../me tries to ping others but they're not in channel right now
[11:36] <atdprhs> thanks rick_h , do you know when they usually come online?
[11:37] <atdprhs> I've been stuck on this issue since more than a week tbh, been jumping up and down, scratched my head, pulled my hair, couldn't solve it lol
[11:43] <rick_h> atdprhs:  understand, they're coming online soon. It's US morning and folks are trickling in
[11:44] <atdprhs> Okay rick_h, I'll try to stay online as much as I can, I'm in Australia and it's 09:44 PM here...
[11:46] <rick_h> atdprhs:  ah, understand. We've got some folks that hack on juju that are aussies
[11:46] <atdprhs> really? That'd be nice, I'll stay for another 1 hour, and if noone came online, I'll try to check with the aussies here in the morning
[11:47] <rick_h> atdprhs:  the issue is that we need the k8s folks I think and they're US based
[11:47] <rick_h> atdprhs:  if you want, the best bet might be your morning and try to catch them near EOD
[11:49] <atdprhs> 08:00 AM Sydney is 6:00 PM in Washington, DC
[11:49] <atdprhs> Would that be a good timing?
[11:49] <rick_h> atdprhs:  tight, but maybe
[12:43] <kwmonroe> rick_h: that LE/resolv.conf issue feels really familiar.  i'll poll the team at standup and have something we can relay to atdprhs when they come back online.
[20:11] <hml> fixing annoying intermittent unit test fail, anyone up for a quick review?
[20:12] <hml> https://github.com/juju/juju/pull/10475
[22:52] <atdprhs> Hello everyone, I really need some help about https://github.com/jetstack/cert-manager/issues/641#issuecomment-399999436 , i don't know how to do this after conjure-up (which uses juju) kubernetes-core deployment, can anyone help me please?
[23:43] <timClicks> atdprhs: from memory, you can use "juju scp kubernetes-master/0:config ~/.kube/config", then follow those steps as advertised
[23:54] <atdprhs> timClicks : yes, but how can I run kubeadm
[23:55] <atdprhs> I don't know how to run `kubeadm init --apiserver-cert-extra-sans="mydomainhere.com" --pod-network-cidr="10.244.0.0/16" --service-cidr="10.96.0.0/12" --apiserver-advertise-address="0.0.0.0"`
[23:57] <atdprhs> All of my pods can't communicate with any HTTPs, my cert-manager gets `cert-manager/controller/clusterissuers "msg"="error setting up issuer" "error"="Get https://acme-staging-v02.api.letsencrypt.org/directory: x509: certificate is valid for ingress.local, not acme-staging-v02.api.letsencrypt.org" "resource_kind"="ClusterIssuer" "resource_name"="le
[23:57] <atdprhs> tsencrypt-staging" "resource_namespace"=""` and my other pods are also reporting similar issue like `https://github.com/...: x509: certificate is valid for ingress.local`
[23:57] <atdprhs> but any local https website is okay to go