You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is a feature request to add support for the managed prometheus capability in the Cluster resource. Though, it might make sense to support a field that could take arbitrary input (such as extraArgs often seen in helm values files) as a faster way to allow users to consume new features released by Google and supported here: https://cloud.google.com/kubernetes-engine/docs/reference/rest/v1/projects.locations.clusters#Cluster
Ultimately, this issue is largely about enabling the ability to toggle on managed prometheus for cluster objects. I would suspect the yaml might look like the following... though we could look at other examples that have implemented this (e.g. terraform) for inspiration.
I currently use Crossplane to build many of our clusters and related objects, but use Terraform and Flux where crossplane is slower on the support of a provided feature. In this case, flux is used to install GMP, but this is a post-install activity that can cause some challenges and we suspect that enabling the feature may be less error prone than managing and updating post-deployment configuration manifests.
Thanks for your time and effort reading this, and for crossplane and the crossplane-gcp support in general!
The text was updated successfully, but these errors were encountered:
What problem are you facing?
This is a feature request to add support for the managed prometheus capability in the Cluster resource. Though, it might make sense to support a field that could take arbitrary input (such as
extraArgs
often seen in helm values files) as a faster way to allow users to consume new features released by Google and supported here: https://cloud.google.com/kubernetes-engine/docs/reference/rest/v1/projects.locations.clusters#ClusterUltimately, this issue is largely about enabling the ability to toggle on managed prometheus for cluster objects. I would suspect the yaml might look like the following... though we could look at other examples that have implemented this (e.g. terraform) for inspiration.
How could Crossplane help solve your problem?
I currently use Crossplane to build many of our clusters and related objects, but use Terraform and Flux where crossplane is slower on the support of a provided feature. In this case, flux is used to install GMP, but this is a post-install activity that can cause some challenges and we suspect that enabling the feature may be less error prone than managing and updating post-deployment configuration manifests.
Thanks for your time and effort reading this, and for crossplane and the crossplane-gcp support in general!
The text was updated successfully, but these errors were encountered: