1. Docs
  2. Changes and releases
  3. Connectivity

Connectivity

  • Connectivity kong-app v5.0.0

    We’re going back to installing the kong OSS version by default instead of enterprise. In case you’re relying on this default behaviour, please make sure to set the .Values.image.repository, .Values.image.tag, .Values.enterprise.enabled and .Values.enterprise.license_secret values to the respective Enterprise values. These changes were introduced in PRs #378 and #379. This release drops support for Kubernetes below v1.26.

    Added

    • Allow chart users to specify the version of the CRDs to match the kong ingress controller version by changing .Values.kubectlApplyJob.files to any other file in helm/kong-app/crds/ folder. The default is crds/custom-resource-definitions-v3.4.3.yaml.

    Changed

  • Connectivity coredns-app v1.25.0

    Changed

    • Update coredns image to 1.12.1.
  • Connectivity ingress-nginx-app v3.9.5

    Changed

    • Chart: Sync to upstream. (#789)
      • Controller: Update image to v1.11.5.
      • Kube Webhook CertGen: Update image to v1.5.2.
  • Connectivity ingress-nginx-app v4.0.0

    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.

    Added

    • Chart: Sync to upstream. (#768https://github.com/giantswarm/ingress-nginx-app/pull/768)
      • Deployment: Add controller.progressDeadlineSeconds.
      • Pod Disruption Budget: Add controller.unhealthyPodEvictionPolicy.
      • Prometheus Rule: Add controller.metrics.prometheusRule.annotations.
      • Metrics Service: Add controller.metrics.service.enabled.
      • Default Backend: Add defaultBackend.maxUnavailable.
      • Default Backend: Add defaultBackend.unhealthyPodEvictionPolicy.

    Changed

    • Chart: Sync to upstream. (#768https://github.com/giantswarm/ingress-nginx-app/pull/768)
      • Controller: Update image to v1.12.0.
        NOTE: Please read the upstream changelog carefully, especially the entries marked with ⚠️. In addition, the following should be noted:
        • The --enable-annotation-validation CLI flag is already enabled by default in this app since v3.2.0.
        • The 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.
        • The 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.
        • The strict-validate-path-type ConfigMap option is already enabled by default in this app since v3.2.0.
      • Values: Rename image to global.image.
    • Chart: Sync to upstream. (#788)
      • Controller: Update image to v1.12.1.
      • Kube Webhook CertGen: Update image to v1.5.2.

    Removed

    • Chart: Sync to upstream. (#768https://github.com/giantswarm/ingress-nginx-app/pull/768)
      • Chart: Remove Pod Security Policies.
        NOTE: Pod Security Policies have already been removed from Kubernetes in v1.25. Therefore, this version is not compatible with Kubernetes v1.24 and below.
      • Values: Remove configmap.
        NOTE: The configmap value is deprecated since v3.0.0. Please use controller.config instead.
      • Deployment: Remove giantswarm.io/monitoring_basic_sli label.
      • Deployment: Remove OpenTelemetry init container.
        NOTE: OpenTelemetry is still supported, but since the module is built into the controller image since v1.10, we hereby remove the init container and image which were used to install it upon controller startup.
  • Connectivity external-dns-app v3.2.0

    Changed

    • Update architect-orb and ATS.
    • Add DNSEndpoints as a source for DNS records.
  • Connectivity kong-app v4.5.1

    Added

    • Allow users to change the unhealthyPodEvictionPolicy of the generated PodDisruptionPolicy. Default is IfHealthyBudget
    • Allow users to disable CRD installation Job by setting kubectlApplyJob.enabled to false
  • Connectivity gateway-api-app v1.2.0

    Added

    • Allow selecting channel (“standard” or “experimental”) for each individual CRD

    Changed

    • Upgrade Gateway API CRDs to v1.2.1
  • Connectivity ingress-nginx-app v4.0.0-alpha1

    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.

    Added

    • Chart: Sync to upstream. (#768https://github.com/giantswarm/ingress-nginx-app/pull/768)
      • Deployment: Add controller.progressDeadlineSeconds.
      • Pod Disruption Budget: Add controller.unhealthyPodEvictionPolicy.
      • Prometheus Rule: Add controller.metrics.prometheusRule.annotations.
      • Metrics Service: Add controller.metrics.service.enabled.
      • Default Backend: Add defaultBackend.maxUnavailable.
      • Default Backend: Add defaultBackend.unhealthyPodEvictionPolicy.

    Changed

    • Chart: Sync to upstream. (#768https://github.com/giantswarm/ingress-nginx-app/pull/768)
      • Controller: Update image to v1.12.0.
        NOTE: Please read the upstream changelog carefully, especially the entries marked with ⚠️. In addition, the following should be noted:
        • The --enable-annotation-validation CLI flag is already enabled by default in this app since v3.2.0.
        • The 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.
        • The 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.
        • The strict-validate-path-type ConfigMap option is already enabled by default in this app since v3.2.0.
      • Values: Rename image to global.image.

    Removed

    • Chart: Sync to upstream. (#768https://github.com/giantswarm/ingress-nginx-app/pull/768)
      • Chart: Remove Pod Security Policies.
        NOTE: Pod Security Policies have already been removed from Kubernetes in v1.25. Therefore, this version is not compatible with Kubernetes v1.24 and below.
      • Values: Remove configmap.
        NOTE: The configmap value is deprecated since v3.0.0. Please use controller.config instead.
      • Deployment: Remove giantswarm.io/monitoring_basic_sli label.
      • Deployment: Remove OpenTelemetry init container.
        NOTE: OpenTelemetry is still supported, but since the module is built into the controller image since v1.10, we hereby remove the init container and image which were used to install it upon controller startup.
  • Connectivity coredns-app v1.24.0

    Changed

    • Update coredns image to 1.12.0.
    • Disable HPA Memory target.
    • Increase threshold for HPA CPU target to 80%.
  • Connectivity kong-app v4.5.0

    Changed

    • Update kong ingress controller to 3.4.1
    • Align with upstream chart version 2.46.0 (Changes in upstream repository)
    • Revert ingressController.admissionWebhook settings to upstream values. (Enabled by default with failurePolicy: Ignore)
    • Update Kong Gateway image to 3.8.1.0-debian
    • Execute CRD installation Job only if ingressController is enabled (ingressController.enabled)

    Removed

    • Keep PSP disabled by default and remove Giant Swarm PSP-PSS migration hacks
    • Legacy Giant Swarm metrics Service and labels

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.