Connectivity
Changed
- Only template Secret if both required values are present in
values.yaml. (#53)
Changed
- Reworked the App to prepare it for customer use. (#49)
- General:
- Pushes the app to the giantswarm app catalog.
- Uses Helm release namespace.
- Uses the release name for resource naming to avoid conflicts.
- Added a values schema to catch incorrect values.
- Generally makes the chart easier to use (fully documented values file).
- external-dns options:
- Allows customisation of the txt registry prefix.
- Allows configuration of synchronisation interval.
- Filter resources to reconcile via annotations.
- AWS-specifc:
- Allows the user to provide an IAM role to use.
- Allows the user to provide the list of domains for external-dns to manage.
- Allows configuration of batch size.
- Allows configuration of CNAME instead of ALIAS records.
- Allows configuration of the AWS zone type to update.
Added
- Add annotation to controller service for external-dns to use for filtering resources. (#169)
- Support user-provided annotations for the controller deployment. (#170)
Changed
- Update image to
v0.43.0. (#165)
Changed
- Upgrade upstream external-dns from v0.7.4 to v0.7.6.
Added
- Allow toggling of the
--update-status flag. Disabling this feature stops NGINX IC from updating Ingress Loadbalancer status fields. (#151)
Changed
- Add ability to set podAntiAffinity scheduling method via the values file. (#146)
Updated
- Update architect-orb to 0.18.1
- Sync with upstream chart 1.12.0. Please check the upstream changelog.
Added
- Add ability to extend
nginx-ingress-controllerwith specific values from appcatalog. - User value validation through a values.schema.json file based on the current values.yaml.
Changed
- Update image to
v0.41.2. (#133)
Added
- Add minReadySeconds to deployment template as optional parameter
Updated
- architect-orb 0.11.0 -> 0.14.0
- github workflow
Breaking changes
- Kong Ingress Controller 1.0 removes support for several deprecated flags and
the KongCredential custom resource. Please see the controller changelog
for details. Note that Helm 3 will not remove the KongCredential CRD by
default: you should delete it manually after converting KongCredentials to
credential Secrets.
If you manage CRDs using Helm (check to see if your KongCredential CRD has a
app.kubernetes.io/managed-by: Helm label), perform the credential Secret
conversion before upgrading to chart 1.11.0 to avoid losing credential
configuration. - The chart no longer uses the
extensions API for PodSecurityPolicy, and now
uses the modern policy API. This breaks compatibility with Kubernetes
versions 1.11 and older.
(#195)
Updated
- Update architect-orb to 0.11.0
- Sync with upstream chart 1.11.0
- Please check the upstream CHANGELOG.md
Changed
- Change upstream default branch in upstream-sync script