* Add sidecar and rbac customization
Following patters in other charts, sidecar pods and rbac customization
was added
* Bump contour version
* Update contour readme with new values
* Adapt values.yaml of Cert Manager, Consul and Contour charts
* Fix liniting issues
* Add charts path to be recognized by Github Actions workflow
* Remove duplicate metadata in Cert Manager values.yaml
* Minor additions to cert-manager values.yaml
* Add missing commented keys in Consul
* Add missing commented keys in Contour
* Bump Consul chart patch version
* cert-manager: Update README with latest changes from master
* consul: Update README with latest changes from master
* Bump charts' patch version
* [bitnami/contour] Add the possibility to set HostIP
The cart does not allow setting the `hostIP` parameter on the
Envoy Deamonset. This is useful in certain cases (e.g. with `k3s`
and single-node deployments) and should be possible.
This commit simply adds the possibility to set the `hostIP` on ports
exposed by Envoy.
Co-authored-by: Alejandro Moreno <alemorcuq@gmail.com>
Co-authored-by: Alejandro Moreno <alemorcuq@gmail.com>
* Remove extra line
* Remove extra line
Co-authored-by: Alejandro Moreno <alemorcuq@gmail.com>
Co-authored-by: Alejandro Moreno <amorenoc@vmware.com>
* Place CRDs into a subchart of contour.
Helm does not perform any actions on CRDs when a chart is upgraded.
Placing the CRDs in a subchart causes them to be processed when the
contour chart is upgraded.
Discussions about this approach - https://github.com/projectcontour/contour/issues/2050#issuecomment-673722738
* Bump version to 4.0.0 as there is a breaking change in how CRDs are installed and upgraded(see README).
* Changed the repository location for contour-crds - this lives as top-level in charts.
* Update Chart and add subchart.
* Move contour-crds back inside contour chart.
* Bump the chart version and fix trailing spaces.
* Updated README to indicate notable changes and steps required for upgrading from 3.x to 4.
* Move the 4.0.0 notes to the 'Upgrade' section.
* Move out contour-crds subchart to manage CRDs in a separate `resources` directory.
Add a `contour.manageCRDs` flag to indicate whether you want the chart to manage CRDs or not.
* Remove the obsolete(Helm v2) CRD options from the README and values.yaml.
Document the new `manageCRDs` option.
* Remove values-production.yaml
We remove this because values.yaml and values-production.yaml are identical and
bitnami member Francisco de Paz Galán stated:
> Also, you can delete the values-production.yaml file, as it is something that
> is in our roadmap to be removed from all of our charts.
Ref: https://github.com/bitnami/charts/pull/3788#pullrequestreview-516865711
* Divide parameters into smaller blocks
* Implement a contour default backend for convenience
This is almost a copy-paste from the nginx-ingress-controller chart:
https://github.com/bitnami/charts/tree/master/bitnami/nginx-ingress-controller
* Move README comments "(eval. as a template)" to right column
* Apply requested changes from review
* Add 3 more missing parameters to README
* Allow extra arguments to be specified, and passed to Contour container
This is useful for enabling the PROXY protocol by specifying
`--use-proxy-protocol` as an extra arg.
See https://projectcontour.io/guides/proxy-proto/ for more information.
* Update contour README.md
* Use `common.tplvalues.render` to render extra args for Contour
* Contour v3.2.0
* Explicitly declare namespace to help with tool integration, also allow putting ServiceMonitor into a different namespace.
* Missing values production.
* Update Chart.yaml
* fix: automatic update of ingress.status by envoy
As the helm chart uses contour-envoy as the name for the envoy service (which differs from the default envoy service name 'envoy' which contour expects as default), this change adjusts the default configuration to ensure automatic ingress.status updates work out of the box.
* Update of chart version
* Forgot the values-production.yaml
* Update bitnami/contour/values-production.yaml
Using same expression which defines the name of the envoy-service in `templates/envoy/service.yaml`.
Co-authored-by: Jose Antonio Carmona <joancafom@icloud.com>
* fix: using the exact naming expression also used by templates/envoy/service.yaml
* fix: linting error trailing spaces
Co-authored-by: Jose Antonio Carmona <joancafom@icloud.com>
Co-authored-by: Jose Antonio Carmona <jcarmona@bitnami.com>
* [bitnami/contour]add new templates for version 1.9
* [bitnami/contour]add new templates for version 1.9
* change cdr
* [bitnami/contour] Update components versions
Signed-off-by: Bitnami Containers <containers@bitnami.com>
Co-authored-by: Bitnami Containers <containers@bitnami.com>
