no way to declare a k8s charm with metadata v2 that doesn't need a workload container
Bug #1928991 reported by
John A Meinel
This bug affects 4 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Fix Released
|
High
|
Achilleas Anagnostopoulos |
Bug Description
The intent is to add syntax in metadata for "assumes:" that can let us declare that a given charm is still valid for Kubernetes even though it isn't using charms.
Changed in juju: | |
assignee: | nobody → Achilleas Anagnostopoulos (achilleasa) |
Changed in juju: | |
status: | Triaged → In Progress |
Changed in juju: | |
milestone: | 2.9.5 → 2.9.6 |
Changed in juju: | |
milestone: | 2.9.6 → 2.9.7 |
Changed in juju: | |
status: | In Progress → Triaged |
assignee: | Achilleas Anagnostopoulos (achilleasa) → nobody |
Changed in juju: | |
milestone: | 2.9.7 → 2.9.8 |
Changed in juju: | |
milestone: | 2.9.8 → 2.9.9 |
Changed in juju: | |
milestone: | 2.9.9 → 2.9.10 |
Changed in juju: | |
milestone: | 2.9.10 → 2.9.11 |
Changed in juju: | |
milestone: | 2.9.11 → 2.9.12 |
Changed in juju: | |
milestone: | 2.9.12 → 2.9.13 |
Changed in juju: | |
milestone: | 2.9.13 → 2.9.14 |
Changed in juju: | |
milestone: | 2.9.14 → 2.9.15 |
Changed in juju: | |
milestone: | 2.9.15 → 2.9.16 |
Changed in juju: | |
milestone: | 2.9.16 → 2.9.17 |
Changed in juju: | |
status: | Triaged → In Progress |
assignee: | nobody → Achilleas Anagnostopoulos (achilleasa) |
milestone: | 2.9.17 → 2.9-next |
Changed in juju: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
This will be needed for the nginx-ingress- integrator charm, fwiw.