Skip to content

Only configure main domain as cluster-domain for legacy clusters #9677

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

Open
wants to merge 1 commit into
base: dev
Choose a base branch
from

Conversation

linki
Copy link
Member

@linki linki commented Jul 11, 2025

Internal discussion revealed that the cluster-domain argument is merely used to detect/filter Ingress/RouteGroup domains on per-stack resources. The main hostname of the stackset isn't affected by this setting.

Since we intend to stop supporting the main hostname variants for individual stacks on EKS clusters, we can just drop it entirely from the list to achieve that.

Users can still use the cluster-internal DNS domain to access individual stacks.

@linki linki added do-not-merge minor Minor changes, e.g. low risk config updates, changes that do not introduce a new API call. labels Jul 11, 2025
@linki linki force-pushed the stackset-eks branch 6 times, most recently from cdaf98f to b2efaed Compare July 15, 2025 12:31
@linki linki changed the title Don't configure main domain as cluster-domain only configure main domain as cluster-domain for legacy clusters Jul 15, 2025
@linki linki changed the title only configure main domain as cluster-domain for legacy clusters Only configure main domain as cluster-domain for legacy clusters Jul 15, 2025
@@ -26,6 +25,7 @@ metadata:
name: "{{{APPLICATION}}}-{{{COMPONENT}}}-config-provider-aws"
data:
CLUSTER_PROVIDER: "zalando-aws"
CLUSTER_DOMAIN_INTERNAL: "teapot-e2e.zalan.do"
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

CLUSTER_DOMAIN_INTERNAL is just the name of the variable to give a second cluster domain to stackset-controller. It doesn't actually need to be internal.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
do-not-merge minor Minor changes, e.g. low risk config updates, changes that do not introduce a new API call.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant