Add custom namespace monitoring for juju status
Bug #2013371 reported by
Chris Johnston
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Kubernetes Control Plane Charm |
Triaged
|
Wishlist
|
Unassigned | ||
Bug Description
Currently the k-c-p charm will report in `juju status` if there are pods not running in the kube-system namespace. Since different services previously deployed into kube-system by cdk-addons are now being deployed as workloads via charms they are now in a different namespace. It would be nice if I was able to specify a list of namespaces to k-c-p and see if there are any expected pods missing via juju status rather than having to do a juju status across multiple models to find out the status of everything.
Revision history for this message
| Kevin W Monroe (kwmonroe) wrote | #1 |
| Changed in charm-kubernetes-master: | |
| status: | New → Triaged |
| milestone: | none → 1.27+ck1 |
| Changed in charm-kubernetes-master: | |
| milestone: | 1.27+ck1 → 1.28 |
| Changed in charm-kubernetes-master: | |
| milestone: | 1.28 → 1.28+ck1 |
| Changed in charm-kubernetes-master: | |
| importance: | Undecided → Wishlist |
| milestone: | 1.28+ck1 → 1.29 |
To post a comment you must log in.
This is timely as a counter feature recently went in with bug 2015366. That allows an admin to ignore certain pods, whereas here we want to ensure them. We should figure out a good UX to handle both flows. Targeting the next maintenance release for now.