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: Allow VNet to be in a separate Resource Group #49725

Merged
merged 1 commit into from
Aug 10, 2017

Conversation

sylr
Copy link
Contributor

@sylr sylr commented Jul 27, 2017

What this PR does / why we need it:

This PR allows Kubernetes in an Azure context to use a VNet which is not in the same Resource Group as Kubernetes.

We need this because currently Azure Cloud Provider driver assumes that it should have a VNet for himself but if there is one thing that should be shared amongst Azure resources it's a VNet cause, well, things might want to talk to each other in a private network, don't you think ?

I guess this should we backported down to 1.6 branch.

Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged):

fixes #49577

Release note:

Azure: Allow VNet to be in a separate Resource Group.

@kubernetes/sig-azure
@kubernetes/sig-azure-pr-reviews

Define a new config VnetResourceGroup in order to be able to use a VNet
which is not in the same resource group as kubernetes.

Signed-off-by: Sylvain Rabot <[email protected]>
@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://github.com/kubernetes/kubernetes/wiki/CLA-FAQ 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 email the CNCF helpdesk: [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 sig/azure cncf-cla: no Indicates the PR's author has not signed the CNCF CLA. needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Jul 27, 2017
@k8s-ci-robot
Copy link
Contributor

Hi @sylr. 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.

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

@k8s-ci-robot
Copy link
Contributor

@sylr: Reiterating the mentions to trigger a notification:
@kubernetes/sig-azure-pr-reviews.

In response to this:

What this PR does / why we need it:

This PR allows Kubernetes in an Azure context to use a VNet which is not in the same Resource Group as Kubernetes.

We need this because currently Azure Cloud Provider driver assumes that it should have a VNet for himself but if there is one thing that should be shared amongst Azure resources it's a VNet cause, well, things might want to talk to each other in a private network, don't you think ?

I guess this should we backported down to 1.6 branch.

Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged):

fixes #49577

Release note:

NONE

@kubernetes/sig-azure
@kubernetes/sig-azure-pr-reviews

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-github-robot k8s-github-robot added size/S Denotes a PR that changes 10-29 lines, ignoring generated files. release-note-none Denotes a PR that doesn't merit a release note. labels Jul 27, 2017
@sylr
Copy link
Contributor Author

sylr commented Jul 28, 2017

/cc @colemickens @karataliu

@k8s-ci-robot
Copy link
Contributor

@sylr: GitHub didn't allow me to request PR reviews from the following users: karataliu.

Note that only kubernetes members can review this PR, and authors cannot review their own PRs.

In response to this:

/cc @colemickens @karataliu

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.

@sylr
Copy link
Contributor Author

sylr commented Jul 28, 2017

cncf-cla signed

@k8s-ci-robot k8s-ci-robot added cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. and removed cncf-cla: no Indicates the PR's author has not signed the CNCF CLA. labels Jul 28, 2017
sylr pushed a commit to sylr/acs-engine that referenced this pull request Jul 28, 2017
Add vnetResourceGroup config to /etc/kubernetes/azure.json in an effort
to make Kubernetes deployed with a Custom VNet configuration to be able
to create internal load balancer services when the VNet is not int the
same Resource Group as Kubernetes.

For this to work Kubernetes Azure driver must have the following patch:
kubernetes/kubernetes#49725

Signed-off-by: Sylvain Rabot <[email protected]>
@jdumars
Copy link
Member

jdumars commented Jul 28, 2017

I'm adding this to the SIG-Azure PR review section. If you could represent it at the next SIG-Azure meeting on 8/9 at 16:00 UTC, we can discuss it.

@brendandburns
Copy link
Contributor

/lgtm
/approve
/ok-to-test

@k8s-ci-robot k8s-ci-robot added lgtm "Looks good to me", indicates that a PR is ready to be merged. and removed needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Aug 9, 2017
@brendandburns
Copy link
Contributor

@colemickens fyi

@k8s-github-robot
Copy link

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: brendandburns, sylr

Associated issue: 49577

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

Needs approval from an approver in each of these OWNERS Files:

You can indicate your approval by writing /approve in a comment
You can cancel your approval by writing /approve cancel in a comment

@k8s-github-robot k8s-github-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Aug 9, 2017
@k8s-github-robot
Copy link

