Project: Emissary-Ingress (Orchestration & Management / API Gateway)
File: CHANGELOG.md

This file documents all notable changes to Ambassador Helm Chart. The release numbering uses . Upgrade Emissary to v3.10.0 Ambassador Agent is no longer installed by default and requires setting `agent.enabled: true` to opt-in. We recommend you use the stand alone chart instead . Upgrade Emissary to v3.9.0 Feature: configure autoscaling behaviors for HorizontalPodAutoscaler in `.Values.autoscaling.behavior` Fix: wrong autoscaling apiVersion on EKS due to EKS not following semver (see https://github.com/aws/containers-roadmap/issues/1404, https://github.com/helm/helm/issues/10375, https://github.com/helm/helm/issues/12053) Upgrade Emissary to v3.8.0 Fix: Ambassador Agent RBAC so that it can properly find cloud connect tokens in a secret Upgrade Ambassador Agent to the latest z-patch of 1.0.14. Upgrade Emissary to v3.7.1 Upgrade Emissary to v3.7.0 Upgrade Emissary to v3.6.0 Use autoscaling/v2 HorizontalPodAutoscaler if the cluster version is >=v1.23 as autoscaling/v2beta2 is deprecated starting v1.23 and removed in v1.26. Thanks to Upgrade KubernetesEndpointResolver & ConsulResolver apiVersions to `getambassador.io/v3alpha1` Add support for setting `nodeSelector`, `tolerations` and `affinity` on the Ambassador Agent. Thanks to . Upgrade Emissary to v3.5.1 Fix regression where the Module resource fails validation when setting the ambassador_id after upgrading to `getambassador.io/v3alpha1`. Thanks to Upgrade Emissary to v3.5.0 Adds support for configuring a startupProbe on the emissary-ingress deployments. This is useful when a larger number of resources are used and the initial startup needs additional time. See for details https://github.com/emissary-ingress/emissary/pull/4649. Update default module resource to use `getambassador.io/v3alpha1`. Thanks to Upgrade Emissary to v3.4.0 The Ambassador agent that was previously embedded in Emissary Ingress has been moved to a standalone container. Upgrade Emissary to v3.3.0 Change: By default, the Ambassador agent will report diagnostics to the Ambassador Cloud Change: updated auto-scaling resource cpu and memory variable ordering to help with git-ops syncing. Also, adjusted memory and cpu settings to be more friendly so that they do not cause the HPA auto-scaling to trigger during start-up. Thanks to for the contribution! Upgrade Emissary to v3.2.0 Bugfix: The default Role configuration of the Ambassador Agent Deployment will allow it to correctly watch Secret resources for Ambassador Cloud tokens. Upgrade Emissary to v3.1.0 Change: The default for the `module` value has changed to enable serving remote client requests to the <code>:8877/ambassador/v0/diag/</code> endpoint by default. Upgrade Emissary to v3.0.0 Change: The default for the `module` value has changed to disable the `/ambassador/v0/` `127.0.0.1:8877` synthetic Mapping by default. We have long recommended to turn this off for production use; it is now off by default. Bugfix: The default values no trigger the creation of an "emissary-test-ready" Pod. This Pod was meant to only be created when running the chart's test suite; it was not meant to be created in users' clusters. Upgrade Emissary to v2.4.0 Update Emissary chart image to version v2.3.2 Update Emissary chart image to version v2.3.1 Update change Emissary chart image to version v2.3.0 Add "lifecycle" option to main container. This can be used, for example, to add a lifecycle.preStop hook. Thanks to for the contribution! Add `ambassadorid` to listener manifests rendered when using `createDefaultListeners: true` with `AMBASSADORID` set in environment variables. Thanks to for the contribution! Feature: Added configurable IngressClass resource to be compliant with Kubernetes 1.22+ ingress specification. Upgrade Emissary to v2.2.2 Upgrade Emissary to v2.2.1 Upgrade Emissary to v2.2.0 Update Emissary chart image to version v2.1.2: There was no v7.2.1 release; we skipped to v7.2.2 to keep the version number in-sync with the edge-stack

Update Emissary chart image to version v2.1.0: Change: It is now always nescessary to manually apply `emissary-crds.yaml` before applying the chart. Bugfix: When setting `adminService.snapshotPort`, it now points at the correct port on the Pod. Update Ambassador chart image to version v2.0.5: Update Ambassador chart image to version v2.0.4: Update Ambassador chart image to version v2.0.3-ea: Update Ambassador chart image to version v2.0.2-ea: Update Ambassador chart image to version v2.0.1-ea: Feature: New canarying features for Ambassador in the chart that allow creation of a secondary deployment/service to test new versions and environment variables. Feature: Exposed `progressDeadlineSeconds` for the Ambassador and Ambassador Agent Deployments with new values We're pleased to introduce Emissary 2.0.0 as a developer preview. Emissary Ingress chart v7.0.0-ea provides early access to Emissary 2.0 features. Update Ambassador chart image to version v2.0.0-ea: Change: removed helm 2 support Feature: Add an option to create default HTTP and HTTPS listeners Update Ambassador API Gateway chart image to version v1.14.4: Update Ambassador Edge Stack chart image to version v1.14.4: Update Ambassador API Gateway chart image to version v1.14.3: Update Ambassador Edge Stack chart image to version v1.14.3: Update Ambassador API Gateway chart image to version v1.14.2: Update Ambassador Edge Stack chart image to version v1.14.2: (v6.9.2 was withdrawn) Update Ambassador API Gateway chart image to version v1.14.1: Update Ambassador Edge Stack chart image to version v1.14.1: Update Ambassador Edge Stack chart image to version v1.14.0: Update Ambassador API Gateway chart image to version v1.14.0: Feature: New Values to expose `progressDeadlineSeconds` for the Ambassador and Ambassador-agent Deployments. Update Ambassador API Gateway chart image to version v1.13.10: Update Ambassador Edge Stack chart image to version v1.13.10: Update Ambassador API Gateway chart image to version v1.13.9: Update Ambassador Edge Stack chart image to version v1.13.9: Update Ambassador API Gateway chart image to version v1.13.8: Update Ambassador Edge Stack chart image to version v1.13.8: Bugfix: remove duplicate label key in ambassador-agent deployment Update Ambassador API Gateway chart image to version v1.13.7: Update Ambassador Edge Stack chart image to version v1.13.7: Update Ambassador chart image to version 1.13.6: Update Ambassador chart image to version 1.13.5: Bugfix: ambassador-injector and telepresence-proxy now use the correct default image repository Update Ambassador chart image to version 1.13.4: Change: unless image.repository or image.fullImageOverride is explicitly set, the ambassador image used will be templated on .Values.enableAES. If AES is enabled, the chart will use docker.io/datawire/aes, otherwise will use docker.io/datawire/ambassador. Update Ambassador chart image to version v1.13.3: Feature: The can now be configured and managed by Helm Update Ambassador chart image to version v1.13.2: Bugfix: Don't change the Role name when running in singleNamespace mode. Update Ambassador chart image to version v1.13.1: Update Ambassador to version 1.13.0: Feature: Ambassador Agent now available for API Gateway (https://app.getambassador.io) Feature: Add support for via the `topologySpreadConstraints` helm value to the Ambassador deployment. (thanks, !) BugFix: Add missing `ambassador_id` for resolvers. Change: Ambassador ClusterRoles are now aggregated under the label `rbac.getambassador.io/role-group`. The aggregated role has the same name as the previous role name (so no need to update ClusterRoleBindings). Update Ambassador to version 1.12.4: Update Ambassador to version 1.12.3: Update Ambassador to version 1.12.2: Fix metadata field in ConsulRevoler Make resolvers available to OSS Update Ambassador to version 1.12.1: Feature: Apply Ambassador Agent deployment by default to enable Service Catalog reporting (https://app.getambassador.io) Bugfix: Disable the cloud agent by

The agent will be enabled in 6.6.0. Bugfix: Adds a check to prevent the cloud agent from being installed if AES version is less than 1.12.0 Update Ambassador to version 1.12.0: Feature: Add support for the ambassador-agent, reporting to Service Catalog (https://app.getambassador.io) Feature: All services are automatically instrumented with discovery annotations. Update Ambassador to version v1.11.2: Make all `livenessProbe` and `readinessProbe` configurations available to the values file Update Ambassador to version v1.11.1: Update Ambassador to version v1.11.0: Bugfix: Fix Mapping definition to correctly support labels in use. Bugfix: Ambassador CRD cleanup will now execute as expected. Bugfix: Ambassador RBAC now includes permissions for IngressClasses. Update for Ambassador v1.10.0 Update for Ambassador v1.9.1 Feature: Add ability to configure `terminationGracePeriodSeconds` for the Ambassador container Update for Ambassador v1.9.0 Feature: add affinity and tolerations support for redis pods Update Ambassador to version 1.8.1: Update Ambassador to version 1.8.0: Bugfix: The RBAC for AES now grants permission to "patch" Events.v1.core. Previously it granted "create" but not "patch". Update Ambassador to version 1.7.4: Update Ambassador to version 1.7.3: The BusyBox image image used by `test-ready` is now configurable (thanks, !) Update Ambassador to version 1.7.2: Feature: Allow overriding the namespace for the release using the values file: Allow hyphens in service annotations: Upgrade Ambassador to version 1.7.1: Upgrade Ambassador to version 1.7.0: Feature: Add support for DaemonSet/Deployment labels: Upgrade Ambassador to version 1.6.2: Upgrade Ambassador to version 1.6.1: Upgrade Ambassador to version 1.6.0: Feature: Allow specifying annotations for the license-key-secret: Feature: Annotation for keeping the AES secret on removal: Fix: do not mount the secret if we do not want a secret: Internal CI refactorings. BugFix: Cannot specify podSecurityPolicies: Upgrade Ambassador to version 1.5.5: BugFix: Registry service is now using the proper `app.kubernetes.io/name` BugFix: Restore ability to set `REDIS` env vars in `env` instead of `redisEnv` Feature: Add `envRaw` to support supplying raw yaml for environment variables. Deprecates `redisEnv`. Upgrade Ambassador to version 1.5.4: Added support setting external IPs for the ambassador service (thanks, !) Upgrade Ambassador to version 1.5.3: Feature flag for enabling or disabling the redisEnv for setting environment variables to control how Ambassador interacts with redis. See Upgrade Ambassador to version 1.5.2: Upgrade Ambassador to version 1.5.1: BugFix: The `PodSecurityPolicy` should not be created by default since it is a cluster-wide resource that should only be created once. If you would like to use the default `PodSecurityPolicy`, make sure to unset `security.podSecurityPolicy` it in all other releases. Upgrade Ambassador to version 1.5.0: AuthService and RateLimitService are now installed in the same namespace as Ambassador. Changes RBAC permissions to better support single-namespace installations and detecting getambassador.io CRDs. Add option to install Service Preview components (traffic-manager, traffic-agent). Add option to install ambassador-injector, alongside Service Preview. Add additional security policy configurations. `securityContext` has been deprecated in favor of `security` which allows you to set container and pod security contexts as well as a default `PodSecurityPolicy`. Switch from Quay.io to DockerHub Upgrade Ambassador to version 1.4.3: Minor bug fixes Add extra labels to ServiceMonitor: Upgrade Ambassador to version 1.4.2: Upgrade Ambassador to version 1.4.1: Adds: Option to create a ServiceMonitor for scraping via Prometheus Operator Upgrade Ambassador to version 1.4.0: Fix typing so that Helm3 doesn't complain (thanks, !) Upgrade Ambassador to version

Use explicit types for things like ports, so that things like `helm .. --set service.ports[0].port=80` will be integers instead of ending up as strings Upgrade Ambassador to version 1.3.1. Remove unnecessary `version` field from CRDs. Add static label to AES resources, to better support `edgectl install` Upgrade Ambassador to version 1.3.0. Add option to not create DevPortal routes Upgrade Ambassador to version 1.2.2. Upgrade from Ambassador 1.2.0 to 1.2.1. Upgrade from Ambassador 1.1.1 to 1.2.0. Upgrade from Ambassador 1.1.0 to 1.1.1. Minor Improvements: Adds: Option to override the name of the RBAC resources Minor improvements including: Adds: Option to set `restartPolicy` Adds: Option to give the AES license key secret a custom name Fixes: Assumption that the AES will be installed only from the `datawire/aes` repository. The `enableAES` flag now configures whether the AES is installed. Clarification on how to install OSS Introduces Ambassador Edge Stack being installed by default. Ambassador Pro support has been removed in 6.0.0. Please upgrade to the Ambassador Edge Stack. Note If upgrading an existing helm 2 installation no action is needed, previously installed CRDs will not be modified. Helm 3 support for CRDs was added. Specifically, the CRD templates were moved to non-templated files in the `/crds` directory, and to keep Helm 2 support they are globbed from there by `/templates/crds.yaml`. However, because Helm 3 CRDs are not templated, the labels for new installations have necessarily changed Introduces the performance tuned and certified build of open source Ambassador, Ambassador core The license key is now stored and read from a Kubernetes secret by default Added `.Values.pro.licenseKey.secret.enabled` `.Values.pro.licenseKey.secret.create` fields to allow multiple releases in the same namespace to use the same license key secret. Introduces the ability to configure resource limits for both Ambassador Pro and it's redis instance Introduces the ability to configure additional `AuthService` options (see ) The ambassador-pro-auth `AuthService` and ambassador-pro-ratelimit `RateLimitService` and now created as CRDs when `.Values.crds.enabled: true` Fixed misnamed selector for redis instance that failed in an edge case Exposes annotations for redis deployment and service The default annotation has been removed. The service port will be set dynamically to 8080 or 8443 for http and https respectively. `service.http`, `service.https`, and `additionalTCPPort` has been replaced with `service.ports`. `rbac.namespaced` has been removed. Use `scope.singleNamespace` instead. Ambassador Pro will pick up when `AMBASSADOR_ID` is set in `.Values.env` . `{{release name}}-admins` has been renamed to `{{release name}}-admin` to match YAML install templates RBAC configuration has been updated to allow for CRD use when `scope.singleNamespace: true`. RBAC configuration now allows for multiple Ambassadors to use CRDs. Set `crds.enabled` in releases that expect CRDs Add ambassador CRDs! Update ambassador to 0.70.0 Update ambassador to 0.61.1 Add support for autoscaling using HPA, see `autoscaling` values. Update ambassador to 0.61.0 Allow configuring `hostNetwork` and `dnsPolicy` Adds HOST_IP environment variable Adds support for init containers using `initContainers` and pod labels `podLabels` Update ambassador to 0.60.3 Add support for Ambassador PRO Update ambassador to 0.60.2 Update ambassador to 0.60.1 Fix RBAC for ambassador 0.60.0 Update ambassador to 0.60.0 Added `scope.singleNamespace` for configuring ambassador to run in single namespace Update ambassador to 0.53.1 Update ambassador to 0.52.0 Removed `ambassador.id` and `namespace.single` in favor of setting environment variables. Update ambassador to 0.50.3 support targetPort specification Update ambassador to 0.50.2 Add additional chart maintainer Default replicas -> 3 Allow RBAC to be namespaced (`rbac.namespaced`) First release of Ambassador Helm Chart in helm/charts For migration see