Added
- Allow users to change the
unhealthyPodEvictionPolicy
of the generated PodDisruptionPolicy. Default isIfHealthyBudget
- Allow users to disable CRD installation Job by setting
kubectlApplyJob.enabled
tofalse
unhealthyPodEvictionPolicy
of the generated PodDisruptionPolicy. Default is IfHealthyBudget
kubectlApplyJob.enabled
to false
v2beta1
.Falco
to upstream version 0.40.0
.secret.firestoreServiceAccountKey
and .secret
.Depending on your current setup, this release may contain breaking changes. We go into these in more detail below and therefore ask you to read them carefully and check whether and to what extent they affect your setup.
controller.progressDeadlineSeconds
.controller.unhealthyPodEvictionPolicy
.controller.metrics.prometheusRule.annotations
.controller.metrics.service.enabled
.defaultBackend.maxUnavailable
.defaultBackend.unhealthyPodEvictionPolicy
.--enable-annotation-validation
CLI flag is already enabled by default in this app since v3.2.0.allow-cross-namespace-resources
ConfigMap option getting deactivated affects you if you are currently referencing resources such as Secrets in Ingress resource annotations from namespaces other than the Ingress resource itself.annotations-risk-level
ConfigMap option getting lowered to High
affects you if you are currently using annotations with an annotation risk level of Critical
. Especially snippet annotations belong to this annotation risk level. So even though you activated snippet annotations via ConfigMap option in the past, you now also need to increase the annotations-risk-level
ConfigMap option back to Critical
.strict-validate-path-type
ConfigMap option is already enabled by default in this app since v3.2.0.image
to global.image
.configmap
.configmap
value is deprecated since v3.0.0. Please use controller.config
instead.giantswarm.io/monitoring_basic_sli
label.coredns
image to 1.12.0.ingressController.admissionWebhook
settings to upstream values. (Enabled by default with failurePolicy: Ignore
)3.8.1.0-debian
ingressController.enabled
)This part of our documentation refers to our vintage product. The content may be not valid anymore for our current product. Please check our new documentation hub for the latest state of our docs.