Skip to content

Conversation

@FxKu
Copy link
Member

@FxKu FxKu commented Jan 25, 2023

fixes #2180

Introduced two new functions: generatePoolerServiceAnnotations for the DNS annotation used for LBs and getCustomServiceAnnotations which is shared for all services. Because pooler unit tests need quite some refactoring, the annotations are tested in e2e suite.

Functions masterDNSName and replicaDNSName now take the cluster name as argument, to make them reusable for pooler DNS name resolving

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

Jan-M commented Jan 26, 2023

Risk of breaking existing setups with change of DNS name for pooler LB. Feature added in 1.8. Felix will check.

@FxKu
Copy link
Member Author

FxKu commented Jan 26, 2023

So far in order to get the DNS entry for the pooler LB one had to enable the normal LB as well because generateConnectionPoolerService calls generateServiceAnnotations function used also for the other services. This function does not check pooler LBs.

So then you end up with two services using the same DNS and you don't know the route a request will take, right? Not sure, how many have really used the feature because of that? And as the normal LB has to be enabled for the DNS to be there, we can be sure that connections still work via the master|replica service.

@FxKu
Copy link
Member Author

FxKu commented Jan 27, 2023

👍

1 similar comment
@idanovinda
Copy link
Member

👍

@FxKu FxKu merged commit c9cada6 into master Jan 27, 2023
@FxKu FxKu deleted the pooler-lb-dns branch January 27, 2023 11:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Identical external-dns hostnames for load balancer type services for the master and the master pooler

4 participants