1
0
Fork 0
mirror of https://github.com/kyverno/kyverno.git synced 2025-03-06 16:06:56 +00:00
Commit graph

5 commits

Author SHA1 Message Date
Michael Barrientos
b067f41d02
Replace Policy CRD AnyValue fields with empty dict (#1086)
/kind cleanup

\## Proposed change

This implements the same change as #1047, except for the new Policy CRD instead of the ClusterPolicy CRD, which apparently did not get those updates before merging.

When deploying Kyverno using Argo CD, we get a persistent false diff for the Policy custom resource definition (the definition itself, not instances of Policy), because Kubernetes converts the invalid AnyValue: {} property types to just an empty dict {}. Since the Kubernetes server makes this change to {} unilaterally after applying, when a diffing tool like Argo CD compares it against the YAML manifest, each such instance of AnyValue appears as a diff.

I know that since AnyValue is not part of the official OpenAPI V3 schema, and that when you run kubectl get crd policies.kyverno.io -o yaml the status message shows Kubernetes complaining about "Required value: must not be empty for specified object fields" for all of these fields. In theory the correct solution would be to somehow provide a full schema, but I know this can be tricky for these data/anyPattern/patches types, but at the minimum, I would like to get Argo CD to believe that there are no changes that need to be applied.

Since these fields are already silently turned into {} by Kubernetes, this should have no functionality change on existing code/deployments.
2020-08-26 11:11:36 -07:00
shuting
513f5ec898
add watch policy to clusterrole kyverno:customresources (#1084) 2020-08-24 12:27:16 -07:00
Shuting Zhao
1371da939b tag v1.1.10 2020-08-21 11:12:55 -07:00
Michael Barrientos
d2ac5b829b
Replace CRD AnyValue fields with empty dict (#1047) 2020-08-13 11:57:35 -07:00
shuting
0794084b4d
1040 automate release (#1044)
* add release in make

* update release in Makefile

* update README.md
2020-08-12 07:54:45 -07:00