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

GCP: Support for ability to specify manual subnet #183

jeenalshah opened this issue Mar 1, 2018 · 5 comments

GCP: Support for ability to specify manual subnet #183

jeenalshah opened this issue Mar 1, 2018 · 5 comments


Copy link

@jeenalshah jeenalshah commented Mar 1, 2018

Deploying a cluster with manual subnets, the cloud-provider.ini needs to specify the subnetwork-name to be able to deploy
a Service of type LoadBalancer with the GCE annotation of type Internal.

Without this, the IP address isn't correctly assigned on a subnet in the VPC.

The erb template

doesn't have this field nor does the
BOSH job spec
have an option for it.

cc @cholick

Copy link

@cf-gitbot cf-gitbot commented Mar 1, 2018

We have created an issue in Pivotal Tracker to manage this:

The labels on this github issue will be updated when the story is started.

@karampok karampok self-assigned this Mar 16, 2018
Copy link

@karampok karampok commented Mar 16, 2018

Hi @jshah-pivotal ,
could you elaborate a bit more the issue?

"Deploying with manual subnets", where/what is the deploying refers to? bosh?

What is the error you get? or what is the output of the kubectl commands that shows
`the IP address isn't correctly assigned on a subnet in the VPC"


Copy link

@jeenalshah jeenalshah commented Mar 16, 2018

Bosh is the one deploying with manual subnets.
This is subnet config we are talking about.

add subnetwork-name here.

In the logs we see that subnet name comes out empty. When loadbalancer is created there is no frontend. It does not get IP assigned to it.

Copy link

@bengtrj bengtrj commented Aug 13, 2018

This is a blocker for the Tracker team now. They're evaluating PKS (that depends on CFCR) by creating memcached service as an internal LoadBalancer and we had the same issue on GCP.

While K8S tries to create the LoadBalancer service on GCP, it needs the specific subnetwork-name - and since the config is not made available by CFCR, the service deployment fails.

A workaround that worked for us was ssh-ing into the master node, editing the cloud-config.ini located at /var/vcap/jobs/kube-controller-manager/config, and issuing a monit restart on the kube-controller-manager process. By looking at kubo-release code, the appropriate file to add the config would be the kube-apiserver/templates/config/cloud-provider.ini.erb because it's the one used by all other jobs on the release.

Related K8S issue:

@karampok karampok removed their assignment Aug 16, 2018
@cf-gitbot cf-gitbot added scheduled and removed unscheduled labels Aug 20, 2018
@cf-gitbot cf-gitbot added accepted and removed delivered labels Sep 20, 2018
Copy link

@alex-slynko alex-slynko commented Oct 19, 2018

The fix is in 0.23 release

@cf-gitbot cf-gitbot removed the accepted label Oct 19, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
5 participants
You can’t perform that action at this time.