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

Add Azure support #10114

Merged
merged 1 commit into from
Dec 21, 2020
Merged

Add Azure support #10114

merged 1 commit into from
Dec 21, 2020

Conversation

kenji-cloudnatix
Copy link
Contributor

This commit contains all changes required to support Azure
(#3957).

As we discussed in the ticket, this helps understand the entire changes needed. Very unlikely to merge this PR as-is.

One thing I wasn't sure about was what's the best way to have Azure specific configuration in the cluster spec. For example, it makes sense to have Resource Group in a cluster spec so that users can build a k8s cluster in their existing Resource Group. On the other hand, adding Azure specific config to the clustrer spec doesn't look good. Currently I just defined AzureSpec inside the cluster spec.

@k8s-ci-robot
Copy link
Contributor

Welcome @kenji-cloudnatix!

It looks like this is your first PR to kubernetes/kops 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes/kops has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

@k8s-ci-robot
Copy link
Contributor

Hi @kenji-cloudnatix. Thanks for your PR.

I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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/test-infra repository.

@k8s-ci-robot k8s-ci-robot added the needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. label Oct 26, 2020
@k8s-ci-robot
Copy link
Contributor

Thanks for your pull request. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please follow instructions at https://git.k8s.io/community/CLA.md#the-contributor-license-agreement to sign the CLA.

It may take a couple minutes for the CLA signature to be fully registered; after that, please reply here with a new comment and we'll verify. Thanks.


  • If you've already signed a CLA, it's possible we don't have your GitHub username or you're using a different email address. Check your existing CLA data and verify that your email is set on your git commits.
  • If you signed the CLA as a corporation, please sign in with your organization's credentials at https://identity.linuxfoundation.org/projects/cncf to be authorized.
  • If you have done the above and are still having issues with the CLA being reported as unsigned, please log a ticket with the Linux Foundation Helpdesk: https://support.linuxfoundation.org/
  • Should you encounter any issues with the Linux Foundation Helpdesk, send a message to the backup e-mail support address at: [email protected]

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/test-infra repository. I understand the commands that are listed here.

@k8s-ci-robot k8s-ci-robot added cncf-cla: no Indicates the PR's author has not signed the CNCF CLA. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. labels Oct 26, 2020
Copy link
Member

@rifelpet rifelpet left a comment

Choose a reason for hiding this comment

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

I left a few minor comments just from a quick scan through but I'll give a closer look sometime soon. You'll also need to sign the CLA with your github email according to one of the above k8s-ci-robot comments. Once you do that we can enable CI testing, and feel free to open the VFS PR next.

upup/pkg/fi/cloudup/azure/status.go Outdated Show resolved Hide resolved
docs/cli/kops_create_cluster.md Outdated Show resolved Hide resolved
// empty, kops will not create a new resource group, and
// it will just reuse the existing resource group of the name.
// This follows the model that kops takes for AWS VPC.
ResourceGroupName string `json:"resourceGroupName,omitempty"`
Copy link
Member

Choose a reason for hiding this comment

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

Optional API fields typically use pointers to more easily denote nil as being unset.

Copy link
Member

Choose a reason for hiding this comment

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

I don't agree that is a necessary pattern. Using a pointer is only necessary when it is useful to distinguish the default value from an explicitly specified zero value. In this case an exiting resource group named with the empty string would not be reasonable.

@hakman hakman requested review from justinsb, mikesplain and hakman and removed request for joshbranham and gjtempleton October 27, 2020 04:41
@kenji-cloudnatix
Copy link
Contributor Author

Thanks for the review. Yes, let me talk internally to get CLA signed.

@k8s-ci-robot k8s-ci-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Oct 30, 2020
@rifelpet
Copy link
Member

rifelpet commented Nov 2, 2020

@kenji-cloudnatix any update on signing the CLA?

@kenji-cloudnatix
Copy link
Contributor Author

Sorry for the delay, we've been talking internally, but no update yet. Will given an update in a few days..

@hakman
Copy link
Member

hakman commented Nov 14, 2020

Hey @kenji-cloudnatix, how are things going? Any news? 😄

@kenji-cloudnatix
Copy link
Contributor Author

Sorry, no update yet.. :( I pinged the team again. Hopefully this will get resolved today or tomorrow..

@kenji-cloudnatix
Copy link
Contributor Author

Sorry again for taking a long time, but I've signed CLA. Will rebase the PR tomorrow. Thanks!

@hakman
Copy link
Member

hakman commented Nov 17, 2020

That's great! Thanks @kenji-cloudnatix.

@kenji-cloudnatix
Copy link
Contributor Author

Sure! Filed #10412 . Adding a "getting started doc".

@k8s-ci-robot k8s-ci-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Dec 11, 2020
Copy link
Member

@rifelpet rifelpet left a comment

Choose a reason for hiding this comment

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

Thanks for the docs update! A few minor things to make it more concise. Hopefully you understand the "```" issues I had with github suggestions. I'm hoping this will be the final review before we can merge.

docs/getting_started/azure.md Outdated Show resolved Hide resolved
docs/getting_started/azure.md Outdated Show resolved Hide resolved
docs/getting_started/azure.md Outdated Show resolved Hide resolved
docs/getting_started/azure.md Outdated Show resolved Hide resolved
docs/getting_started/azure.md Outdated Show resolved Hide resolved
docs/getting_started/azure.md Outdated Show resolved Hide resolved
docs/getting_started/azure.md Outdated Show resolved Hide resolved
docs/getting_started/azure.md Outdated Show resolved Hide resolved
docs/getting_started/azure.md Outdated Show resolved Hide resolved
pkg/apis/kops/componentconfig.go Show resolved Hide resolved
Copy link
Contributor Author

@kenji-cloudnatix kenji-cloudnatix left a comment

Choose a reason for hiding this comment

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

Thanks for the quick and detailed review, @rifelpet !

docs/getting_started/azure.md Outdated Show resolved Hide resolved
Copy link
Member

@rifelpet rifelpet left a comment

Choose a reason for hiding this comment

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

A few formatting issues to address, mostly around my inability to suggest the exact changes through GH's suggestions features :) and I forgot that you'll need to add the new page to the docs site menu too

docs/getting_started/azure.md Show resolved Hide resolved
Comment on lines 199 to 212
\```
$ kops update cluster \
--name my-azure.k8s.local
\```

Now add the `--yes` flag to have kOps provision the resources
and create the cluster. This will also add a kubeconfig context
for the cluster.

\```
$ kops update cluster \
--name my-azure.k8s.local \
--yes
\```
Copy link
Member

Choose a reason for hiding this comment

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

these code blocks arent working because of the \ in front of the triple backticks

Copy link
Contributor Author

Choose a reason for hiding this comment

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

fixed!

Copy link
Contributor Author

@kenji-cloudnatix kenji-cloudnatix left a comment

Choose a reason for hiding this comment

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

Thanks! Updated mkdocs.yml as well.

Comment on lines 199 to 212
\```
$ kops update cluster \
--name my-azure.k8s.local
\```

Now add the `--yes` flag to have kOps provision the resources
and create the cluster. This will also add a kubeconfig context
for the cluster.

\```
$ kops update cluster \
--name my-azure.k8s.local \
--yes
\```
Copy link
Contributor Author

Choose a reason for hiding this comment

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

fixed!

docs/getting_started/azure.md Show resolved Hide resolved
@rifelpet
Copy link
Member

/retest
/lgtm

Any other approvers want to take a look at this? Otherwise I think it is ready to merge

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Dec 14, 2020
hack/.packages Outdated Show resolved Hide resolved
@k8s-ci-robot k8s-ci-robot removed the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Dec 21, 2020
This commit contains all changes required to support Azure
(kubernetes#3957).
@hakman
Copy link
Member

hakman commented Dec 21, 2020

Thanks @kenji-cloudnatix, time to merge :)
/lgtm
/approve

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

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: hakman, kenji-cloudnatix

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

The pull request process is described 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 approved Indicates a PR has been approved by an approver from all required OWNERS files. label Dec 21, 2020
@k8s-ci-robot k8s-ci-robot merged commit 4eaa97b into kubernetes:master Dec 21, 2020
@k8s-ci-robot k8s-ci-robot added this to the v1.20 milestone Dec 21, 2020
@kenji-cloudnatix kenji-cloudnatix deleted the azure2 branch December 21, 2020 17:16
@kenji-cloudnatix
Copy link
Contributor Author

Thanks for all the efforts for code review, @rifelpet @hakman !

@chrislovecnm
Copy link
Contributor

@kenji-cloudnatix THANKS!!! This as been a long time coming!

@rendhalver
Copy link

Wowie! Thanks gang! <3

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. area/addons area/api area/documentation area/kops-controller area/nodeup cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. lgtm "Looks good to me", indicates that a PR is ready to be merged. ok-to-test Indicates a non-member PR verified by an org member that is safe to test. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

8 participants