Kubernetes Worker charm does not pick up the default proxy settings defined in the model, I.E juju-https-proxy and juju-http-proxy
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Container Runtime Common Layer |
Fix Released
|
Undecided
|
Peter De Sousa | ||
Containerd Subordinate Charm |
Fix Released
|
Low
|
Peter De Sousa | ||
Docker Subordinate Charm |
Fix Released
|
Low
|
Peter De Sousa | ||
Kubernetes Control Plane Charm |
Fix Released
|
Low
|
Peter De Sousa | ||
Kubernetes Worker Charm |
Fix Released
|
Low
|
Peter De Sousa |
Bug Description
Hi all,
The kubernetes-worker charm does not pickup the default proxy settings defined in the model like most charms should now. These options are juju-https-proxy and juju-http-proxy.
The proxy settings in the charm should use the juju values as defaults which we can override if we require. For example, if we have a local registry on-prem which we do not want to access through the proxy, we should be able to override the proxy settings of the kubernetes-worker to disable the http/https proxy for the docker daemon/container run-time.
We encountered an issue recently during a customer deployment where we expected the proxy settings to be set and the containers were not being pulled, so we had to go set these settings.
I hope this is pretty self-explanatory, feel free to ask questions.
Cheers,
- Calvin
Changed in charm-kubernetes-worker: | |
importance: | Undecided → Low |
status: | New → Triaged |
assignee: | nobody → Peter De Sousa (pjds) |
Changed in charm-kubernetes-worker: | |
status: | Triaged → In Progress |
Changed in charm-docker: | |
importance: | Undecided → Low |
Changed in charm-layer-docker: | |
importance: | Undecided → Low |
Changed in charm-containerd: | |
importance: | Undecided → Low |
Changed in charm-docker: | |
assignee: | nobody → Peter De Sousa (pjds) |
Changed in charm-layer-docker: | |
assignee: | nobody → Peter De Sousa (pjds) |
Changed in charm-containerd: | |
assignee: | nobody → Peter De Sousa (pjds) |
Changed in charm-containerd: | |
status: | New → In Progress |
Changed in charm-layer-docker: | |
status: | New → In Progress |
Changed in charm-docker: | |
status: | New → In Progress |
Changed in charm-kubernetes-master: | |
assignee: | nobody → Peter De Sousa (pjds) |
Changed in charm-kubernetes-master: | |
status: | New → In Progress |
Changed in charm-kubernetes-master: | |
importance: | Undecided → Low |
Changed in layer-container-runtime-common: | |
status: | New → In Progress |
assignee: | nobody → Peter De Sousa (pjds) |
Changed in charm-layer-docker: | |
status: | In Progress → Invalid |
status: | Invalid → In Progress |
Changed in layer-container-runtime-common: | |
status: | In Progress → Fix Committed |
Changed in charm-layer-docker: | |
status: | In Progress → Fix Committed |
Changed in charm-containerd: | |
status: | In Progress → Fix Committed |
Changed in charm-layer-docker: | |
status: | Fix Committed → In Progress |
Changed in charm-docker: | |
status: | In Progress → Fix Committed |
Changed in charm-kubernetes-master: | |
status: | In Progress → Fix Committed |
Changed in charm-kubernetes-worker: | |
status: | In Progress → Fix Committed |
Changed in layer-container-runtime-common: | |
milestone: | none → 1.16 |
Changed in charm-containerd: | |
milestone: | none → 1.16 |
Changed in charm-docker: | |
milestone: | none → 1.16 |
Changed in charm-kubernetes-master: | |
milestone: | none → 1.16 |
Changed in charm-kubernetes-worker: | |
milestone: | none → 1.16 |
no longer affects: | charm-layer-docker |
Changed in layer-container-runtime-common: | |
status: | Fix Committed → Fix Released |
Changed in charm-containerd: | |
status: | Fix Committed → Fix Released |
Changed in charm-docker: | |
status: | Fix Committed → Fix Released |
Changed in charm-kubernetes-master: | |
status: | Fix Committed → Fix Released |
Changed in charm-kubernetes-worker: | |
status: | Fix Committed → Fix Released |
FYI this is a low-priority item as it is easy to work around, but it should be fixed long-term.