Skip to content

Conversation

@alexander-demicev
Copy link
Contributor

This commit rebases the cluster-api-provider-gcp openshift patches on top of the kubernetes-sigs/ cluster-api-provider-gcp main branch after.
There are several commits that we carry on top of the upstream cluster-api-provider-gcp and the rebase process allows us to preserve those. Here is a description of the process I used to create this PR.

(replicated @elmiko's process within openshift/kubernetes-autoscaler)

Process

First we need to identify the carry commits that we currently have, this is done against our previous rebase (or fork in this case) to catch new changes. Once identified we will drop commits which have merged upstream and only carry unique commits. (see below for the carried and dropped commits).

Identify carry commits:

git log --oneline --no-merges c26a68b23e9317323d5d37660fe9d29b3d2ff40c..openshift/master

After identifying the carry commits, the next step is to create the new commit-tree that will be used for the rebase and then cherry pick the carry commits into the new branch. The following commands cover these steps:

$ git remote update # make sure we update our refs
$ git checkout c26a68b23e9317323d5d37660fe9d29b3d2ff40c
$ git checkout -b merge-tmp # create a temporary branch for our merge commit
$ git checkout openshift/master # we want to be at the tip of the openshift master branch when we run the next command
$ echo 'merge latest upstream changes' | git commit-tree merge-tmp^{tree} -p HEAD -p merge-tmp -F - # create a new merge commit for our history
deadbeef12345678 # id of new merge commit
$ git branch rebase-upstream-latest deadbeef12345678 # create a new branch for the cherry-pick work
$ git checkout rebase-upstream-latest
$ git cherry-pick <carry commits> # cherry pick the needed commits into the new branch

With the rebase-upstream-latest branch in place, I cherry picked the carry commits which we should carry.

Carried Commits

These commits are integral to our CI platform, or are specific to the releases we create for OpenShift.

   498c4ae9e UPSTREAM: <carry>: Add vendor directory
   3c05c04f3 UPSTREAM: <carry>: Add openshift specific changes

Changed Commits

---

Dropped Commits

Click to expand

rishi-anand and others added 30 commits February 19, 2020 18:40
🏃 [ci-conformance] Fix kustomize template to remove ami reference
- Increase timeout for getting nodes
- Fix GCPMachine watch in GCPCluster controller
- Fix template errors
- Remove cloud-init bootstrapping in favor of building an image with the ci artifacts
🏃 [ci-conformance] Fix kustomize template to better handle envsubst
🏃 [ci-conformance] Fix tests when not using CI artifacts
🏃 [ci-conformance] fix unbound variable
Makefile: add missing kustomize dependency
This avoids the 63 character limit on the kubernetes.io/hostname label.

Issue kubernetes/kubernetes#90686
Register only with first component of local_hostname
🏃 Fix conformance script for recent image-builder change
🏃 Add gab-satchi to cluster-api-gcp-maintainers
🐛 Added common tag for control-plane and worker nodes to resolve LoadBalancer issue
Signed-off-by: Stephen Augustus <saugustus@vmware.com>
hack/ci: Use ci/latest version marker for retrieving cross builds
Support confirurable root volume type as (optional) parameter within
GCPMachineSpec.
Signed-off-by: Spencer Smith <robertspencersmith@gmail.com>
sayantani11 and others added 18 commits October 13, 2021 05:53
Related to:
  - kubernetes/k8s.io#1523
  - kubernetes/test-infra#23656

Signed-off-by: Arnaud Meukam <ameukam@gmail.com>
use k8s-staging-test-infra/gcb-docker-gcloud
Signed-off-by: Carlos Panato <ctadeu@gmail.com>
Signed-off-by: Carlos Panato <ctadeu@gmail.com>
[api/labels] Initialize nil dest labels during addition.
This version pulls in updated linters. This provides better checks and
addresses an issue some had when running under go 1.17.

Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
@openshift-ci openshift-ci bot requested review from JoelSpeed and elmiko January 7, 2022 15:45
@JoelSpeed
Copy link
Contributor

/approve

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 31, 2022

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: JoelSpeed

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

The pull request process is described here

Details 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 Jan 31, 2022
Copy link
Contributor

@Fedosin Fedosin left a comment

Choose a reason for hiding this comment

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

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Feb 1, 2022
@openshift-merge-robot openshift-merge-robot merged commit f6b7118 into openshift:master Feb 1, 2022
@alexander-demicev alexander-demicev deleted the rebase-upstream-latest branch April 12, 2022 09:58
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.