-
Notifications
You must be signed in to change notification settings - Fork 191
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
Bug 2032566: Azure: Add Support for Azure Stack Hub #686
Bug 2032566: Azure: Add Support for Azure Stack Hub #686
Conversation
/hold Azure Stack CI should be done soon openshift/release#24394 but I doubt in time for this PR. |
/test verify
Doesn't look related to this changeset... |
|
Azure Stack is on-prem Azure, so the ARM endpoint, which is known in advance for public Azure or Government Azure, must be provided through configuration. This commit adds support for Azure Stack by checking the infrastructure object to determine the cloud and in the case of Azure Stack, uses the provided ARMEndpoint.
995fcfa
to
5c5fe85
Compare
I made it past the initial error in testing but I hit this issue and have updated accordingly. |
/test ? |
@patrickdillon: The following commands are available to trigger required jobs:
The following commands are available to trigger optional jobs:
Use
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. |
/test e2e-azure |
Azure SDK Profile ensures compatibility with Azure Stack.
/test e2e-azure |
/hold cancel
|
/test e2e-azure |
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.
Functionally, these changes look correct to me.
/test e2e-azure |
/test verify |
5061b6d
to
5786874
Compare
verify test was supposedly fixed in openshift/api-machinery-go#58 but my retest failed. Just force pushed with no changes to see if that refreshes the ci namespace or something |
/test e2e-azure |
Oh, of course it wouldn't fix it until it is vendored in. Doh. #687 will take care of it. /test e2e-azure These passed earlier. Flaking now, methinks. |
These are build failures:
|
/retitle Bug 2032566: Azure: Add Support for Azure Stack Hub |
@patrickdillon: This pull request references Bugzilla bug 2032566, which is valid. The bug has been moved to the POST state. The bug has been updated to refer to the pull request using the external bug tracker. 3 validation(s) were run on this bug
Requesting review from QA contact: 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. |
/bugzilla refresh |
@patrickdillon: This pull request references Bugzilla bug 2032566, which is valid. 3 validation(s) were run on this bug
Requesting review from QA contact: 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. |
The ingress operator itself doesn't require that both private and public zones be configured; the operator will publish records in the zones if they're specified, and it will not complain if a zone is not specified. On some platforms (such as AWS), it is necessary to configure records in both the public zone and the private zone because otherwise a wildcard DNS record (such as |
If e2e-azure-operator passes, |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: Miciah, patrickdillon The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Seeing |
/bugzilla refresh |
@patrickdillon: This pull request references Bugzilla bug 2032566, which is valid. 3 validation(s) were run on this bug
Requesting review from QA contact: 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. |
/retest-required Please review the full test history for this PR and help us cut down flakes. |
4 similar comments
/retest-required Please review the full test history for this PR and help us cut down flakes. |
/retest-required Please review the full test history for this PR and help us cut down flakes. |
/retest-required Please review the full test history for this PR and help us cut down flakes. |
/retest-required Please review the full test history for this PR and help us cut down flakes. |
|
@patrickdillon: All pull requests linked via external trackers have merged: Bugzilla bug 2032566 has been moved to the MODIFIED state. 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. |
@patrickdillon: all tests passed! 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. |
@patrickdillon: new pull request created: #690 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. |
Azure Stack is on-prem Azure, so the ARM endpoint, which is known in advance for public Azure or Government Azure, must be provided through configuration. This commit adds support for Azure Stack by checking the infrastructure object to determine the cloud and in the case of Azure Stack, uses the provided ARMEndpoint.
I think this is a bug because we released UPI in 4.9, and this should be supported in UPI. I will open a BZ for backporting in a moment.
Without this PR, Azure Stack is failing like this:
Also, at the moment, the installer does not create a privateDNSZone in the DNS manifest for Azure Stack (because Azure Stack does not have private DNS zones). Does the cluster-ingress-operator require BOTH a private and public zone in order to add *.apps?