Skip to content
This repository has been archived by the owner on May 22, 2020. It is now read-only.

Enable GCP provider specific logic in the Kubernetes API. #674

Closed
krousey opened this issue Apr 10, 2018 · 5 comments
Closed

Enable GCP provider specific logic in the Kubernetes API. #674

krousey opened this issue Apr 10, 2018 · 5 comments
Assignees
@krousey
Labels
cluster-api-gcp
Milestone
cluster-api-alpha...

Comments

@krousey
Copy link
Contributor

krousey commented Apr 10, 2018

The Google provider implementation installs Kubernetes without any GCP cloud provider code enabled. This code is needed to enable several key features:

  • Loadbalancing
  • Persistent Volumes
  • Ingresses
  • GCP routes for container networking (no need for CNI)

This largely is making sure the correct flags are specified on the existing k8s components and also installing additional controllers (I think the ingress controller is separate). Also, the master VMs have to have the appropriate permissions to perform these operations.
@rsdcastro
Copy link

/cc @mkjelland

@mkjelland
Copy link

I'll take a look!

@krousey
Copy link
Contributor Author

krousey commented Apr 10, 2018

self-assigning for now since @mkjelland isn't part of the k8s org.

/assign @krousey

@rsdcastro
Copy link

/cc @kawych

mkjelland added a commit to mkjelland/kube-deploy that referenced this issue Apr 13, 2018
@mkjelland
Adding cloud provider support for gce to enable load balancer and per…
a114285 
…sistent disk provisioning

Issue kubernetes-retired#674
@rsdcastro rsdcastro mentioned this issue Apr 17, 2018
Closed
@rsdcastro
Copy link

This issue was moved to kubernetes-sigs/cluster-api#81

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@krousey krousey

Labels
cluster-api-gcp
Projects
None yet
Milestone
cluster-api-alpha-implementation
Development

No branches or pull requests
3 participants
@krousey @rsdcastro @mkjelland