1
0
Fork 0
mirror of https://github.com/kyverno/kyverno.git synced 2025-03-09 09:26:54 +00:00
Commit graph

15 commits

Author SHA1 Message Date
Shuting Zhao
36c549ea22 Merge branch 'master' into policyreport
# Conflicts:
#	charts/kyverno/values.yaml
2020-10-22 20:35:22 -07:00
Shuting Zhao
af07e66ede - tag v1.2.1; - update liveness, readiness port in Helm chart 2020-10-22 13:07:48 -07:00
Jim Bugwadia
022c227bce update pod security context and ports 2020-10-22 11:26:22 -07:00
Shuting Zhao
6b5e935e49 Merge branch 'feature/reports-cli' of https://github.com/evalsocket/kyverno into policyreport
# Conflicts:
#	Makefile
#	cmd/kyverno/main.go
#	go.mod
#	go.sum
#	pkg/client/clientset/versioned/clientset.go
#	pkg/client/clientset/versioned/fake/clientset_generated.go
#	pkg/client/clientset/versioned/fake/register.go
#	pkg/client/clientset/versioned/scheme/register.go
#	pkg/client/informers/externalversions/factory.go
#	pkg/client/informers/externalversions/generic.go
#	pkg/client/listers/kyverno/v1/expansion_generated.go
#	pkg/policy/common.go
#	pkg/policy/controller.go
#	pkg/policy/existing.go
#	pkg/policyviolation/builder.go
#	pkg/policyviolation/generator.go
#	pkg/webhooks/server.go
#	pkg/webhooks/validate_audit.go
#	pkg/webhooks/validation.go
2020-10-12 18:30:37 -07:00
Shuting Zhao
49c61a574a tag v1.2.0 2020-10-07 15:44:15 -07:00
Shuting Zhao
fe20f3aa4c tag 1.1.12 2020-09-18 12:57:38 -07:00
evalsocket
6a0a5132b5 resolve conflict 2020-09-11 05:16:31 -07:00
Shuting Zhao
c7adf66fda tag 1.1.11 2020-09-08 11:53:49 -07:00
Yuvraj
e43154ea1c merge conflict resolve 2020-09-02 14:17:33 +05:30
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
Yuvraj
251521a77a policy report added 2020-08-26 18:50:38 +05:30
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