Open totallyGreg opened 2 years ago
We use Terraform and its various providers instead of Helm. We currently manage Gloo configuration via Terraform-controlled kube configs, not unlike Helm (but Terraform's templating is so much easier). Often we run into times that it would be ideal to be able to query Gloo's custom resources so that we can validate or wire in information, like when Gloo automatically creates Upstreams.
Terraform providers also do a far better job than Helm at documenting what options are available and why since all of the contract is a static schema.
Helm may still be ideal for the initial deploy, but a provider to manipulate or even just query the resources would be great.
I would use a provider that created and queried VirtualServices
, RouteTables
, Upstreams
, RateLimitConfigs
, etc.
This issue has been marked as stale because of no activity in the last 180 days. It will be closed in the next 180 days unless it is tagged "no stalebot" or other activity occurs.
Version
No response
Is your feature request related to a problem? Please describe.
Providers in Terraform allow static contracts and clear documentation of the various options that can be configured. it would be nice to query the custom resources, like the upstreams, to aid in wiring everything together
Describe the solution you'd like
Creating a Terraform provider would allow customers the ability to define their complex infrastructure consistently
Describe alternatives you've considered
using the helm provider to define Gloo values.
Additional Context
No response