Juju should handle setting Kubernetes properties with manual charm support
Bug #1907709 reported by
Kenneth Koski
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical Juju |
Triaged
|
Low
|
Unassigned | ||
Bug Description
Coming from this feature request for a K8s charm:
https:/
The ask there is for the charm to support these options:
podSecurity
enabled: true
useAppArmor: true
It doesn't really seem like charms should be involved in this, unless the charm author explicitly wants to get involved. In other words, it seems proper for Juju to support something along the lines of:
juju config cert-manager-
Perhaps the charm author could provide a default value if desired, but this seems like something that's going to highly depend on one's Kubernetes setup and security requirements.
| tags: | added: bitesize |
| Changed in juju: | |
| milestone: | none → 2.8.8 |
| importance: | Undecided → High |
| status: | New → Triaged |
| Changed in juju: | |
| milestone: | 2.8.8 → 2.8.9 |
| Changed in juju: | |
| milestone: | 2.8.9 → 2.8.10 |
| Changed in juju: | |
| milestone: | 2.8.10 → 2.8.11 |
| Changed in juju: | |
| milestone: | 2.8.11 → none |
| importance: | High → Medium |
Revision history for this message
| Canonical Juju QA Bot (juju-qa-bot) wrote | #1 |
| Changed in juju: | |
| importance: | Medium → Low |
| tags: | added: expirebugs-bot |
To post a comment you must log in.
This Medium-priority bug has not been updated in 60 days, so we're marking it Low importance. If you believe this is incorrect, please update the importance.