Skip to content
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

Automate AKS features available in ASO #3629

Closed
Tracked by #3446
dtzar opened this issue Jun 15, 2023 · 4 comments · Fixed by #4527
Closed
Tracked by #3446

Automate AKS features available in ASO #3629

dtzar opened this issue Jun 15, 2023 · 4 comments · Fixed by #4527
Assignees
Labels
area/managedclusters Issues related to managed AKS clusters created through the CAPZ ManagedCluster Type kind/feature Categorizes issue or PR as related to a new feature. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. size/XL Denotes a PR that changes 500-999 lines, ignoring generated files.

Comments

@dtzar
Copy link
Contributor

dtzar commented Jun 15, 2023

/kind feature

Describe the solution you'd like
As a user of CAPZ I would like the ability to provision all features available in AKS as soon as they are made available.

Even once we switch to the dependency of using ASO for AKS provisioning, all features present in ASO will take individual coding work to be able to be utilized in CAPZ. Since the features in AKS rapidly update (see comment on #2625), it would be ideal to have a mechanism for people to access all the available options in ASO via CAPZ via some coding mechanism which auto generates the code for it to work.

@k8s-ci-robot k8s-ci-robot added the kind/feature Categorizes issue or PR as related to a new feature. label Jun 15, 2023
@dtzar dtzar added the area/managedclusters Issues related to managed AKS clusters created through the CAPZ ManagedCluster Type label Jun 15, 2023
@dtzar dtzar added size/XL Denotes a PR that changes 500-999 lines, ignoring generated files. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. labels Sep 28, 2023
@dtzar dtzar moved this to Todo in CAPZ Planning Sep 28, 2023
@dtzar
Copy link
Contributor Author

dtzar commented Sep 28, 2023

Prerequisites for this are #2625 and #3529

@nojnhuh
Copy link
Contributor

nojnhuh commented Nov 20, 2023

/assign

@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Feb 18, 2024
@nawazkh
Copy link
Member

nawazkh commented Feb 20, 2024

/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Feb 20, 2024
@github-project-automation github-project-automation bot moved this from Todo to Done in CAPZ Planning Feb 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/managedclusters Issues related to managed AKS clusters created through the CAPZ ManagedCluster Type kind/feature Categorizes issue or PR as related to a new feature. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. size/XL Denotes a PR that changes 500-999 lines, ignoring generated files.
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

5 participants