-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
Add Azure support #10114
Conversation
Welcome @kenji-cloudnatix! |
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 Once the patch is verified, the new status will be reflected by the 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. |
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.
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. |
d21625b
to
544258a
Compare
There was a problem hiding this 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.
pkg/apis/kops/v1alpha2/cluster.go
Outdated
// 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"` |
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
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.
Thanks for the review. Yes, let me talk internally to get CLA signed. |
@kenji-cloudnatix any update on signing the CLA? |
Sorry for the delay, we've been talking internally, but no update yet. Will given an update in a few days.. |
Hey @kenji-cloudnatix, how are things going? Any news? 😄 |
Sorry, no update yet.. :( I pinged the team again. Hopefully this will get resolved today or tomorrow.. |
Sorry again for taking a long time, but I've signed CLA. Will rebase the PR tomorrow. Thanks! |
That's great! Thanks @kenji-cloudnatix. |
544258a
to
8c06680
Compare
Sure! Filed #10412 . Adding a "getting started doc". |
d8c9455
to
412f237
Compare
There was a problem hiding this 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.
There was a problem hiding this 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 !
There was a problem hiding this 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
Outdated
\``` | ||
$ 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 | ||
\``` |
There was a problem hiding this comment.
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
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
fixed!
There was a problem hiding this 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.
docs/getting_started/azure.md
Outdated
\``` | ||
$ 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 | ||
\``` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
fixed!
8cc2951
to
87a27a6
Compare
/retest Any other approvers want to take a look at this? Otherwise I think it is ready to merge |
d9101ff
to
f57b0b2
Compare
f57b0b2
to
350f125
Compare
This commit contains all changes required to support Azure (kubernetes#3957).
350f125
to
a61caea
Compare
Thanks @kenji-cloudnatix, time to merge :) |
[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 |
@kenji-cloudnatix THANKS!!! This as been a long time coming! |
Wowie! Thanks gang! <3 |
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.