V2.1 Azure Reference Implementation - Streamline install process #4
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.
This PR is created to address the following Issue in the CNOE repo: #3
Problem Statement
The current Azure Reference Implementation does not provision the cloud resources in the most cloud native way.
Specifically:
(a) The Key Vault and Crossplane workload identity are currently created using AZ commands locally.
(b) There is currently too much logic in the Task File to handle the cloud resource creation and deletion.
Possible Solution
We believe that we can improve the cloud resource provisioning to take better advantage of cloud native tools by:
(i) Remove the dependency of running local commands to provision the cloud resources by using the Kind cluster.
(ii) Use the local Kind cluster to Bootstrap some of the Cloud resource provisioning, and the CNOE installation on AKS.