/test all [submit-queue is verifying that this PR is safe to merge]

@k8s-github-robot
Copy link

Automatic merge from submit-queue

@djsly
Copy link
Contributor

djsly commented Aug 10, 2017

@jdumars if you could also look for having it in 1.6.9 ... I know I'm asking for a lot but we just upgraded to 1.6. Not sure how fast we will be moving to 1.7.
We are using a separate Vnet as well.

If it can't be done, I would understand.

@jdumars
Copy link
Member

jdumars commented Aug 11, 2017

I'll work with @wojtek-t to see what is possible. @seanknox you feeling adventurous?

@jdumars
Copy link
Member

jdumars commented Aug 11, 2017

BTW thank you @sylr for this work! Welcome to the Azure community.

@sylr
Copy link
Contributor Author

sylr commented Aug 11, 2017

This PR should be cherrypick-candidate for release-1.6 & release-1.7 according to me.

@wojtek-t
Copy link
Member

@jdumars - please prepare a cherrypick for it, I'm fine with that.

@seanknox
Copy link

I'm game to cherry pick. Let me know. @jdumars @wojtek-t

@jdumars
Copy link
Member

jdumars commented Aug 15, 2017

@seanknox make it so!

@enisoc enisoc added release-note Denotes a PR that will be considered when it comes time to generate release notes. and removed release-note-none Denotes a PR that doesn't merit a release note. labels Aug 15, 2017
k8s-github-robot pushed a commit that referenced this pull request Aug 15, 2017
…25-upstream-release-1.6

Automatic merge from submit-queue

Automated cherry pick of #49725

Cherry pick of #49725 on release-1.6.

#49725: Azure: Allow VNet to be in a separate Resource Group
k8s-github-robot pushed a commit that referenced this pull request Aug 16, 2017
…25-upstream-release-1.7

Automatic merge from submit-queue

Automated cherry pick of #49725

Cherry pick of #49725 on release-1.7.

#49725: Azure: Allow VNet to be in a separate Resource Group
@dcieslak19973
Copy link

I still am experiencing this problem in 1.7.4

@jdumars
Copy link
Member

jdumars commented Aug 23, 2017

@sylr are you able to help @dcieslak19973 with the implementation details if needed?

@sylr
Copy link
Contributor Author

sylr commented Aug 23, 2017

@dcieslak19973 You need to edit /etc/kubernetes/azure.json on the masters and add the property vnetResourceGroup

@dcieslak19973
Copy link

Thanks; I'll check with the acs-engine folks and see if they are doing that when provisioning the cluster.

sylr pushed a commit to sylr/acs-engine that referenced this pull request Aug 29, 2017
Add vnetResourceGroup config to /etc/kubernetes/azure.json in an effort
to make Kubernetes deployed with a Custom VNet configuration to be able
to create internal load balancer services when the VNet is not int the
same Resource Group as Kubernetes.

For this to work Kubernetes Azure driver must have the following patch:
kubernetes/kubernetes#49725

Signed-off-by: Sylvain Rabot <[email protected]>
sylr pushed a commit to sylr/acs-engine that referenced this pull request Oct 5, 2017
Add vnetResourceGroup config to /etc/kubernetes/azure.json in an effort
to make Kubernetes deployed with a Custom VNet configuration to be able
to create internal load balancer services when the VNet is not int the
same Resource Group as Kubernetes.

For this to work Kubernetes Azure driver must have the following patch:
kubernetes/kubernetes#49725

Signed-off-by: Sylvain Rabot <[email protected]>
jackfrancis pushed a commit to Azure/acs-engine that referenced this pull request Oct 9, 2017
* Improve Custom VNet support

Add vnetResourceGroup config to /etc/kubernetes/azure.json in an effort
to make Kubernetes deployed with a Custom VNet configuration to be able
to create internal load balancer services when the VNet is not int the
same Resource Group as Kubernetes.

For this to work Kubernetes Azure driver must have the following patch:
kubernetes/kubernetes#49725

Signed-off-by: Sylvain Rabot <[email protected]>

* rebase errata
@sylr sylr deleted the vnet branch August 24, 2018 11:34
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. 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. release-note Denotes a PR that will be considered when it comes time to generate release notes. size/S Denotes a PR that changes 10-29 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

K8s Service fails to create Azure internal load balancer