-
Notifications
You must be signed in to change notification settings - Fork 99
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
Fix coredns based exposure #799
Conversation
The issue was detected with AWS reference setup * The condition was not working as expected * It led to degraded state when we expected `k8gb-ns-*` DNSEndpoint IP addresses to be populated with exposed coredns service ip addresses Instead it was not detecting the rule and was populated by Ingress IPs creating non-obvious mess in the configuration. Signed-off-by: Yury Tsarev <yury.tsarev@absa.africa>
Related to #615 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@ytsarev this code renders
|
weirdly enough, the
while brew one:
this expression works on both versions, but I can't check if it's ok in the aws context:
|
@jkremser thanks for finding the working solution! I've checked the proper rendering with |
The issue was detected with AWS reference setup
k8gb-ns-*
DNSEndpointIP addresses to be populated with exposed coredns service ip addresses
Instead it was not detecting the rule and was populated by Ingress IPs
creating non-obvious mess in the configuration.
Signed-off-by: Yury Tsarev yury.tsarev@absa.africa