-
Notifications
You must be signed in to change notification settings - Fork 5.1k
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
[kube-prometheus-stack] Update prometheus-operator to 0.42.1 #128
[kube-prometheus-stack] Update prometheus-operator to 0.42.1 #128
Conversation
8000b7a
to
0219394
Compare
Would love for this to get merged. I've done this by hand by bumping image versions and deploying the CRDs by hand but the lack of "probes" in the ClusterRole makes things difficult. |
This also bumps the kubernetes prerequisite to 1.16+. prometheus-operator 0.39 introduced a requirement for kubernetes v1.16 or newer. https://github.com/prometheus-operator/prometheus-operator/releases/tag/v0.39.0 I'm +1 with getting this merged in. |
What do you think, should I add a |
0219394
to
96d1037
Compare
|
Related to #24 |
Have these CRDs been updated in the upstream https://github.com/prometheus-operator/kube-prometheus project? This may be a question for @brancz |
I took the CRDs in this PR directly from here: https://github.com/prometheus-operator/prometheus-operator/tree/v0.42.1/example/prometheus-operator-crd |
@bashofmann OK thanks yes, it appears the source – generated as part of the These were updated recently upstream:
Which is interesting to me. I wonder:
Maybe some of the other |
Are you sure that |
9a9284a
to
eb813c3
Compare
The source of truth for CRDs is their jsonnet definition in prometheus-operator repository, this is used to generate yaml files in prometheus-operator and it is also consumed by kube-prometheus. Note: jsonnet code is also generated from go code using generate-crd.go script. |
This chart fails on AWS EKS and probably fails on GKE due to the
Solution appears to be to change the constraint to |
f3d2663
to
03fba17
Compare
Thanks, good catch. I fixed the constraint and rebased the PR. |
I would also love to see this PR land, as |
(Also keenly interested in this one for black box exporter) |
@scottrigby Is there anything else this PR needs besides the obvious rebase? |
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.
resolve merge conflict please
03fba17
to
b9546f9
Compare
b9546f9
to
554e13f
Compare
I rebased the branch again to resolve conflicts. |
554e13f
to
31df5b6
Compare
The lint task seems to have failed due to a network hickup. Is there a way to rerun it (with the right permissions), or do I need to make a tiny change and push again? |
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.
Could you merge the changes from master to your branch introduced by #191 please?
After that linting should succeed :)
This also introduces a new `Probes` CRD. Since Helm does not create this new CRD on a chart upgrade automatically, the chart version is bumped to 10 to indicate the breaking change. Signed-off-by: Bastian Hofmann <bashofmann@gmail.com>
…rRole Signed-off-by: Bastian Hofmann <bashofmann@gmail.com>
….clusterAdvertiseAddress Introduced in 0.39.0 with prometheus-operator/prometheus-operator#3160 Signed-off-by: Bastian Hofmann <bashofmann@gmail.com>
Introduced in 0.41.0 with prometheus-operator/prometheus-operator#3334 Signed-off-by: Bastian Hofmann <bashofmann@gmail.com>
Compatibility added in in 0.41.0 with prometheus-operator/prometheus-operator#3316 Signed-off-by: Bastian Hofmann <bashofmann@gmail.com>
…rtiseAddress Signed-off-by: Bastian Hofmann <bashofmann@gmail.com>
Signed-off-by: Bastian Hofmann <bashofmann@gmail.com>
Signed-off-by: Bastian Hofmann <bashofmann@gmail.com>
31df5b6
to
19f327c
Compare
@monotek rebased and pushed |
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.
Thanks for your work on this
…eus-community#128) * [kube-prometheus-stack] Update prometheus-operator to 0.42.1 This also introduces a new `Probes` CRD. Since Helm does not create this new CRD on a chart upgrade automatically, the chart version is bumped to 10 to indicate the breaking change. Signed-off-by: Bastian Hofmann <bashofmann@gmail.com> * [kube-prometheus-stack] Remove duplicated podmonitors entry in ClusterRole Signed-off-by: Bastian Hofmann <bashofmann@gmail.com> * [kube-prometheus-stack] Add support for alertmanager.alertmanagerSpec.clusterAdvertiseAddress Introduced in 0.39.0 with prometheus-operator/prometheus-operator#3160 Signed-off-by: Bastian Hofmann <bashofmann@gmail.com> * [kube-prometheus-stack] Update configmap-reload to 0.4.0 Introduced in 0.41.0 with prometheus-operator/prometheus-operator#3334 Signed-off-by: Bastian Hofmann <bashofmann@gmail.com> * [kube-prometheus-stack] Update default prometheus version to 2.19.2 Compatibility added in in 0.41.0 with prometheus-operator/prometheus-operator#3316 Signed-off-by: Bastian Hofmann <bashofmann@gmail.com> * [kube-prometheus-stack] Fix alertmanager.alertmanagerSpec.clusterAdvertiseAddress Signed-off-by: Bastian Hofmann <bashofmann@gmail.com> * [kube-prometheus-stack] Fix kubeVersion constraint for GKE and EKS Signed-off-by: Bastian Hofmann <bashofmann@gmail.com> * [kube-prometheus-stack] Update Prometheus to 2.21.0 Signed-off-by: Bastian Hofmann <bashofmann@gmail.com>
What this PR does / why we need it:
Update prometheus-operator to 0.42.1.
This also introduces a new
Probes
CRD. Since Helm does not create this new CRD on a chart upgrade automatically, the chart version is bumped to 10 to indicate the breaking change.Checklist
[prometheus-couchdb-exporter]
)