=== frankban|afk is now known as frankban [17:22] hi guys , im trying to deploy the canonical distro of kubernetes in an offline enviorment , currently im stuck with deploying kube-proxy snaps , i tried manually downloading and attaching the snaps to the kubernetes-worker resource but they serivces fails to start === frankban is now known as frankban|afk [17:51] assaf: Hey, I can try to help you with that. Can we start with which snaps you downloaded and attached? [17:52] assaf: I'd also like to refer you to this documentation: https://github.com/juju-solutions/bundle-canonical-kubernetes/wiki/Running-CDK-in-a-restricted-environment [17:54] assaf: In particular, you may find the cdk-shrinkwrap tool helpful in your case. [18:43] Is it possible to use juju to deploy windows 10 using Maas? [20:04] hi [20:04] is posible remove ceph from openstack juju charm? [20:04] and where the charms are stored? [20:04] to perform a modification? [21:18] stokachu:ping [21:19] ryebot: ping [21:20] jamesbenson: Something I can help with? [21:21] ryebot: I was wondering if you could provide some input on canonical k8s deploy [21:22] jamesbenson: Yes, definitely [21:22] ryebot: It's completed (I think) the conjure up, all services are active, and in juju status everything is active and idle, however, the conjure up window hasn't gone away yet... I thought there was post conjure things that happened. [21:22] ryebot: I can send screen shots if you want [21:23] ryebot: In conjure-up it has a "Setting relationship kubeapi-load-balancer:apiserver <-> kuberneters-master:kube-api-endpoint" [21:24] ryebot: But has been there for a while now.... 1+ hr. [21:24] alright [21:24] * ryebot thinks [21:25] jamesbenson: can you open up another terminal and take a look at `juju status` [21:26] ryebot : yeah, I'm actively looking at that as well [21:27] jamesbenson: okay great, can you send me a pastebin of that? [21:27] http://paste.ubuntu.com/26060543/ [21:27] perfect, one sec [21:28] jamesbenson: it appears that everything has deployed successfully. [21:28] jamesbenson: There may have been a hiccup in the conjureup output, but that looks good to me. [21:29] https://snag.gy/liuxHj.jpg [21:29] ryebot: so where do I go from here then? === petevg_afk is now known as petevg [21:29] ryebot : kubectl get nodes [21:30] jamesbenson: yeah, you can log into one of the boxes and go to town with kubectl [21:31] jamesbenson: or copy out the kubeconfig and use kubectl locally [21:31] ryebot : do you have a command for that? which node is it in? [21:32] jamesbenson: all workers and masters will have a copy [21:32] okay [21:32] `juju ssh kubernetes-master/0` [21:32] yep, found the config file [21:32] copied it locally [21:36] ryebot: having issues the command: kubectl --kubeconfig=~/.kube/config (I made the dir & copied the config file here). The command isn't valid it seems... [21:37] jamesbenson: do you have kubectl in your path? [21:37] ie can you kubectl --help ? [21:37] yes [21:38] http://paste.ubuntu.com/26060596/ [21:39] ryebot: that's the output when I issue the kubeconfig command above. [21:39] jamesbenson: oh, it may not expand ~ [21:39] jamesbenson: try it with the absolute path [21:39] ok [21:40] ryebot: same issue [21:41] ubuntu@k8s:~/.kube$ kubectl --kubeconfig=/home/ubuntu/.kube/config |pastebinit [21:41] http://paste.ubuntu.com/26060615/ [21:42] jamesbenson: alright hmm [21:42] can I safely kill the conjure-up screen? [21:43] ryebot: I actually deployed twice on two different machines... both are stuck on the conjure up screen with different status' but same juju status, active/idle [21:43] ryebot: The other machine says it's stuck at "Setting relation easyrsa:client <-> kubernetes-master:certificates [21:43] " [21:45] jamesbenson: I -think- so, but am not entirely sure - maybe stokachu can weigh in [21:45] https://snag.gy/rUToJM.jpg [21:45] jamesbenson: oh, I'm being silly - you'll need to tack a command onto that [21:45] ? [21:45] jamesbenson: so, `kubectl --kubeconfig=... get po` [21:45] ok [21:45] relations are there [21:45] you can kill conjure-up [21:45] stokachu: thanks :) [21:46] ah yeah, get nodes worked [21:46] cory_fu: ^ i see this on internal testing ci as well, where the deployment in conjure-up will stop at setting relations [21:47] is there a way to set the config so I dont' always have to include that? [21:47] ah, I guess when I moved it into that dir, it did it... [21:47] i think there is an environment var [21:47] kubectl get nodes works now without issue. [21:48] we also want to do some magic later on to merge the configs and have you switch by context [21:48] just not done yet [21:48] sweet, I'm still pretty new to k8s, so learning a lot. [21:48] thank you stokachu and ryebot [21:48] np [21:48] jamesbenson: hit us up in #conjure-up if you have any more specific questiosn around that [21:48] out of curiousity, where are you guys based out of? I'm always curious how ^_^ [21:49] stokachu: conjure-up stops, but the relations exist? That sounds like the AllWatcher not seeing the relations come through. Not sure if that we could handle that in libjuju in a reasonable way. Maybe a timeout after which it re-inspects the complete model status? [21:49] Seems heavy-handed [21:49] We've already [21:49] cory_fu: yea, it's why majority of the auto ci runs fail [21:49] *gotten complaints about pulling in the full model state on connect [21:49] jamesbenson: im EST [21:49] "complaints" [21:49] comments [21:49] "suggestions" [21:50] stokachuL nice I used to be in NY, now in Tx === admcleod_ is now known as admcleod