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

Azure Stack Hub HybridEnvironment Support #5201

Open
4 tasks
patrickdillon opened this issue Oct 23, 2024 · 1 comment
Open
4 tasks

Azure Stack Hub HybridEnvironment Support #5201

patrickdillon opened this issue Oct 23, 2024 · 1 comment
Labels
kind/feature Categorizes issue or PR as related to a new feature.

Comments

@patrickdillon
Copy link

/kind feature

Describe the solution you'd like
Support using CAPZ to provision clusters on Azure Stack Hub.

Anything else you would like to add:
Achieving this goal would entail:

  • Adding Azure Stack Cloud (or HybridEnvironment) as a valid AzureEnvironment
  • Configuring cloud endpoints for the azure stack environment
  • Adding support for Basic Load Balancers (only supported LB on Azure Stack Hub)
  • Updating API version to a compatible profile as necessary (I believe this is only needed for resources that are not provisioned using ASO, so we can either migrate them to ASO or update the profiles. I'm currently working through NSGs, not sure if more are needed).

Environment:

  • cluster-api-provider-azure version:
  • Kubernetes version: (use kubectl version):
  • OS (e.g. from /etc/os-release):
@k8s-ci-robot k8s-ci-robot added the kind/feature Categorizes issue or PR as related to a new feature. label Oct 23, 2024
@nojnhuh
Copy link
Contributor

nojnhuh commented Oct 25, 2024

FYI @mboersma I think this will probably intersect with #4780.

I see ASO exposes only the AZURE_AUTHORITY_HOST, AZURE_RESOURCE_MANAGER_ENDPOINT, and AZURE_RESOURCE_MANAGER_AUDIENCE variables instead what CAPZ does now with the pre-baked sets of those for public cloud, China, Gov cloud, etc. @patrickdillon Would a way to set the equivalents of those variables in CAPZ be sufficient?

And since CAPZ would ultimately have to pass this config along to ASO, we should iron out Azure/azure-service-operator#3447 first before we commit to any API changes in CAPZ.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature.
Projects
Status: Todo
Development

No branches or pull requests

3 participants