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.

Sign up for GitHub

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

Jump to bottom

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

Closed
rsdcastro opened this issue Apr 17, 2018 · 4 comments · Fixed by #141
Closed

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

rsdcastro opened this issue Apr 17, 2018 · 4 comments · Fixed by #141
Assignees
@krousey

Comments

@rsdcastro
Copy link

From @krousey on April 10, 2018 16:43

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.

Copied from original issue: kubernetes-retired/kube-deploy#674
@rsdcastro
Copy link
Author

/cc @mkjelland

@rsdcastro
Copy link
Author

From @mkjelland on April 10, 2018 16:49

I'll take a look!

@rsdcastro
Copy link
Author

From @krousey on April 10, 2018 16:50

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

/assign @krousey

@rsdcastro
Copy link
Author

/cc @kawych

@rsdcastro rsdcastro mentioned this issue Apr 17, 2018
Closed
@rsdcastro rsdcastro added this to the cluster-api-alpha-implementation milestone Apr 17, 2018
@kcoronado kcoronado mentioned this issue Apr 23, 2018
Merged
@kcoronado kcoronado mentioned this issue Apr 30, 2018
Merged
mkjelland added a commit to mkjelland/cluster-api that referenced this issue May 8, 2018
@mkjelland
Issue kubernetes-sigs#81:
62e0516 
- Create service accounts on cluster creation for master/worker nodes
- Add default storage class
- Start kubelet with gce cloud provider configuration
mkjelland added a commit to mkjelland/cluster-api that referenced this issue May 8, 2018
@mkjelland
Issue kubernetes-sigs#81
3e3813e 
Adding instructions for deploying ingress controller
@mkjelland mkjelland mentioned this issue May 8, 2018
Merged
mkjelland added a commit that referenced this issue May 15, 2018
@mkjelland
Merge pull request #141 from mkjelland/gce-cloud-provider
4e00ee9 
Enable GCE cloud provider support: Issue #81
chuckha pushed a commit to chuckha/cluster-api that referenced this issue Oct 2, 2019
@k8s-ci-robot
Merge pull request kubernetes-sigs#81 from chuckha/gha-cleanup
27e1ffa 
Minor fixup for workflow
chuckha pushed a commit to chuckha/cluster-api that referenced this issue Oct 2, 2019
@k8s-ci-robot
Merge pull request kubernetes-sigs#81 from chuckha/machine-ref-match
739894d 
Fix machine ref matching
jayunit100 pushed a commit to jayunit100/cluster-api that referenced this issue Jan 31, 2020
@k8s-ci-robot
Conform folder struct and controller code to Go standard (kubernetes-…
10c76a3 
…sigs#83)

* Moved folders around to match standard go project structure

Created cmd and pkg as top level folder and moved folders around appropriately.  Fixed
up the makefiles and dockerfiles.

* Use Go standard for struct name for functions

Some leftover code from before this repo was under sig-vmware didn't
follow the go standard.  Fixed them.

Resolves kubernetes-sigs#81
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@krousey krousey

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

GCE cloud provider mkjelland/cluster-api
2 participants
@krousey @rsdcastro