Fix proxy configuration for canonical k8s #331
Conversation
Canonical kubernetes requires the proxy configuration to be set on the juju model. See https://documentation.ubuntu.com/canonical-kubernetes/latest/charm/howto/proxy
| else | ||
| MOD_MSGS[1_proxy.0]='PROXY: Hostname squid.internal resolves, setting juju proxy to http://squid.internal:3128' | ||
| # from https://documentation.ubuntu.com/canonical-kubernetes/latest/charm/howto/proxy | ||
| juju model-config juju-http-proxy=http://squid.internal:3128 juju-https-proxy=http://squid.internal:3128 juju-no-proxy=10.0.0.0/8,192.168.0.0/16,127.0.0.1,10.152.183.0/24 |
There was a problem hiding this comment.
I would re-use the config option for --containerd-no-proxy that I already had, and have a different set of defaults for: --containerd-no-proxy #__OPT__type: (default=127.0.0.1,localhost,::1,10.149.0.0/16,10.0.0.0/8,172.16.0.0/12,192.168.0.0/16)
So would just use ${MOD_PARAMS[CONTAINERD_NO_PROXY]}
Seems 10.152.183.0/24 is the default subnet for Kubernetes in some cases? It should in theory be taken care of by 10.0.0.0/8 however CIDR exclusions in no-proxy are non-standard and juju tries to expand them out a bit and sometimes runs out of space to do so. You may also need to add 10.152.183.0/24 in front of 10.0.0.0/8 in the current no-proxy default.
Please also verify that Canonical K8s works and that you can actually deploy something obvious like COS on top of it. We had issues in the past where the proxy config didn't work for some other things or services in the model.. since this setting is for the entire juju model, we may need to tweak the default no-proxy config a bit more.
2 participants
Canonical kubernetes requires the proxy configuration to be set on the juju model.
See https://documentation.ubuntu.com/canonical-kubernetes/latest/charm/howto/proxy