Bump deps to version 1.14#178
Conversation
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: rcarrillocruz If they are not already assigned, you can assign the PR to them by writing The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
That was fast :-) |
|
/retest |
a76a6b2 to
3a473c0
Compare
|
While you're at it, want to bump operator-sdk to 0.8? Annoyingly, you will have to figure out any changes to main.go from the operator-sdk templating. |
Yah, can look at it. |
43d6e99 to
ef96418
Compare
|
/retest |
ef96418 to
b3f8d22
Compare
| [[override]] | ||
| name = "sigs.k8s.io/controller-runtime" | ||
| version = "=v0.1.8" | ||
| version = "=v0.2.0-beta.1" |
There was a problem hiding this comment.
don't bump this yet, this version is definitely not ready to go.
There was a problem hiding this comment.
So yeah, this tripped me up.
The issue is that 0.2.0-beta.1 is the tag for controller-runtime to bump to Kubernetes 1.14.
Without pinning to that, we hit this on compile time:
# github.com/openshift/cluster-network-operator/vendor/sigs.k8s.io/controller-runtime/pkg/leaderelection
vendor/sigs.k8s.io/controller-runtime/pkg/leaderelection/leader_election.go:83:25: not enough arguments in call to resourcelock.New
have (string, string, string, "github.com/openshift/cluster-network-operator/vendor/k8s.io/client-go/kubernetes/typed/core/v1".CoreV1Interface, resourcelock.ResourceLockConfig)
want (string, string, string, "github.com/openshift/cluster-network-operator/vendor/k8s.io/client-go/kubernetes/typed/core/v1".CoreV1Interface, "github.com/openshift/cluster-network-operator/vendor/k8s.io/client-go/kubernetes/typed/coordination/v1".CoordinationV1Interface, resourcelock.ResourceLockConfig)
Check pkg/leaderelection/leader_election.go.
kubernetes-sigs/controller-runtime@71cf6f6#diff-2590281733c8f856c7a8fb319d5d3cc5R87
So I wonder if we should wait for controller-runtime to release a version that is non-beta, then we change the pin.
Reverting to 0.1.8 is a no-go.
There was a problem hiding this comment.
Yes, we have a PR out in operator-sdk to switch to controller-runtime 0.2.0-x, we haven't merged it yet as they are still in beta (from what I spoke with the maintainer they should be cutting the stable release soon if no bugs are found in testing). There are a lot of changes there, you can see in operator-framework/operator-sdk#1388 PR if that is of any help. Sadly they did not release an intermediate version with bumping k8s to 1.14.
I would agree to the following as we have things ready:
So I wonder if we should wait for controller-runtime to release a version that is non-beta, then we change the pin.
|
/hold |
|
@rcarrillocruz: PR needs rebase. DetailsInstructions 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. |
|
hi @rcarrillocruz so we merged the bump to k8s 1.14 into a branch on operator-sdk. You can see the PR operator-framework/operator-sdk#1512. Maybe start testing against that commit from https://github.com/operator-framework/operator-sdk/tree/refactor/controller-runtime-v0.2.0, in this PR. We are blocked on controller-runtime cutting the final release of v0.2.0. But things should not change too much when we do merge that branch into operator-sdk master. |
|
oki, thx for the update @lilic |
No description provided.