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

Remove GCP cluster api provider #5437

Conversation

patrickdillon
Copy link
Contributor

I ended up doing this work while trying to eliminate our need to replace the cluster-api-provider-azure. More work is needed beyond this to achieve that, but we might as well commit it. I am doing this work for Azure, but we should be able to do something similar for all other providers that have migrated to openshift/api.

@patrickdillon
Copy link
Contributor Author

/cc @kirankt @staebler

@openshift-ci openshift-ci bot requested review from kirankt and staebler December 1, 2021 17:14
@patrickdillon
Copy link
Contributor Author

/test e2e-gcp

I thought these tests should be run automatically with recent changes, but it looks like they are not getting queued.

@patrickdillon patrickdillon force-pushed the remove-gcp-cluster-api-provider branch from 346d380 to 4737c4a Compare December 1, 2021 17:17
@patrickdillon
Copy link
Contributor Author

/test e2e-gcp

Copy link
Contributor

@kirankt kirankt left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @patrickdillon I actaully meant to work on this today as well. Left a few comments. PTAL.

@@ -537,7 +535,6 @@ func (m *Master) Machines() ([]machineapi.Machine, error) {
awsapi.AddToScheme(scheme)
azureapi.AddToScheme(scheme)
baremetalapi.AddToScheme(scheme)
gcpapi.AddToScheme(scheme)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we will need to add the GCP types into the schema here.
e.g.

// Add vsphere types to scheme
scheme.AddKnownTypes(machineapi.SchemeGroupVersion,
&machineapi.VSphereMachineProviderSpec{},
)

@@ -555,7 +552,6 @@ func (w *Worker) MachineSets() ([]machineapi.MachineSet, error) {
awsprovider.SchemeGroupVersion,
azureprovider.SchemeGroupVersion,
baremetalprovider.SchemeGroupVersion,
gcpprovider.SchemeGroupVersion,
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ditto.

Copy link
Contributor

@staebler staebler left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please separate the vendor changes in their own commit.

@@ -4,8 +4,7 @@ import (
"encoding/json"
"fmt"

gcpprovider "github.com/openshift/cluster-api-provider-gcp/pkg/apis/gcpprovider/v1beta1"

machineapi "github.com/openshift/api/machine/v1beta1"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Leave the machineapi import in a section separate from the installer import.

@patrickdillon patrickdillon force-pushed the remove-gcp-cluster-api-provider branch 2 times, most recently from 452963a to 173546b Compare December 1, 2021 19:17
@patrickdillon
Copy link
Contributor Author

/test e2e-gcp

Ok, fixed it up based on the recommendations. Let's see if we get further in the tests now.

@patrickdillon
Copy link
Contributor Author

install suceeds, 2 failed tests that look unrelated

/test e2e-gcp

Copy link
Contributor

@kirankt kirankt left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It would be nice to see 2 separate commits. One for the code changes and the other for vendoring changes. Other than that it looks like the gcp test is passing, so lgtm.

@kirankt
Copy link
Contributor

kirankt commented Dec 2, 2021

/test e2e-metal

@jhixson74
Copy link
Member

/uncc

@openshift-ci openshift-ci bot removed the request for review from jhixson74 December 2, 2021 21:44
@openshift-ci openshift-ci bot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Dec 12, 2021
@patrickdillon patrickdillon force-pushed the remove-gcp-cluster-api-provider branch from 173546b to 98e2d2a Compare December 14, 2021 21:24
@openshift-ci openshift-ci bot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Dec 14, 2021
@patrickdillon
Copy link
Contributor Author

Oops, I lost track of this but have now updated/rebased.

@staebler
Copy link
Contributor

/test e2e-gcp

Copy link
Contributor

@kirankt kirankt left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

GCP test passed.
/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Dec 15, 2021
@staebler
Copy link
Contributor

/approve

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Dec 15, 2021

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: staebler

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

The pull request process is described here

Needs approval from an approver in each of these files:

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

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Dec 15, 2021
@openshift-bot
Copy link
Contributor

/retest-required

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest-required

Please review the full test history for this PR and help us cut down flakes.

7 similar comments
@openshift-bot
Copy link
Contributor

/retest-required

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest-required

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest-required

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest-required

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest-required

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest-required

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest-required

Please review the full test history for this PR and help us cut down flakes.

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Dec 16, 2021

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

Test name Commit Details Required Rerun command
ci/prow/verify-vendor 98e2d2a30d1116bc0c11ea2805febe87e8d41c24 link true /test verify-vendor

Full PR test history. Your PR dashboard.

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.

@openshift-bot
Copy link
Contributor

/retest-required

Please review the full test history for this PR and help us cut down flakes.

1 similar comment
@openshift-bot
Copy link
Contributor

/retest-required

Please review the full test history for this PR and help us cut down flakes.

Now that the GCP machine provider spec has moved to the openshift/api
we can remove the GCP cluster api provider.
@staebler staebler force-pushed the remove-gcp-cluster-api-provider branch from 98e2d2a to 3e4b438 Compare December 16, 2021 13:12
@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Dec 16, 2021
@staebler
Copy link
Contributor

98e2d2a30...3e4b438b1

  • Rebased and ran go mod tidy to fix up the go.sum file.

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Dec 16, 2021
@staebler staebler force-pushed the remove-gcp-cluster-api-provider branch from 3e4b438 to 830d0d7 Compare December 16, 2021 13:38
@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Dec 16, 2021
@staebler
Copy link
Contributor

3e4b438b1...830d0d73f

  • Actually include the go.sum changes this time.

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Dec 16, 2021
@openshift-bot
Copy link
Contributor

/retest-required

Please review the full test history for this PR and help us cut down flakes.

6 similar comments
@openshift-bot
Copy link
Contributor

/retest-required

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest-required

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest-required

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest-required

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest-required

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest-required

Please review the full test history for this PR and help us cut down flakes.

@openshift-merge-robot openshift-merge-robot merged commit 8f24215 into openshift:master Dec 16, 2021
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. lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants