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

Rename AKS provider to Azure #2864

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

Jont828
Copy link
Contributor

@Jont828 Jont828 commented Sep 5, 2024

/kind feature

What type of PR is this?

What this PR does / why we need it: Rename the AKS provider to Azure since it works with non-AKS Azure clusters (such as CAPZ) as well.

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

@k8s-ci-robot k8s-ci-robot added kind/feature Categorizes issue or PR as related to a new feature. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. labels Sep 5, 2024
@k8s-ci-robot k8s-ci-robot added the size/S Denotes a PR that changes 10-29 lines, ignoring generated files. label Sep 5, 2024
Copy link
Contributor

@mboersma mboersma left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could you also update the README for CL2 to mention azure as an option for provider?

clusterloader2/pkg/provider/provider.go Outdated Show resolved Hide resolved
@jackfrancis
Copy link

cc @JohnRusk

Do you have any thoughts on this change?

@JohnRusk
Copy link

JohnRusk commented Sep 13, 2024

I think the stated rationale makes sense.

The only risk I can think of would be if in fact this statement wasn't always correct: "since it works with non-AKS Azure clusters (such as CAPZ) as well". I.e. if in fact there are expected to be any kind of Azure cluster that it does not support - is that a problem? E.g. does it create an implied mainteance burden to modify this so that it does support them?

But I think my concern there is very minor, and unlikely to any reason to reject the PR. So, if you're happy with it as it stands, so am I @jackfrancis .

@jackfrancis
Copy link

The only risk I can think of would be if in fact this statement wasn't always correct: "since it works with non-AKS Azure clusters (such as CAPZ) as well". I.e. if in fact there are expected to be any kind of Azure cluster that it does not support - is that a problem? E.g. does it create an implied mainteance burden to modify this so that it does support them?

I think that is a valid point, and I would argue that if we discover this to be true in the future (novel Kubernetes + Azure infra use case) that the provider doesn't support, we want to support it. I'm committed to that level of support.

@JohnRusk
Copy link

Sounds good to me @jackfrancis

@k8s-ci-robot k8s-ci-robot added needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. size/M Denotes a PR that changes 30-99 lines, ignoring generated files. and removed size/S Denotes a PR that changes 10-29 lines, ignoring generated files. labels Sep 20, 2024
@mboersma
Copy link
Contributor

lgtm, but needs a rebase.

@mboersma
Copy link
Contributor

@Jont828 this needs to be rebased.

@Jont828
Copy link
Contributor Author

Jont828 commented Oct 2, 2024

@mboersma Done!

@k8s-ci-robot k8s-ci-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Oct 2, 2024
Copy link
Contributor

@mboersma mboersma left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Oct 3, 2024
@k8s-ci-robot k8s-ci-robot removed the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Oct 4, 2024
@Jont828
Copy link
Contributor Author

Jont828 commented Oct 4, 2024

@mboersma Just rebased it, shouldn't have changed anything.

Copy link
Contributor

@mboersma mboersma left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Oct 4, 2024
@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: Jont828, mboersma
Once this PR has been reviewed and has the lgtm label, please assign wojtek-t for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Nov 6, 2024
@k8s-ci-robot
Copy link
Contributor

PR needs rebase.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. kind/feature Categorizes issue or PR as related to a new feature. lgtm "Looks good to me", indicates that a PR is ready to be merged. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants