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

Bug 1832153: Upstream v1.18.2 rebase #136

Merged
merged 6 commits into from May 6, 2020

Conversation

squeed
Copy link
Contributor

@squeed squeed commented May 5, 2020

Nothing too exciting, but a lot of mechanical changes:

  • All client-go operations need a context
  • Some former string types now have explicit names, so lots of boilerplate
  • Some small kube-proxy cmd changes

@openshift-ci-robot openshift-ci-robot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label May 5, 2020
@openshift-ci-robot openshift-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label May 5, 2020
@squeed
Copy link
Contributor Author

squeed commented May 5, 2020

This currently points to a personal fork of kubernetes - once CI looks reasonable will push to origin.

@squeed
Copy link
Contributor Author

squeed commented May 5, 2020

/cc @juanluisvaladas @danwinship

@juanluisvaladas
Copy link
Contributor

Oh, I hope you were aware of this this: #117 or at least that you didn't miss it

@squeed
Copy link
Contributor Author

squeed commented May 5, 2020

Oh, I hope you were aware of this this: #117 or at least that you didn't miss it

Yup, I followed it - it worked quite well!

@@ -224,3 +225,19 @@ func GetHostIPNetworks(skipInterfaces []string) ([]*net.IPNet, []net.IP, error)
}
return hostIPNets, hostIPs, kerrors.NewAggregate(errList)
}

func HSEgressIPsToStrings(ips []networkv1.HostSubnetEgressIP) []string {
Copy link
Contributor

Choose a reason for hiding this comment

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

Sigh. This is a mess and we should revert the openshift/api change that required it.
(At a minimum, split the egressip changes into a separate commit so they're easily revertable when we fix this later.)

Copy link
Contributor

Choose a reason for hiding this comment

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

In case someone else gets here later and also wonders the rationale for this:
openshift/api@a63a88e

Copy link
Contributor Author

@squeed squeed May 5, 2020

Choose a reason for hiding this comment

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

grump: go has exactly two "magic" types. Why it can't implement type conversion across literally the only two polymorphic types in the whole world is infuriating. It can't even use the "oh, we actually monomorphize everything" excuse like Rust.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

@abhat can fill us in, but I believe the issue is that it's not possible to add validation to an array

Copy link
Contributor

Choose a reason for hiding this comment

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

Yes, but we don't need validation there if it's just going to make our lives more difficult. We have to validate the network CRD types at runtime anyway because the CRD validation only handles part of it. There is talk about adding a ValidatingWebHook at some point so we can do this properly.

@juanluisvaladas
Copy link
Contributor

Looks good to me so far. Also checked your local 1.18 branch and only has the two old carry patches so it looks fine there too.

I'm launching the e2e-gcp for you because I'm pretty sure the failing test is unrelated.
/test e2e-gcp

@squeed
Copy link
Contributor Author

squeed commented May 6, 2020

okay, just waiting for someone with more power to push to openshift/kubernetes

@squeed
Copy link
Contributor Author

squeed commented May 6, 2020

ok, @danwinship I split the commits.

Since CI passed, I've pushed the tag to openshift/kubernetes, and updated go.mod accordingly. This is ready to go.

@squeed squeed changed the title [wip] Upstream v1.18.2 rebase Bug 1832153: Upstream v1.18.2 rebase May 6, 2020
@openshift-ci-robot openshift-ci-robot added bugzilla/severity-unspecified Referenced Bugzilla bug's severity is unspecified for the PR. and removed do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. labels May 6, 2020
@openshift-ci-robot
Copy link
Contributor

@squeed: This pull request references Bugzilla bug 1832153, which is valid. The bug has been moved to the POST state. The bug has been updated to refer to the pull request using the external bug tracker.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target release (4.5.0) matches configured target release for branch (4.5.0)
  • bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)

In response to this:

Bug 1832153: Upstream v1.18.2 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/test-infra repository.

@openshift-ci-robot openshift-ci-robot added the bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. label May 6, 2020
@juanluisvaladas
Copy link
Contributor

Oof, looks like the verify-deps strikes again... @squeed the make update-deps-overrides produces different vendor depending on your go version, env, and god knows what.

I strongly recommend that you get pull verify-deps pod image, run it locally, run the make update-deps-overrides inside that container and copy the contents of it into your vendor directory with docker cp or whatever container runtime engine you're using.

@squeed
Copy link
Contributor Author

squeed commented May 6, 2020

Oof, looks like the verify-deps strikes again...

Derp, forgot to go mod tidy.

squeed added 5 commits May 6, 2020 15:38
What were formerly strings are now named types.
- all client-go operations need a context
- small test util renames
@squeed
Copy link
Contributor Author

squeed commented May 6, 2020

Dan observed that kubernetes branch should have been a fork off of upstream, not origin.

Fixed that, revendored, repushed.

@danwinship
Copy link
Contributor

lgtm but should we wait for openshift/kubernetes#126 first to avoid a second bump?

@squeed
Copy link
Contributor Author

squeed commented May 6, 2020

lgtm but should we wait for openshift/kubernetes#126 first to avoid a second bump?

Hah, I figured you'd be mad if I conflated that pr.

@danwinship
Copy link
Contributor

/retest
/lgtm

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label May 6, 2020
@openshift-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: danwinship, squeed

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-merge-robot openshift-merge-robot merged commit 100a929 into openshift:master May 6, 2020
@openshift-ci-robot
Copy link
Contributor

@squeed: All pull requests linked via external trackers have merged: openshift/sdn#136. Bugzilla bug 1832153 has been moved to the MODIFIED state.

In response to this:

Bug 1832153: Upstream v1.18.2 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/test-infra repository.

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. bugzilla/severity-unspecified Referenced Bugzilla bug's severity is unspecified for the PR. bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants