reinstate ingress-proxy relation for kubernetes-worker
Bug #2066049 reported by
Kevin W Monroe
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Kubernetes Worker Charm |
Fix Released
|
High
|
Adam Dyess | ||
Bug Description
We dropped the http interface from k8s-worker 1.29 (assumed the k-l-b interface on the control plane provided a superset of what was needed); turns out users indeed need it, so let's bring it back for the ck2 maint release.
| Changed in charm-kubernetes-worker: | |
| status: | New → In Progress |
| assignee: | nobody → Adam Dyess (addyess) |
| milestone: | none → 1.29+ck2 |
| importance: | Undecided → High |
Revision history for this message
| Adam Dyess (addyess) wrote | #2 |
Revision history for this message
| Adam Dyess (addyess) wrote | #3 |
Revision history for this message
| Adam Dyess (addyess) wrote | #4 |
| summary: |
- reinstate load balancing relation for k8s-worker + reinstate ingress-proxy relation for k8s-worker |
| summary: |
- reinstate ingress-proxy relation for k8s-worker + reinstate ingress-proxy relation for kubernetes-worker |
| Changed in charm-kubernetes-worker: | |
| status: | In Progress → Fix Committed |
| Changed in charm-kubernetes-worker: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
Merged in https:/