PSS + use kustomize from binary not from kubectl #62
Conversation
| seccompProfile: | ||
| type: RuntimeDefault | ||
|
|
||
| containerSecurityContext: |
There was a problem hiding this comment.
Who uses these? Subcharts use global section and their own section like vsphere-csi-driver above.
There was a problem hiding this comment.
also leftover, it was used for install-crd job, so removing. The nameOverride options for individual sub-charts are necessary here btw. because it's used to put correct labels on pods + are used as name of the pods. And kubevip pods (cloud provider, kubevip running as service LB and kubevip running as HA for control-plane) had the same prefix so it wasn't possible to distinguish between them in the polex. These are then re-used here.
| @@ -15,6 +15,28 @@ | |||
| } | |||
| } | |||
| }, | |||
| "crdInstall": { | |||
Signed-off-by: Jirka Kremser <[email protected]>
| @@ -37,3 +41,19 @@ kube-vip-cloud-provider: | |||
| image: | |||
| repository: docker.io/giantswarm/kube-vip-cloud-provider | |||
| tag: "v0.0.4" | |||
| nameOverride: kube-vip-cloud-provider | |||
|
|
|||
| vsphere-csi-driver: | |||
There was a problem hiding this comment.
I wouldn't have this at the root level. I would have it at the subchart level to keep root values clean.
pr w/ exceptions is here: giantswarm/kyverno-app#292
Checklist
values.yamlandvalues.schema.jsonare valid.