Skip to content

Conversation

pschichtel
Copy link
Member

As suggested in #3 a PR that introduces a chart for the gateway provisioner. I needed to build this anyway, because we standardized on deployments using helm. As a preparation I've also added a chart for the CRDs, which could be pulled by the main contour chart as well.

What I considered, but didn't do in this PR:

  • change the contour chart to pull contour-crds
  • pull the gateway-api CRDs via oci://docker.io/envoyproxy/gateway-crds-helm

@pschichtel
Copy link
Member Author

I bootstrapped the contour-gateway-provisioner chart using helm create and then reduced that to what's needed and merged in the non-crd resources from the official manifest file.

@pschichtel pschichtel force-pushed the feature/gateway-provisioner-chart branch 4 times, most recently from 058fa58 to 3f0d471 Compare September 1, 2025 18:27
@pschichtel
Copy link
Member Author

I have an internal fork deployed to a cluster in together with the contour chart (with manageCRDs: false)

@pschichtel pschichtel force-pushed the feature/gateway-provisioner-chart branch from 3f0d471 to 9ac1fb2 Compare September 1, 2025 18:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant