Allow standard CRD YAML in customResourceDefinition in pod_spec_set
Bug #1821069 reported by
Kenneth Koski
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Fix Released
|
High
|
Ian Booth |
Bug Description
The current implementation of passing in `customResource
Would it be possible to introspect the passed-in YAML and if it looks like regular K8S CRD YAML, just pass it straight through to K8S?
Changed in juju: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
See the CRD YAML here:
https:/ /github. com/juju- solutions/ charm-kubeflow- pytorch- operator/ blob/master/ files/crd- v1beta1. yaml
And what we have to pass to pod_spec_set here:
https:/ /github. com/juju- solutions/ charm-kubeflow- pytorch- operator/ blob/master/ reactive/ kubeflow_ pytorch_ operator. py#L75