1. Docs
  2. Changes and releases
  3. Connectivity

Connectivity

  • Connectivity external-dns-app v1.3.0

    Added

    • Added monitoring and common labels.

    Changed

    • Upgrade upstream external-dns from v0.7.2 to v0.7.3.
    • Upgrade architect-orb to 0.10.1
  • Connectivity ingress-nginx-app v1.9.1
    • Configure explicit helm hook weights to make validating webhook resource management reliable.
  • Connectivity ingress-nginx-app v1.9.0
    • Support Ingress resources validating webhook.
  • Connectivity ingress-nginx-app v1.8.4

    Fixed

    • Fix NetworkPolicy templating, to allow Pod ingress traffic (Prometheus scrape requests) on same port that the metrics/monitoring service advertises.
  • Connectivity ingress-nginx-app v1.8.3

    Fixed

    • Fix controller RBAC permissions, granting “get” and “update” of leader election ConfigMap lock.
  • Connectivity ingress-nginx-app v1.8.2

    Fixed

    • Fix controller RBAC permissions, granting “get” and “update” of leader election ConfigMap lock.
  • Connectivity ingress-nginx-app v1.8.1

    Added

    • Make node ports configurable for NodePort Service type.
  • Connectivity ingress-nginx-app v1.8.0

    Breaking changes

    In older releases the NGINX IC LoadBalancer Service name was hardcoded to nginx-ingress-controller. As of this release, to ensure the Service name uniqueness for multiple NGINX ICs per cluster support, the LoadBalancer Service name was made to be dynamic, derived from Helm release i.e. App Custom Resource (CR) name. Therefore, if you’re upgrading from an older NGINX IC App release to v1.8.0+, existing NGINX IC LoadBalancer Service may get replaced by a new one for every NGINC IC App CR whose name is not nginx-ingress-controller. When NGINX IC LoadBalancer Service gets recreated, cloud service provider (CSP) load balancer behind it gets recycled as well. It can take minute or so for ingress DNS records to be updated by external-dns and change propagated to clients. During that time there’s ingress traffic downtime, since clients still resolve old no longer present CSP load balancer. Please take the potential ingress downtime (a minute or so) into consideration when planning the NGINX IC App upgrade from older to v1.8.0+. To make sure the downtime is shortest possible, external-dns availability is important precondition. In recent platform releases (Azure v12.0.2, and AWS v12.1.4 and v11.5.4) we’ve improved external-dns monitoring and alerting. Therefore, before upgrading NGINX IC optional app to v1.8.0+, please make sure that your cluster has been upgraded to the latest platform release.

    Added

    • Support multiple NGINX IC App installations per tenant cluster.

    Removed

    • Dropped support for deprecated configuration properties:
      • configmap.annotations-prefix
      • configmap.default-ssl-certificate
      • configmap.hpa-enabled
      • configmap.hpa-max-replicas
      • configmap.hpa-min-replicas
      • configmap.hpa-target-cpu-utilization-percentage
      • configmap.hpa-target-memory-utilization-percentage
      • configmap.ingress-class
  • Connectivity ingress-nginx-app v1.7.3

    Changed

  • Connectivity coredns-app v1.2.0

    Changed

    • Apply a readiness probe
    • Increase the liveness probe failure threshold from 5 failures to 7 failures

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.