| === sparkieg` is now known as sparkiegeek | ||
| === frankban|afk is now known as frankban | ||
| === xnox_ is now known as xnox | ||
| filiplt | Hello! Is it possible to move juju 'units' deployed in LXD containers between machines? | 08:31 |
|---|---|---|
| filiplt | i mean move containers | 08:32 |
| sparkiegeek | well if your units are stateless, it's better to just "juju add-unit --to lxd:<TARGET_MACHINE> <MY_APP>" and "juju destroy-unit <OLD_UNIT>" | 08:36 |
| === Trefex_ is now known as Trefex | ||
| filiplt | Thank you, sparkiegeek. That was solution i thought of | 08:46 |
| === med_ is now known as Guest45512 | ||
| === Guest45512 is now known as med_ | ||
| Budgie^Smore | o/ juju world | 15:04 |
| Zic | hi here | 15:05 |
| rick_h | party | 15:05 |
| Zic | just for info, for one of my 1.5.3 CDK cluster upgrading to 1.6.1, I had a strange issue with kube-dns claiming that its pod cannot mount his volume (kube-dns has a volume??): http://paste.ubuntu.com/24407777/ | 15:06 |
| Zic | don't know if it's normal | 15:06 |
| Zic | http://paste.ubuntu.com/24408100/ | 15:43 |
| Zic | kubernetes-dashboard is also unavailable | 15:43 |
| Zic | (it's a test cluster, no urgence but just to let you know if somebody of the CDK team already saw that kind of problem before submitting a bug) | 15:44 |
| Zic | hmm, seems it's the return of https://github.com/juju-solutions/bundle-canonical-kubernetes/issues/238 | 15:52 |
| === frankban is now known as frankban|afk | ||
| cory_fu | Does anyone know how to change the default bootstrap config options for juju? I managed to get enable-os-update turned off by default and it's preventing me from bootstrapping without manual intervention | 17:19 |
| sparkiegeek | cory_fu: perhaps you set it using "juju model-defaults" ? | 17:22 |
| cory_fu | sparkiegeek: That helps for creating new units inside models, but it requires a controller to already be bootstrapped. I'm trying to influence the default config of the controller during bootstrap. | 17:23 |
| cory_fu | sparkiegeek: I can do it per-bootstrap with `juju bootstrap --config enable-os-update=true` but I'm trying to figure out how I ended up with it defaulting to false | 17:24 |
| cory_fu | Oh, wait | 17:24 |
| cory_fu | Of course. I created an alias that's sending those options. | 17:25 |
| cory_fu | >_< | 17:25 |
| sparkiegeek | haha | 17:25 |
| marcoceppi | cory_fu: wtg ;) | 18:19 |
| === scuttlemonkey is now known as scuttle|afk | ||
| firl | mbruzek you around? | 20:59 |
| mbruzek | Sure | 20:59 |
| firl | I am looking at doing an install of 1.6.1 k8s | 21:00 |
| firl | ontop of openstack, didn’t know the best way you would recommend it. just use the conjure? https://jujucharms.com/canonical-kubernetes/ | 21:00 |
| mbruzek | You only need conjure-up if you want to deploy to LXD. Otherwise just make sure Juju can talk to your OpenStack and you should be good with "juju deploy canonical-kubenernetes". | 21:02 |
| firl | juju 2.0? | 21:02 |
| mbruzek | conjure-up just calls Juju for you. Yep 2.x | 21:02 |
| firl | and does it “just work” with ingress and openstack? | 21:02 |
| mbruzek | Networking is complicated. If you are able to reach your OpenStack VMs without Kubernetes then you should be fine. In my test cases the VMs did not have ingress access. | 21:05 |
| firl | so will I be able to reach my services some how though? | 21:07 |
| lazyPower | firl: so, the way it works is your workers deploy ingress controllers on port 80/443 respectively | 21:07 |
| firl | yes, | 21:07 |
| firl | like juju doesn’t block the ports to prevent me from putting up a ha_proxy for example I mean | 21:08 |
| lazyPower | firl: so long as you have a route to those vm's and you can reach port 80/443, the rest will be handled by the ingress objects you declare with your applications. | 21:08 |
| firl | ok, I just remember juju not exposing those ports | 21:08 |
| lazyPower | firl: correct, you can expose/unexpose the workers respectively, but yeah. | 21:08 |
| firl | so only port 80/443 support right now? | 21:08 |
| lazyPower | firl: what you'll find thats slightly mroe complicated is if you want to use the nodeport networking model | 21:08 |
| lazyPower | right, you'll wind up needing to do a juju run --application kubernetes-worker "open-port 6000" for example | 21:09 |
| lazyPower | thats the only caveat, is you have to manually expose those ports | 21:09 |
| firl | gotcha | 21:09 |
| firl | that’s perfectly acceptable, I just remember the first time I tried 8 months ago I couldn’t get that going | 21:09 |
| firl | is the `juju run --application kubernetes-worker "open-port 6000”` documented anywhere? | 21:09 |
| * lazyPower checks the readme | 21:09 | |
| lazyPower | i'm not positive we documented that | 21:10 |
| lazyPower | yeah, undocumented behavior at the moment firl, but i'll file a bug and get that added for the next release | 21:10 |
| firl | sweet | 21:10 |
| firl | I will go through and see what I can do, I think I have to adjust my environment to accept juju 2.0 first | 21:11 |
| firl | I will report back here if you guys want on how it went | 21:11 |
| lazyPower | sounds good firl, make sure you ping me :) | 21:12 |
| firl | sweet, thanks again as always | 21:12 |
| lazyPower | I monitor #juju but less actively than prior | 21:12 |
| lazyPower | s/prior/previously/ | 21:12 |
| firl | gotcha | 21:13 |
| firl | I can imagine, looks like you guys have been busy with juju as a service too | 21:13 |
| firl | Is the hope to get it integrated with the kubernetes deployments there to kind of make it an easier deployment then the current azure one? | 21:13 |
| lazyPower | firl: i'm not sure i understand the question? | 21:14 |
| firl | https://jujucharms.com/jaas | 21:15 |
| firl | for example the default kubernetes in azure doesn’t allow for scaling post install or attaching to a scaling group etc | 21:15 |
| lazyPower | Juju deployed kubernetes certainly supports both of those cases (however instead of scaling groups, we use an autoscaler or manual scaling) | 21:16 |
| lazyPower | firl: one such autoscaler exists by a community submission. SimonKLB wrote the elastisys autoscaler charm so you get all the autoscaling goodies it brings with it. | 21:17 |
| firl | I will have to check that out. It’s nice to see you guys progressing towards that | 21:17 |
| firl | anyone know where the config data for juju2 is stored locally? | 22:14 |
| blahdeblah | firl: .local/share/juju | 22:15 |
| firl | ty | 22:15 |
| firl | anyone know of a juju 2.0 environment generator for openstack I am having issues specifying the network id | 22:23 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!