no way to declare a k8s charm with metadata v2 that doesn't need a workload container

[John A Meinel]

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.

[Tom Haddon (mthaddon)]

This will be needed for the nginx-ingress-integrator charm, fwiw.

[Achilleas Anagnostopoulos (achilleasa)]

PR https://github.com/juju/juju/pull/13442 will allow such charms to be deployed.

[Achilleas Anagnostopoulos (achilleasa)]

Note that the PR mentioned above does not actually fix the problem. It simply removes the (client-side) checks that prevent such charms from being deployed. The correct solution is for charm authors to explicitly reference the feature their charm requires in the "assumes" section of the charm metadata.

[Andrew Scribner (ca-scribner)]

Is the "assumes" section planned out somewhere? It sounds like something we've (kubeflow) discussed before as a nice to have and I'm curious if we're thinking of the same thing

[Achilleas Anagnostopoulos (achilleasa)]

You can find the spec for assumes here: https://docs.google.com/document/d/1D4ECIWFBxe_7IZE0q1nkEGE8O2QqmTinKOpx5EL7ReI/edit