1. Docs
  2. Changes and releases
  3. Managed Apps

Managed Apps

  • Managed Apps ingress-nginx-app v1.8.2

    Fixed

    • Fix controller RBAC permissions, granting “get” and “update” of leader election ConfigMap lock.
  • Managed Apps fluent-logshipping-app v0.5.2
  • Managed Apps cert-manager-app v2.0.2

    Changed

    • Install CRDs during chart installation only. (#46)
  • Managed Apps dex-app v1.2.2

    Fixed

    • Fix github release workflow.
  • Managed Apps ingress-nginx-app v1.8.1

    Added

    • Make node ports configurable for NodePort Service type.
  • Managed Apps cert-manager-app v2.0.1

    Changed

    • Fixed leader election namespace. (#41)
    • Template validatingwebhook namespace selector. (#43)
    • Align CRD templating with the main chart. (#42)

    Added

    • Add Github release workflow.
  • Managed Apps strimzi-kafka-operator-app v0.0.1

    Added

    • Initial helm chart based on upstream strimzi-kafka-operator v0.18.0
    • Cruise Control example
    • GitHub workflows
  • Managed Apps 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
  • Managed Apps kube-prometheus-stack-app v0.3.4

    Added

    • Set default request/limits in deployment (cpu: 100m, memory: 100Mi) per best practice

    Changed

    • Sync with upstream
      • Bug fixes
      • Add namespace overwrite

    Updated

    • Update architect-orb to 0.10.0
    • kube-state-metrics chart 2.8.8 -> 2.8.11
    • grafana chart 5.1.4 -> 5.3.0
    • grafana chart requirement 5.1.* -> 5.3.*
    • configmapReloadImage 0.0.1 -> 0.3.0
    • hyperkubeImage 1.12.1 -> 1.16.12
  • Managed Apps prometheus-operator-app v0.3.4

    Added

    • Set default request/limits in deployment (cpu: 100m, memory: 100Mi) per best practice

    Changed

    • Sync with upstream
      • Bug fixes
      • Add namespace overwrite

    Updated

    • Update architect-orb to 0.10.0
    • kube-state-metrics chart 2.8.8 -> 2.8.11
    • grafana chart 5.1.4 -> 5.3.0
    • grafana chart requirement 5.1.* -> 5.3.*
    • configmapReloadImage 0.0.1 -> 0.3.0
    • hyperkubeImage 1.12.1 -> 1.16.12