Deploy policies as an app #6
Conversation
* Try skipping lint via orb * Trigger CI * Add silly ClusterAnimal policy to test deployment * Bump orb version, remove test policy
| @@ -0,0 +1,6 @@ | |||
| apiVersion: v1 | |||
| name: policies-common | |||
There was a problem hiding this comment.
Do we need to prefix everything with policies? Especially for folders it seems redundant as the repo is already called clusterpolicies
There was a problem hiding this comment.
In places where the name is actually used I think it will make more sense. Like with opsctl it would currently be opsctl deploy -i <whatever> policies-kvm. I tried to keep this similar to the releases structure
There was a problem hiding this comment.
I understand that - but the folders in releases also don't have a prefix. Maybe I am missing something.
There was a problem hiding this comment.
The folders for the actual helm charts do https://github.com/giantswarm/releases/tree/master/helm
The outer folders are kustomized in, which we can't do with ClusterPolicy CRs because it alphabetizes things and re-quotes strings which break kyverno
Separates policies into
common,aws,azure,kvm, andvmwareconcerns and pushes the charts to the cp test catalog.After https://github.com/giantswarm/opsctl/pull/1109 we can deploy these with
opsctl.release-operatorbehavior is still in progress