Releases: kubewarden/helm-charts
kubewarden-controller-0.3.4
A Helm chart for deploying the Kubewarden stack
kubewarden-controller-0.3.3
A Helm chart for deploying the Kubewarden stack
kubewarden-controller-0.3.2
A Helm chart for deploying the Kubewarden stack
kubewarden-crds-0.1.1
A Helm chart for deploying the Kubewarden CRDs
kubewarden-controller-0.3.1
A Helm chart for deploying the Kubewarden stack
kubewarden-crds-0.1.0
What's new?
- Introduce a PolicyServer CRD that allow users to describe a Policy Server Deployment. The configuration of PolicyServer is now done through this resource, instead of using the
policy-serverConfigMap. - ClusterAdmissionPolicy has the following changes:
- A new PolicyStatus field which can be:
unscheduled,unschedulable,pendingoractive - A new condition called PolicyActive.
- A
policyServerattribute. This is used to specify which instance of PolicyServer is going to host the policy. If nothing is specified, the policy will be scheduled on the PolicyServer nameddefault. This one is created by the helm chart at installation time.
- A new PolicyStatus field which can be:
How to upgrade?
Unfortunately helm upgrade is not supported for this release. Uninstall previous kubewarden installation and delete the ClusterAdmissionPolicy CRD:
kubectl delete --all clusteradmissionpolicies.policies.kubewarden.io
helm uninstall --namespace kubewarden kubewarden-controller
kubectl delete namespace kubewarden
kubectl delete crd clusteradmissionpolicies.policies.kubewarden.io Then install kubewarden's new version:
kubectl apply -f https://github.com/jetstack/cert-manager/releases/download/v1.5.3/cert-manager.yaml
helm install --create-namespace -n kubewarden kubewarden-crds kubewarden/kubewarden-crds
helm install --wait -n kubewarden kubewarden-controller kubewarden/kubewarden-controllerkubewarden-controller-0.3.0
What's new?
- Separate helm chart for ClusterAdmissionPolicy and PolicyServer CRDs
- Introduce cert-manager dependency
- PolicyServer and ClusterAdmissionPolicies are now validated and mutated by dedicated admission controllers. The kubewarden-controller is acting as validation endpoint for both of them.
- All the resources created by the operator are now using
Finalizers.
How to upgrade?
Unfortunately helm upgrade is not supported for this release. Uninstall previous kubewarden installation and delete the ClusterAdmissionPolicy CRD:
kubectl delete --all clusteradmissionpolicies.policies.kubewarden.io
helm uninstall --namespace kubewarden kubewarden-controller
kubectl delete namespace kubewarden
kubectl delete crd clusteradmissionpolicies.policies.kubewarden.io Then install kubewarden's new version:
kubectl apply -f https://github.com/jetstack/cert-manager/releases/download/v1.5.3/cert-manager.yaml
helm install --create-namespace -n kubewarden kubewarden-crds kubewarden/kubewarden-crds
helm install --wait -n kubewarden kubewarden-controller kubewarden/kubewarden-controllerkubewarden-controller-0.2.4
kubewarden-controller-0.2.3
Update to the latest release of policy-server.
Starting from this release, Kubewarden can evaluate also Open Policy Agent and Gatekeeper policies.
See https://www.kubewarden.io/blog/2021/09/towards-a-universal-policy-platform/