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

Update Kubernetes dependencies to 1.12.7 #793

Merged
merged 5 commits into from
Mar 29, 2019

Conversation

jpeeler
Copy link

@jpeeler jpeeler commented Mar 28, 2019

Need to discuss if this is a valid approach. I've not been able to make go get download the desired versions without using replace in go.mod. I assume this is because of all the weird non-semver tagging in play. If using replace is okay, then it's probably best to remove the makefile vendoring stuff as it does not work well with the changes here.

The good news is that the necessary changes due to updating were very minimal. One benefit to keeping the dependencies aligned this way is that there won't be go.* file changes during normal OLM development.

OLM-892

@openshift-ci-robot openshift-ci-robot added approved Indicates a PR has been approved by an approver from all required OWNERS files. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. labels Mar 28, 2019
@ecordell
Copy link
Member

/retest

@jpeeler
Copy link
Author

jpeeler commented Mar 29, 2019

I managed to get the items in the replace block down to three things - logrus, client-go, and api. However, that makes less sense to me than doing what was done here since everything here is permanently in sync and will therefore not break.

The impossible behavior I've observed is that when client-go is fetched, it pulls in the latest k8s.io/api. Fetching other kubernetes dependencies (for whatever reason) downgrades client-go to the previous release. Both of which causes things to break and is why pinning both of them seemed to be absolutely necessary.

@ecordell
Copy link
Member

/lgtm

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Mar 29, 2019
@openshift-ci-robot
Copy link
Collaborator

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ecordell, jpeeler

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

@ecordell
Copy link
Member

/retest

2 similar comments
@jpeeler
Copy link
Author

jpeeler commented Mar 29, 2019

/retest

@jpeeler
Copy link
Author

jpeeler commented Mar 29, 2019

/retest

@openshift-merge-robot openshift-merge-robot merged commit a88f534 into operator-framework:master Mar 29, 2019
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. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants