Replies: 0 comments 1 reply
-
@petenorth GitOps and external-dns operate independent control loops. Are you asking to conflate the two ideas into one? If yes, then why conflate? Thanks. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Taking the example of cert-manager. We can choose to deploy to a cluster with Helm and then create and Issuer resource. Some of the values provided to the Issuer will depend on resources outside of the cluster .
For example
https://cert-manager.io/docs/configuration/acme/dns01/azuredns/
When using GitOps the Issuer resource (and the cert-manager chart) will be present in the GitOps repo .
Should a GitOps technology provide a way to integrate with the cloud provider so that these parameters can be retrieved dynamically rather than being stored statically in the GitOps repo (directly from the cloud provider or from the infrastructure as code state)?
Or should a GitOps technology provide a standard way in which this information can be published to the GitOps repo ....
Beta Was this translation helpful? Give feedback.
All reactions