Support Application CRD in K8s charms

Bug #1892212 reported by Kenneth Koski
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Canonical Juju
Triaged
Low
Unassigned

Bug Description

The Application CRD provides a way to declare metadata about a deployed application in Kubernetes:

https://github.com/kubernetes-sigs/application

An example of an Application custom resource can be found here:

https://github.com/kubernetes-sigs/application/blob/master/docs/examples/wordpress/application.yaml

The existence of this CRD is relied upon for some behavior in the Kubeflow bundle, such as the Central Dashboard knowing which version it is, see here for that logic:

https://github.com/kubeflow/kubeflow/blob/master/components/centraldashboard/app/k8s_service.ts#L156

Could we get support in Juju for automatically creating these? Although they can be created with the `customResources` section of the pod spec, that would require a lot of manual code that seems like something Juju should handle itself. In particular, it seems like a lot of the metadata in an Application could be directly ported over from what's in metadata.yaml.

Ian Booth (wallyworld)
tags: added: k8s
Changed in juju:
importance: Undecided → Wishlist
status: New → Triaged
Revision history for this message
Canonical Juju QA Bot (juju-qa-bot) wrote :

This bug has not been updated in 2 years, so we're marking it Low importance. If you believe this is incorrect, please update the importance.

Changed in juju:
importance: Wishlist → Low
tags: added: expirebugs-bot
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.