Skip to content
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

The current public_dns zone in the GCP provider doesn't work #228

Open
nacx opened this issue Feb 10, 2023 · 0 comments
Open

The current public_dns zone in the GCP provider doesn't work #228

nacx opened this issue Feb 10, 2023 · 0 comments
Labels
bug Something isn't working

Comments

@nacx
Copy link
Member

nacx commented Feb 10, 2023

When deploying the management plane in GCP, there is a bit of flexibility when configuring the FQDN. Users can create a FQDN with the .private suffix to create an internal zone, and can use any other name that is not the gcp.cx.tetrate.info and a public DNS zone will be created.

However, that zone needs to be explicitly configured so that other projects (and clusters can see it), and this is something that needs to be done beforehand, by pointing the Domain to the nameservers in that zone. This breaks the CP deployment in GCP if using this approach.

In order to fix it, public zones should be assumed to exist (like we do with the shared one) instead of being created, and the project in which they exist should be configurable.
This is a small change I already fixed in my fork (last 3 files of this commit): nacx@bf8b200

@nacx nacx added the bug Something isn't working label Feb 10, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant