-
Notifications
You must be signed in to change notification settings - Fork 224
fix: properly mutate flux ocirepo and helmrepo objects when using the registry proxy #4486
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
base: main
Are you sure you want to change the base?
Conversation
Signed-off-by: Austin Abro <[email protected]>
✅ Deploy Preview for zarf-docs canceled.
|
Codecov Report❌ Patch coverage is
... and 5 files with indirect coverage changes 🚀 New features to boost your workflow:
|
Signed-off-by: Austin Abro <[email protected]>
Signed-off-by: Austin Abro <[email protected]>
Signed-off-by: Austin Abro <[email protected]>
Signed-off-by: Austin Abro <[email protected]>
| } | ||
|
|
||
| return fmt.Sprintf("%s:%d", svc.Spec.ClusterIP, port), nil | ||
| return fmt.Sprintf("%s.%s.svc.cluster.local:%d", svc.Name, svc.Namespace, port), nil |
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.
Changing behavior of the nodeport service as well. I cannot think of any reason we initially used clusterip. Seems like hostname is a more consistent alternative.
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.
Also a little un-educated guess, but I wonder if it is because not every cluster uses cluster.local as its FQDN?
Description
WIP
Related Issue
Fixes #4474
Checklist before merging