This repository has been archived by the owner on Oct 24, 2023. It is now read-only.
fix: trust Azure Stack's CA cert before pre-provision extensions are exectuted #2053
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jadarsie
changed the title
|
/azp run pr-e2e |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
@deaborch During this work spike were you able to validate that pre-provision extensions are working for public cloud? |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: deaborch, jackfrancis 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 |
|
@jackfrancis haven't been able to test on azure yet as I am looking into getting the telemetry fix up |
This was referenced Oct 9, 2019
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Reason for Change:
Cluster pre-provisioning was failing on Azurestack due to an untrusted certificate on the host preventing the pre-provisioning scripts from being downloaded
Issue Fixed:
Requirements:
Notes: