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
Bump client-go and other deps to v1.18.3 #851
Conversation
c759cae
to
e9c478b
Compare
/retest |
I don't think there is a reason we should wait until 0.40 prom-operator bump as well right? Is this ready for review now? |
I don't think there is any.
yes |
k8s.io/api => k8s.io/api v0.18.3 | ||
k8s.io/apimachinery => k8s.io/apimachinery v0.18.3 | ||
k8s.io/client-go => k8s.io/client-go v0.18.3 |
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.
Do we really need these replacements?
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.
Those are ensuring we are pinning to 0.18.3, without them go mod tidy
rewrites it to v0.18.4 and in case of client-go it panics.
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.
👍
go.mod
Outdated
k8s.io/api => k8s.io/api v0.17.1 | ||
k8s.io/apimachinery => k8s.io/apimachinery v0.17.1 | ||
k8s.io/client-go => k8s.io/client-go v0.17.1 | ||
github.com/prometheus/prometheus => github.com/prometheus/prometheus v1.8.2-0.20200609102542-5d7e3e970602 // v1.8.2 is misleading as Prometheus does not have v2 module. This is pointing to v2.19.0, the same as in promehteus-operator v0.40.0 |
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 suspect that you can get rid of the replacement and put it directly in the require
list.
pkg/client/client.go
Outdated
@@ -148,32 +149,33 @@ func (c *Client) SecretListWatchForNamespace(ns string) *cache.ListWatch { | |||
|
|||
func (c *Client) WaitForPrometheusOperatorCRDsReady() error { | |||
return wait.Poll(time.Second, time.Minute*5, func() (bool, error) { | |||
err := c.WaitForCRDReady(k8sutil.NewCustomResourceDefinition(monv1.DefaultCrdKinds.Prometheus, mon.GroupName, map[string]string{}, false)) | |||
// TODO(paulfantom): re-add checking for CRDs |
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.
to be removed?
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 removed waiting for CRDs as those are managed externally.
/refresh |
This is now rebased on top of #870 to allow faster testing. |
9fc9508
to
e2dcff3
Compare
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.
One question otherwise
@@ -4,34 +4,33 @@ go 1.13 | |||
|
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.
Should we do go 1.14 here above?
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 don't think we have any features in CMO which need 1.14 and codebase can be compiled with 1.13, so the current setting seems good to me.
* all k8s deps to 1.18.X * prometheus-operator to 0.40.0 * prometheus to v2.19.0 (same as in promehteus-operator)
aws failures |
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.
/lgtm
Thanks!!
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: lilic, paulfantom 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 Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
13 similar comments
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
Updated client-go to 0.18.3
Updated prometheus-operator to 0.40.0 (necessary for client-go upgrade)
Updated other k8s deps to 0.18.X (required by prometheus-operator upgrade)
Updated prometheus to 2.19.0 (required by prometheus-operator upgrade)
Moving
VolumeClaimTemplate
type toEmbeddedPersistentVolumeClaim
from prometheus-operator to fix type incompatibilityRemoved setting
CreationTimestamp
to 0 as it is not required after changing types.