Adding GCPMachinePool Functionality #901

BrennenMM7 · 2023-04-18T20:14:15Z

What type of PR is this?
/kind feature

What this PR does / why we need it:
This PR Implements GCPMachinePool using Managed Instance Groups. This is needed to support the CAPI MachinePools object. Feature will allow cluster operators to deploy GCP MIG's to their CAPG clusters to take advantage of both Google Autoscaling of Compute Instances or utilizing cluster autoscaler to dynamically provision node resources.

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #297,#1005

Special notes for your reviewer:

Please confirm that if this PR changes any image versions, then that's the sole change this PR makes.

TODOs:

squashed commits
includes documentation
adds unit tests

Release note:

Feature: adds MachinePool/GCPMachinePool Objects to deploy Managed Instance Group services.

k8s-ci-robot · 2023-04-18T20:14:23Z

Welcome @BrennenMM7!

It looks like this is your first PR to kubernetes-sigs/cluster-api-provider-gcp 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes-sigs/cluster-api-provider-gcp has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

k8s-ci-robot · 2023-04-18T20:14:24Z

Hi @BrennenMM7. Thanks for your PR.

I'm waiting for a kubernetes-sigs 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.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

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.

k8s-ci-robot · 2023-04-18T20:20:32Z

@BrennenMM7: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

In response to this:

/ok-to-test

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.

cpanato

/ok-to-test
/assign @richardcase

thanks for your PR, an initial comments

cloud/services/compute/instancegroups/client.go

cloud/scope/machinepool.go

cloud/const.go

cloud/services/compute/instancegroups/doc.go

cloud/services/compute/instancegroups/instancegroups.go

exp/controllers/helpers.go

k8s-ci-robot · 2023-08-30T18:06:55Z

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: BrennenMM7
Once this PR has been reviewed and has the lgtm label, please ask for approval from cpanato. For more information see the Kubernetes Code Review Process.

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

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

k8s-triage-robot · 2024-01-21T08:17:56Z

The Kubernetes project currently lacks enough contributors to adequately respond to all PRs.

This bot triages PRs according to the following rules:

After 90d of inactivity, lifecycle/stale is applied
After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
After 30d of inactivity since lifecycle/rotten was applied, the PR is closed

You can:

Mark this PR as fresh with /remove-lifecycle stale
Close this PR with /close
Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

k8s-triage-robot · 2024-02-20T08:31:16Z

The Kubernetes project currently lacks enough active contributors to adequately respond to all PRs.

This bot triages PRs according to the following rules:

After 90d of inactivity, lifecycle/stale is applied
After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
After 30d of inactivity since lifecycle/rotten was applied, the PR is closed

You can:

Mark this PR as fresh with /remove-lifecycle rotten
Close this PR with /close
Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

k8s-ci-robot · 2024-05-10T16:37:22Z

PR needs rebase.

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-sigs/prow repository.

damdo · 2024-05-15T11:12:31Z

@BrennenMM7 this will need a rebase :)

cloud/const.go

exp/api/v1beta1/gcpmachinepool_types.go

salasberryfin · 2024-05-16T07:27:32Z

exp/controllers/gcpmachinepool_controller.go

