-
-
Notifications
You must be signed in to change notification settings - Fork 323
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add public IPv4 address of Traefik to output #16
Conversation
Tried to merge this but it failed and had to revert it. Also, the type of LB is configured here. So not always going to be lb11. I understand what you are trying to achieve, maybe we can find a better way. |
This was just the name of the data source. The public IPv4 address will be fetched, based on the name |
Ok, I understand, will just change |
It did not work because the lb is automatically provisioned by the CCM, not through terraform. So there is no way I know of acquiring its IP unless we ask Kubernetes somehow. When deploying I get the following error:
|
@dhoppe If your concern is to have the lb IP to later configure DNS, this is easily solved by external-dns that can be installed in kube. |
You seem pretty advanced :) But just in case, gave an example of using external-dns at the end of issue #18 |
Hm. To be honest, the loadbalancer already existed when I tested this. Unfortunately my DNS provider is not supported by external-dns, yet. |
In that case, maybe there is a way to ask Kubernetes and grab the value, store it, and display that. Maybe with https://registry.terraform.io/providers/hashicorp/kubernetes/latest/docs |
This output might be required by other Terraform modules to manage the DNS records.