Skip to content

use old LB DNS format when teamId prefix is disabled #2011

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

Merged
merged 4 commits into from
Aug 25, 2022
Merged

Conversation

FxKu
Copy link
Member

@FxKu FxKu commented Aug 25, 2022

With #2001 merged we dropped the teamId prefix constraint for cluster names and deprecated the ClusterName field of the Postgresql type assuming it was not used somewhere else. Turns out, it is used for LoadBalancer service's external DNS name and ClusterStatus API.

This PR will set this field again when clusters are added to the operator's internal cluster list.

If we would continue to use the Spec.ClusterName for the LB DNS names they would break when disabling the team Id constraint. Therefore, we should continue to use old format when the cluster name starts with the team ID. external-dns supports multiple names per annotation, separated by comma.

@FxKu FxKu added this to the 1.9 milestone Aug 25, 2022
@Jan-M
Copy link
Member

Jan-M commented Aug 25, 2022

👍

@Jan-M
Copy link
Member

Jan-M commented Aug 25, 2022

👍

1 similar comment
@FxKu
Copy link
Member Author

FxKu commented Aug 25, 2022

👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants