Releases: kubewarden/kubewarden-controller
Releases · kubewarden/kubewarden-controller
Release v0.4.4
Update CHANGELOG.md
Release v0.4.3
Update CHANGELOG.md
Release v0.4.2
Update CHANGELOG.md
Release v0.4.1
v0.4.1
Release v0.4.0
Features
- 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 thepolicy-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:
- 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.
Release v0.3.2
Update CHANGELOG.md
Release v0.3.1
This release includes a correct aarch64 controller binary in the published container images on the GitHub registry.
Release v0.3.0
This version has removed support of v1alpha1 ClusterAdmissionPolicy custom resource. You should migrate to v1alpha2 before upgrading to this version.
Release v0.2.3
Update CHANGELOG.md
Release v0.2.2
Update CHANGELOG.md