diff --git a/CHANGELOG.md b/CHANGELOG.md index 4d96b5f7d..1d80fd43a 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -5,6 +5,10 @@ numbering uses [semantic versioning](http://semver.org). ## Next Release +## v6.5.7 + +- Update Ambassador to version 1.7.3: [CHANGELOG](https://github.com/datawire/ambassador/blob/master/CHANGELOG.md) +- The BusyBox image image used by `test-ready` is now configurable (thanks, [Alan Silva](https://github.com/OmegaVVeapon)!) ## v6.5.6 diff --git a/Chart.yaml b/Chart.yaml index 3ddf5b682..266ee4852 100644 --- a/Chart.yaml +++ b/Chart.yaml @@ -1,9 +1,9 @@ apiVersion: v1 -appVersion: 1.7.2 -ossVersion: 1.7.2 +appVersion: 1.7.3 +ossVersion: 1.7.3 description: A Helm chart for Datawire Ambassador name: ambassador -version: 6.5.6 +version: 6.5.7 icon: https://www.getambassador.io/images/logo.png home: https://www.getambassador.io/ sources: diff --git a/README.md b/README.md index af85e6d0e..32f035fb2 100755 --- a/README.md +++ b/README.md @@ -98,7 +98,7 @@ The following tables lists the configurable parameters of the Ambassador chart a | `envRaw` | Additional environment variables in raw YAML format | `{}` | | `image.pullPolicy` | Ambassador image pull policy | `IfNotPresent` | | `image.repository` | Ambassador image | `docker.io/datawire/aes` | -| `image.tag` | Ambassador image tag | `1.7.2` | +| `image.tag` | Ambassador image tag | `1.7.3` | | `imagePullSecrets` | Image pull secrets | `[]` | | `namespace.name` | Set the `AMBASSADOR_NAMESPACE` environment variable | `metadata.namespace` | | `scope.singleNamespace` | Set the `AMBASSADOR_SINGLE_NAMESPACE` environment variable and create namespaced RBAC if `rbac.enabled: true` | `false`| diff --git a/crds/getambassador.io_hosts.yaml b/crds/getambassador.io_hosts.yaml index a3778bc88..465ec8ed4 100644 --- a/crds/getambassador.io_hosts.yaml +++ b/crds/getambassador.io_hosts.yaml @@ -62,7 +62,7 @@ spec: email: type: string privateKeySecret: - description: LocalObjectReference contains enough information to let you locate the referenced object inside the same namespace. + description: "Specifies the Kubernetes Secret to use to store the private key of the ACME account (essentially, where to store the auto-generated password for the auto-created ACME account). You should not normally need to set this--the default value is based on a combination of the ACME authority being registered wit and the email address associated with the account. \n Note that this is a native-Kubernetes-style core.v1.LocalObjectReference, not an Ambassador-style `{name}.{namespace}` string. Because we're opinionated, it does not support referencing a Secret in another namespace (because most native Kubernetes resources don't support that), but if we ever abandon that opinion and decide to support non-local references it, it would be by adding a `namespace:` field by changing it from a core.v1.LocalObjectReference to a core.v1.SecretReference, not by adopting the `{name}.{namespace}` notation." properties: name: description: 'Name of the referent. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#names TODO: Add other useful fields. apiVersion, kind, uid?' @@ -179,14 +179,14 @@ spec: type: string type: object tlsContext: - description: Name of the TLSContext the Host resource is linked with. It is not valid to specify both `tlsContext` and `tls`. + description: "Name of the TLSContext the Host resource is linked with. It is not valid to specify both `tlsContext` and `tls`. \n Note that this is a native-Kubernetes-style core.v1.LocalObjectReference, not an Ambassador-style `{name}.{namespace}` string. Because we're opinionated, it does not support referencing a Secret in another namespace (because most native Kubernetes resources don't support that), but if we ever abandon that opinion and decide to support non-local references it, it would be by adding a `namespace:` field by changing it from a core.v1.LocalObjectReference to a core.v1.SecretReference, not by adopting the `{name}.{namespace}` notation." properties: name: description: 'Name of the referent. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#names TODO: Add other useful fields. apiVersion, kind, uid?' type: string type: object tlsSecret: - description: Name of the Kubernetes secret into which to save generated certificates. If ACME is enabled (see $acmeProvider), then the default is $hostname; otherwise the default is "". If the value is "", then we do not do TLS for this Host. + description: "Name of the Kubernetes secret into which to save generated certificates. If ACME is enabled (see $acmeProvider), then the default is $hostname; otherwise the default is \"\". If the value is \"\", then we do not do TLS for this Host. \n Note that this is a native-Kubernetes-style core.v1.LocalObjectReference, not an Ambassador-style `{name}.{namespace}` string. Because we're opinionated, it does not support referencing a Secret in another namespace (because most native Kubernetes resources don't support that), but if we ever abandon that opinion and decide to support non-local references it, it would be by adding a `namespace:` field by changing it from a core.v1.LocalObjectReference to a core.v1.SecretReference, not by adopting the `{name}.{namespace}` notation." properties: name: description: 'Name of the referent. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#names TODO: Add other useful fields. apiVersion, kind, uid?' diff --git a/values.yaml b/values.yaml index 1a330bb3e..cc681e8b4 100644 --- a/values.yaml +++ b/values.yaml @@ -119,7 +119,7 @@ security: image: repository: docker.io/datawire/aes - tag: 1.7.2 + tag: 1.7.3 pullPolicy: IfNotPresent dnsPolicy: "ClusterFirst"