-
Notifications
You must be signed in to change notification settings - Fork 226
Update vendor dependencies #163
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 vendor dependencies #163
Conversation
Hi @cynepco3hahue. Thanks for your PR. I'm waiting for a openshift member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. 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. |
Gopkg.toml
Outdated
name = "k8s.io/code-generator" | ||
# revision for tag "kubernetes-1.11.2" | ||
revision = "6702109cc68eb6fe6350b83e14407c8d7309fd1a" | ||
version = "kubernetes-1.11.1" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why not 1.11.2
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I checked other openshift repositories that we depend on like github.com/openshift/api
, github.com/openshift/client-go
and they use kubernetes-1.11.1
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
fair enough. Hopefully there is no signification difference (e.g. known errors in 1.11.1 fixed in 1.11.2).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@ingvagabund, in the end, I updated dependencies to 1.11.2 because controller-runtime
depends on it
// NewTestConfig creates new test config with clients | ||
func NewTestConfig(kubeconfig string) *TestConfig { | ||
config, err := controller.GetConfig(kubeconfig) | ||
config, err := clientcmd.BuildConfigFromFlags("", kubeconfig) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+1
sigs.k8s.io/cluster-api-machineset: worker | ||
spec: | ||
providerConfig: | ||
providerSpec: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ha, this got forgotten. Please, remove this from the PR. The field can be renamed once we remove the .providerConfig
field completely in upcoming PR.
/ok-to-test |
9a08cfc
to
0c6a834
Compare
/retest |
0c6a834
to
dd6e72c
Compare
/retest |
@ingvagabund hi, do you know how can I update actuator images with the latest changes? |
@cynepco3hahue yeah, the job responsible for building the docker images is most likely broken/not running. @paulfantom can you take a look at it? |
@cynepco3hahue can you break the commit into two? One that updates deps and one that changes the mao code? It's easier to review then. Plus, the PR summary does not reflect what the PR does. Can you more elaborate on that? E.g. |
@ingvagabund I separated change where I drop |
@cynepco3hahue we have images on quay, for this repo image is stored in https://quay.io/repository/openshift/origin-machine-api-operator |
@paulfantom Do I need to update this repo to take images from |
Yes, we should use quay where possible. |
@paulfantom Can you point me to related images under the quay.io? I just tried to search for |
@paulfantom Thanks will update images to relevant one |
b6a6d61
to
79f1a9d
Compare
@cynepco3hahue can you rebase? |
@ingvagabund Sure and sorry for the delay, I had some snowboard PTO 😄 |
Take your time :) Not urgent, relaxing and having good time is better :P |
79f1a9d
to
848e66a
Compare
fc99d85
to
33ab181
Compare
@ingvagabund Rebased, can you please review again? |
revision = "1624edc4454b8682399def8740d46db5e4362ba4" | ||
version = "v1.1.5" | ||
|
||
[[projects]] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why do we need this? How did it end up in the lock file?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hm, I just ran dep ensure -v
, I will check the dependency tree to see from where it is coming.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@enxebre Ok, logrus
v1.3.0 has this dependency, I see only test/integration
has the dependency on the logrus
, can we drop it in favor of glog
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
definitely sg
pkg/operator/status.go
Outdated
Name: optr.name, | ||
}, | ||
Status: osconfigv1.ClusterOperatorStatus{ | ||
Version: version.Raw, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This belongs to a different commit. This effort it's being tracked here https://jira.coreos.com/browse/CLOUD-332
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I need to update it here because of dep
updates to the latest changes, otherwise, I will have a compilation error, at least from CI I can see that it does not break anything.
- align k8s.io dependencies version to k8s-1.11.2 - use exact version 0.1.7 for `controller-runtime` package
33ab181
to
f843367
Compare
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: 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
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/retest |
After the pivoting of cluster API this PR does not relevant anymore. |
Drop cluster test since it's not relevant for the actuator
Bug 1948719: update controller-runtime dependency
This package depends on release-1.9 or on release-1.12, in both
cases it does not work with our dependencies