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

Consider switching to the out-of-tree Azure cloud-controller-manager #373

Closed
ialidzhikov opened this issue Sep 21, 2021 · 1 comment
Closed
Labels
area/control-plane Control plane related kind/enhancement Enhancement, improvement, extension lifecycle/stale Nobody worked on this for 6 months (will further age) platform/azure Microsoft Azure platform/infrastructure priority/3 Priority (lower number equals higher priority) status/closed Issue is closed (either delivered or triaged)

Comments

@ialidzhikov
Copy link
Member

How to categorize this issue?

/area control-plane
/kind enhancement
/priority 3
/platform azure

What would you like to be added:
Before #72, we were already using the out-of-tree Azure cloud-controller-manager for a short period of time. With #72, we switched to our fork of the in-tree Azure CCM as the out-of-tree one was still considered as alpha and not ready for production.

But things changed and out-of-tree CCM claims to be GA now:

cloud-provider-azure has been GA since v1.0.0

Why is this needed:
To get rid of our CCM fork (https://github.com/gardener/cloud-provider-azure) and all the maintenance effort related to it.

@ialidzhikov ialidzhikov added the kind/enhancement Enhancement, improvement, extension label Sep 21, 2021
@gardener-robot gardener-robot added area/control-plane Control plane related platform/azure Microsoft Azure platform/infrastructure priority/3 Priority (lower number equals higher priority) labels Sep 21, 2021
@gardener-robot gardener-robot added the lifecycle/stale Nobody worked on this for 6 months (will further age) label Mar 21, 2022
@ialidzhikov
Copy link
Member Author

Fixed with #431.

/close

@gardener-robot gardener-robot added the status/closed Issue is closed (either delivered or triaged) label May 5, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/control-plane Control plane related kind/enhancement Enhancement, improvement, extension lifecycle/stale Nobody worked on this for 6 months (will further age) platform/azure Microsoft Azure platform/infrastructure priority/3 Priority (lower number equals higher priority) status/closed Issue is closed (either delivered or triaged)
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants