Fixed
- The VPA for
external-secretserroneously picks up thekubectlpod created by the CRD installer job and changes the resource requirements for it potentially causing OOM kill for it
Updates on Giant Swarm workload cluster releases, apps, UI improvements and documentation changes.
external-secrets erroneously picks up the kubectl pod created by the CRD installer job and changes the resource requirements for it potentially causing OOM kill for itapp-operator.giantswarm.io/depends-on) to the prometheus-operator-app and agent so they are not installed until the CRD app is deployed.apiserver_request_slo_duration_seconds_bucket metrics from apiserverprometheus-operator-app to 4.0.1 and prometheus-operator-crd to 4.0.0prometheus-agent to 0.3.0 to support chinese registrypromtail-app v1.0.1 disabled by default.capz-app-collection on new release.controller.containerSecurityContext.ingress-nginx.image.ingress-nginx.imageDigest.ingress-nginx.controller.publishServicePath.ingress-nginx.params.isControllerTagValid.extraModules..helmignore.NOTES.txt.controller.kind.controller.labels.controller.annotations.revisionHistoryLimit.controller.podAnnotations.controller.dnsConfig.controller.hostname.controller.dnsPolicy.controller.podLabels.imagePullSecrets.controller.priorityClassName.system-cluster-critical. Please override if required.controller.podSecurityContext & controller.sysctls.controller.shareProcessNamespace.controller.containerName.controller.updateStrategy.controller.publishService.controller.ingressClass.controller.ingressClassResource.name, there are two cases which require manual intervention:controller.ingressClassByName.
Please set controller.ingressClass to the value of controller.ingressClassResource.name if any of these cases applies to you.controller.configMapNamespace.controller.tcp.configMapNamespace.controller.udp.configMapNamespace.controller.scope.namespace.controller.scope.namespaceSelector.controller.reportNodeInternalIp.controller.admissionWebhooks.certificate & controller.admissionWebhooks.key.controller.maxmindLicenseKey.controller.healthCheckHost.controller.healthCheckPath.controller.enableTopologyAwareRouting.controller.extraArgs.serviceAccount.name.controller.containerSecurityContext.controller.hostPort.controller.metrics.portName.tcp & udp ports.controller.customTemplate.controller.extraVolumeMounts.controller.opentelemetry.controller.extraContainers.controller.extraInitContainers.controller.hostNetwork.controller.nodeSelector.controller.tolerations.controller.affinity.DaemonSet option.name to ingress-nginx.name.chart to ingress-nginx.chart.ingress-nginx.fullname.ingress-nginx.controller.fullname.ingress-nginx.controller.electionID.ingress-nginx.defaultBackend.fullname.ingress-nginx.labels.ingress-nginx.selectorLabels.ingress-nginx.defaultBackend.serviceAccountName.Chart.yaml.if. (#434)controller.image.startupProbe.controller.startupProbe.enabled from your overrides and remove/set controller.startupProbe instead.livenessProbe.controller.livenessProbe.enabled from your overrides and remove/set controller.livenessProbe instead.readinessProbe.controller.readinessProbe.enabled from your overrides and remove/set controller.readinessProbe instead.controller.image.tag to v1.6.4.resource.controller-service-internal.name.resource.controller-service.name.controller.extraAnnotations.deployment.controller.annotations instead.controller.extraAnnotations.pod.controller.podAnnotations instead.sysctls setting net.ipv4.ip_local_port_range.controller.sysctls if required.initContainers setting net.core.somaxconn.controller.sysctls if required.controller.maxSurge.controller.updateStrategy instead.controller.maxUnavailable.controller.updateStrategy instead.controller.userID.controller.image.runAsUser instead.controller.groupID.controller.antiAffinityScheduling & controller.nodeAffinity.
NOTE: This is part of our alignment to upstream. Use controller.affinity instead.0.7.0/app version 0.37.2.cert-manager-controller that has permissions needed for the DNS01 challenge via AWS Route53