-
Notifications
You must be signed in to change notification settings - Fork 518
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
feat (templates): [cluster] migrate to bicep #302
Conversation
…entity highlights: - resource group: networking - spoke - assign roles at the spoke ingress and cluster nodes subnets level
… at the subscription level highlights: - resource group: aks cluster
44eebd5
to
7a075c7
Compare
7a075c7
to
0f9bfd0
Compare
…s and other minors
This reverts commit a1d83e8.
f8b2d8b
to
6610084
Compare
w00t @ckittel current version is working. |
Nice work! Just one more small observation ^, and this can be merged. |
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.
LGTM, given the above feedback, @ferantivero. Okay to merge? If so, can you update the PR body with any "additional changes" made (like general API version updates)
Great job, @ferantivero & @ckittel. Thank you guys! |
closes: #571187
WHY
we wanted to move our last ARM json template (cluster-stamp) to bicep, so we fully support this lang for deploying from the AKS Baseline.
What Changed?
Ensure
deploymentsexisting
resources.HOW to Test?
You should be able to follow the instructions and successfully deploy an AKS Baseline cluster having a full bicep experience along the road.