-
Notifications
You must be signed in to change notification settings - Fork 5
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
Resolve DNS Issues with Azure #6
Comments
@TannerMoore Do you have an update on this task? |
Unable to get feedback from Paul from Chevron. We need a service principle. [email protected] |
We need to deploy our own Azure AD tenant. This will ultimately remove the obstacle have this deployed. |
@arthomasredhat I have a solution for this in route53. We can create subdomains and delegate to other groups. Sync up with me. |
I'm planning to redeploy OCP with a new domain name |
I heard back from Christopher and he's ok to create an SP for us. Let me know if we still have a need for one in their tenant after deployment. |
Yes, we need the tenant after the deployment. Per @codekow, we have route 53 set up. |
FYI... new OCP console is here https://console-openshift-console.apps.hou.edgelab.online/ |
Need Access to Route 53 and discuss route creation automation |
My plan is to create subdomains and let individual groups manage those subdomains however they want. Please help me understand your use case so I can help setup a solution. |
Success Criteria: Setup principle role access to the Azure to ensure that we can configure the DNS settings appropriately
The text was updated successfully, but these errors were encountered: