* [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>
* fix: using correct service name to output external ip of Contour ingress
* fix: using correct service name to output external ip of Contour ingres
* Bump chart version
* Sync back most significant upstream projectcontour changes
The most important change is the refactoring of the shutdown sidecar:
7cd9f4a685
Signed-off-by: Marco Kilchhofer <marco@kilchhofer.info>
* Delete removed CRD ingressroutes.contour.heptio.com
> As a reminder, support for IngressRoute was officially dropped in v1.6.
> If you haven’t already migrated to HTTPProxy, see the IngressRoute to
> HTTPProxy migration guide for instructions on how to do so. Once you have
> migrated, delete the IngressRoute and related CRDs.
Ref: https://projectcontour.io/resources/upgrading/
Signed-off-by: Marco Kilchhofer <marco@kilchhofer.info>
* Sync HTTPProxy CRD
Signed-off-by: Marco Kilchhofer <marco@kilchhofer.info>
* Sync TLSCertificateDelegation CRD
* Drop old TLSCertificateDelegation CRD on API group contour.heptio.com
API group contour.heptio.com is no longer supported since 1.6.x
* Bump minor chart version as the change is no longer a patch
Signed-off-by: Marco Kilchhofer <marco@kilchhofer.info>
* Attempt to fix contour tests by upgrading to latest github actions
* Override envoy service type to ClusterIP to make tests happy
I found a hint in PR #2721 that it should be possible to override values
used in GH actions.
* Revert "Attempt to fix contour tests by upgrading to latest github actions"
This was requested during the review process by dani8art.
This reverts commit 253a8ecd60.
* Add bitnami/common as a dependency
Signed-off-by: Marco Kilchhofer <marco@kilchhofer.info>
* Also use bitnami/common subchart for image
* Implement extraVolumes and extraVolumeMounts on contour and envoy
Signed-off-by: Marco Kilchhofer <marco@kilchhofer.info>
* Implement extraEnvVars on contour and envoy
Signed-off-by: Marco Kilchhofer <marco@kilchhofer.info>
* Implement extraEnvVarsConfigMap and extraEnvVarsSecret
* Implement initContainers for contour and envoy
* Implement service.extraPorts on contour and envoy
* Implement rolling tags helpers
* Sync rbac with upstream
As George Goh (@georgegoh) mentioned in issue projectcontour/contour#2050
the leaderelection role is not needed anymore:
> 1. I remove the `contour-leaderelection` role as it's no longer needed
> in `templates/rbac.yaml`.
> 2. General matching of the rbac.yaml to the rbacs defined in this project.
Signed-off-by: Marco Kilchhofer <marco@kilchhofer.info>
* Update README.md
* Fix default values for image repositories
* Add quotes (`)
* Fix whitespaces in table
* Also use bitnami/common subchart for pullSecrets
The subchart bitnami/common now supports this (version 0.6.2 and newer).
See PR #3566
* Use same tpl functions for job
Inside the Deployment we can use templating with 'tpl'. Since we use the
same structure (affinity, nodeSelector and tolerations) for the
Deployment and the Job, we should also use the same template functions.
* Fix: affinity defined twice
* Use more specific keyword antiAffinity -> antiAffinityPolicy
* Bump chart major: 2.0.0
* Variant2: Implement certgen by using hooks (#2)
* Implement certgen via hooks
* Delete resources with helm hooks only if needed
* Revert "Delete resources with helm hooks only if needed"
This reverts commit 76449252d06b7bda0f16c490316478c3fb1004f1.
As documented inside the helm docs, we should remove unneeded resources:
~~~
The resources that a hook creates are currently not tracked or managed as part
of the release. Once Helm verifies that the hook has reached its ready state,
it will leave the hook resource alone. Garbage collection of hook resources
when the corresponding release is deleted may be added to Helm 3 in the future,
so any hook resources that must never be deleted should be annotated with
`helm.sh/resource-policy: keep`.
Practically speaking, this means that if you create resources in a hook, you
cannot rely upon helm uninstall to remove the resources. To destroy such
resources, you need to either add a custom `helm.sh/hook-delete-policy`
annotation to the hook template file, or set the time to live (TTL) field of
a Job resource.
~~~
* Replace colons with dashes (standardize even more)
This was requested during review by @dani8art
* Clearify README regarding CRDs and helm v3
* Add small upgrading notes to README
* Fix helm2 incompatibility due to PR #2961
Helm2 uses Sprig v2 and therefore the funtion "get" is not available
there. Since we need to guarantee helm v2 support, we need to workaround
this.
* Use consistent component labels on certgen resources
* Use bitnami/common for apiVersion of kind Deployment
* Rename parameter `contour.createCustomResource` to `contour.installCRDs`
* Do not allocate an IP address on metrics services
Services for ServiceMonitor do not need to allocate an IP address. We therefore do not
waste IPs from the services CIDR pool for this.
* Split into subfolders
* Add ability to specify ingressClass
Signed-off-by: Marco Kilchhofer <marco@kilchhofer.info>
* Roll contour pods when config changes
Signed-off-by: Marco Kilchhofer <marco@kilchhofer.info>
* Add documentation (README) of already implemented settings
Signed-off-by: Marco Kilchhofer <marco@kilchhofer.info>
* Remove duplicate in README (rbac.create)
Signed-off-by: Marco Kilchhofer <marco@kilchhofer.info>