+		).
+		// watch for changes in KubeadmConfig to sync bootstrap token
+		Watches(
+			&kubeadmv1.KubeadmConfig{},


Would we be able to avoid having to watch KubeadmConfig? This would prevent anyone enabling MachinePool from selecting the bootstrap provider of their choice and force them to use Kubeadm. This is something we've realized happens in CAPZ and there's an open issue to address this. Other providers, like CAPA, don't have this dependency on Kubeadm.

A great point @salasberryfin 👍

+1, thanks for catching this!

This is a great point, I'd love to abstract the mechanism away from the kubeadm bootstrap provider lock-in. Any idea how we'd enqueue a reconcile from a token rotation when two different bootstrap providers are being utilized 🤔

cpanato · 2024-05-20T13:08:13Z

need rebase

BrennenMM7 · 2024-05-20T16:14:34Z

@damdo @cpanato PR has been rebased thanks 💯

k8s-ci-robot · 2024-05-20T16:18:12Z

@BrennenMM7: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
pull-cluster-api-provider-gcp-verify	`3f4e888`	link	true	`/test pull-cluster-api-provider-gcp-verify`
pull-cluster-api-provider-gcp-test	`3f4e888`	link	true	`/test pull-cluster-api-provider-gcp-test`

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

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

k8s-ci-robot · 2024-05-30T23:14:41Z

PR needs rebase.

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-sigs/prow repository.

k8s-triage-robot · 2024-06-30T00:10:30Z

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages PRs according to the following rules:

After 90d of inactivity, lifecycle/stale is applied
After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
After 30d of inactivity since lifecycle/rotten was applied, the PR is closed

You can:

Reopen this PR with /reopen
Mark this PR as fresh with /remove-lifecycle rotten
Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close

k8s-ci-robot · 2024-06-30T00:10:34Z

@k8s-triage-robot: Closed this PR.

In response to this:

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages PRs according to the following rules:

After 90d of inactivity, lifecycle/stale is applied

After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied

After 30d of inactivity since lifecycle/rotten was applied, the PR is closed

You can:

Reopen this PR with /reopen

Mark this PR as fresh with /remove-lifecycle rotten

Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close

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-sigs/prow repository.

damdo · 2024-06-30T09:31:42Z

/reopen

k8s-ci-robot · 2024-06-30T09:31:46Z

@damdo: Reopened this PR.

In response to this:

/reopen

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-sigs/prow repository.

damdo · 2024-06-30T09:31:53Z

/remove-lifecycle rotten

salasberryfin · 2024-07-02T06:54:02Z

Hey @BrennenMM7. We discussed previously the fact that we do not want to create a Kubeadm dependency, which was an issue with other providers too. I think we can do something similar to what CAPZ did here which decouples the MachinePool reconciler from Kubeadm. What do you think?

BrennenMM7 · 2024-07-08T16:58:21Z

@salasberryfin 👋 Yeah this looks good, I can easily port my changes to support this, I'll update and rebase this PR this week.

salasberryfin · 2024-09-24T15:31:22Z

Hey @BrennenMM7, would you be able to update this PR?

k8s-triage-robot · 2024-12-23T16:02:54Z

The Kubernetes project currently lacks enough contributors to adequately respond to all PRs.

This bot triages PRs according to the following rules:

After 90d of inactivity, lifecycle/stale is applied
After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
After 30d of inactivity since lifecycle/rotten was applied, the PR is closed

You can:

Mark this PR as fresh with /remove-lifecycle stale
Close this PR with /close
Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

k8s-ci-robot added release-note Denotes a PR that will be considered when it comes time to generate release notes. kind/feature Categorizes issue or PR as related to a new feature. labels Apr 18, 2023

k8s-ci-robot requested review from cpanato and dims April 18, 2023 20:14

k8s-ci-robot added the cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. label Apr 18, 2023

k8s-ci-robot added the needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. label Apr 18, 2023

k8s-ci-robot added the size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. label Apr 18, 2023

cpanato requested changes Apr 18, 2023

View reviewed changes

k8s-ci-robot assigned richardcase Apr 18, 2023

k8s-ci-robot added ok-to-test Indicates a non-member PR verified by an org member that is safe to test. and removed needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Apr 18, 2023

k8s-ci-robot assigned cpanato Apr 18, 2023

BrennenMM7 force-pushed the GCPMachinePools branch from 7187b6d to 08edce3 Compare April 18, 2023 20:33

k8s-ci-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Apr 25, 2023

BrennenMM7 force-pushed the GCPMachinePools branch from 08edce3 to dbffc56 Compare June 13, 2023 15:58

k8s-ci-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jun 13, 2023

BrennenMM7 requested a review from cpanato June 13, 2023 16:30

k8s-ci-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jun 20, 2023

BrennenMM7 force-pushed the GCPMachinePools branch 2 times, most recently from 45b2b1a to caf5243 Compare August 30, 2023 17:54

k8s-ci-robot added needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. and removed needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. labels Aug 30, 2023

k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 21, 2024

k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Feb 20, 2024

BrennenMM7 force-pushed the GCPMachinePools branch from 14b660a to 6f8e1ea Compare April 18, 2024 18:20

BrennenMM7 mentioned this pull request May 2, 2024

Implement MachinePool Machines #1005

Open

k8s-ci-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label May 10, 2024

richardcase reviewed May 15, 2024

View reviewed changes

cloud/const.go Outdated Show resolved Hide resolved

exp/api/v1beta1/gcpmachinepool_types.go Show resolved Hide resolved

salasberryfin reviewed May 16, 2024

View reviewed changes

Adding GCPMachinePool Functionality

4528f81

BrennenMM7 force-pushed the GCPMachinePools branch from 4cf6e2b to 4528f81 Compare May 20, 2024 16:12

go mod tidy after rebase

3f4e888

k8s-ci-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label May 20, 2024

k8s-ci-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label May 30, 2024

k8s-ci-robot closed this Jun 30, 2024

k8s-ci-robot reopened this Jun 30, 2024

k8s-ci-robot removed the lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. label Jun 30, 2024

salasberryfin mentioned this pull request Sep 6, 2024

Move managed cluster support (GKE) to general availability #1168

Open

k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 23, 2024

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Adding GCPMachinePool Functionality #901

Adding GCPMachinePool Functionality #901

BrennenMM7 commented Apr 18, 2023 •

edited

Loading

k8s-ci-robot commented Apr 18, 2023

k8s-ci-robot commented Apr 18, 2023

k8s-ci-robot commented Apr 18, 2023

cpanato left a comment

k8s-ci-robot commented Aug 30, 2023

k8s-triage-robot commented Jan 21, 2024

k8s-triage-robot commented Feb 20, 2024

k8s-ci-robot commented May 10, 2024

damdo commented May 15, 2024

salasberryfin May 16, 2024

richardcase May 16, 2024

damdo May 16, 2024

cpanato May 20, 2024

BrennenMM7 May 20, 2024

cpanato commented May 20, 2024

BrennenMM7 commented May 20, 2024

k8s-ci-robot commented May 20, 2024 •

edited

Loading

k8s-ci-robot commented May 30, 2024

k8s-triage-robot commented Jun 30, 2024

k8s-ci-robot commented Jun 30, 2024

damdo commented Jun 30, 2024

k8s-ci-robot commented Jun 30, 2024

damdo commented Jun 30, 2024

salasberryfin commented Jul 2, 2024

BrennenMM7 commented Jul 8, 2024

salasberryfin commented Sep 24, 2024

k8s-triage-robot commented Dec 23, 2024

Adding GCPMachinePool Functionality #901

Are you sure you want to change the base?

Adding GCPMachinePool Functionality #901

Conversation

BrennenMM7 commented Apr 18, 2023 • edited Loading

k8s-ci-robot commented Apr 18, 2023

k8s-ci-robot commented Apr 18, 2023

k8s-ci-robot commented Apr 18, 2023

cpanato left a comment

Choose a reason for hiding this comment

k8s-ci-robot commented Aug 30, 2023

k8s-triage-robot commented Jan 21, 2024

k8s-triage-robot commented Feb 20, 2024

k8s-ci-robot commented May 10, 2024

damdo commented May 15, 2024

salasberryfin May 16, 2024

Choose a reason for hiding this comment

richardcase May 16, 2024

Choose a reason for hiding this comment

damdo May 16, 2024

Choose a reason for hiding this comment

cpanato May 20, 2024

Choose a reason for hiding this comment

BrennenMM7 May 20, 2024

Choose a reason for hiding this comment

cpanato commented May 20, 2024

BrennenMM7 commented May 20, 2024

k8s-ci-robot commented May 20, 2024 • edited Loading

k8s-ci-robot commented May 30, 2024

k8s-triage-robot commented Jun 30, 2024

k8s-ci-robot commented Jun 30, 2024

damdo commented Jun 30, 2024

k8s-ci-robot commented Jun 30, 2024

damdo commented Jun 30, 2024

salasberryfin commented Jul 2, 2024

BrennenMM7 commented Jul 8, 2024

salasberryfin commented Sep 24, 2024

k8s-triage-robot commented Dec 23, 2024

BrennenMM7 commented Apr 18, 2023 •

edited

Loading

k8s-ci-robot commented May 20, 2024 •

edited

Loading