This file documents all notable changes to Ambassador Helm Chart. The release numbering uses semantic versioning.
- 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. TheenableAES
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 AuthService documentation) - The ambassador-pro-auth
AuthService
and ambassador-pro-ratelimitRateLimitService
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
, andadditionalTCPPort
has been replaced withservice.ports
.rbac.namespaced
has been removed. Usescope.singleNamespace
instead.
- Ambassador Pro will pick up when
AMBASSADOR_ID
is set in.Values.env
[#15025]. {{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
. [ambassador/#1576] - RBAC configuration now allows for multiple Ambassadors to use CRDs. Set
crds.enabled
in releases that expect CRDs [ambassador/#1679]
- 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
anddnsPolicy
- Adds HOST_IP environment variable
- Adds support for init containers using
initContainers
and pod labelspodLabels
- Update ambassador to 0.60.3
- Add support for Ambassador PRO see readme
- 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
andnamespace.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 Migrating from datawire/ambassador chart