-
Notifications
You must be signed in to change notification settings - Fork 1.4k
CORS-2323: Allow users to bring their own custom DNS solution for API and API-Int #6829
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
Conversation
0b754da
to
dbcb9b2
Compare
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.
Probably need to add "TechPreview" here and in types, validate that tech preview feature set is active when this is provided.
pkg/types/installconfig.go
Outdated
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.
Do we need to know explicitly if it is "Disabled" or can we just assume that it is disabled when Enabled is not true ?
Issues go stale after 90d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle stale |
Stale issues rot after 30d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle rotten |
dbcb9b2
to
fdfd7c3
Compare
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
@sadasu: This pull request references CORS-2323 which is a valid jira issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/remove-lifecycle rotten |
5594f30
to
0bac87e
Compare
@sadasu: This pull request references CORS-2323 which is a valid jira issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
f9c3963
to
eb7d9a2
Compare
pkg/asset/cluster/tfvars.go
Outdated
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.
@sadasu per the code here, only BYO LB is not in this feature's scope yet, right?
Provide a way for customers to use their custom DNS solution in place of the one provided by the cloud platform. This requires the users to pre-create LBs for API and API-Int. The customer is also required to configure their DNS solution with entries for API and API-Int resolution.
3917ac3
to
a344d84
Compare
When user has provided the API and API-Int Load Balancers(LB) when a custom DNS solution is in use, configure these instead.
a344d84
to
ee9f519
Compare
@sadasu: The following tests failed, say
Full PR test history. Your PR dashboard. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
We are moving to a solution that depends on a self-hosted DNS. In that case, there would be no need for the customer to pre-create their LBs, thus making these changes obsolete. |
Based on Enhancement Proposal : openshift/enhancements#1400
OpenShift API PR: openshift/api#1397