-
Notifications
You must be signed in to change notification settings - Fork 16.8k
[stable/prometheus] migrate API versions from deprecated, removed versions #17268
Conversation
Hi @oke-py. Thanks for your PR. I'm waiting for a helm 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. |
/assign @mgoodness |
(Sadly..). This might be worth creating a new variable cause I suspect there are simply too many people on older k8s still.. Just throwing that in, I'm worried about a flood of PRs afterwards asking for "legacy support" |
@starkers All right. I'll try it. |
PodSecurityPolicy policy/v1beta1 API, available since v1.10. |
Ahh geat! Sorry, I should have looked this up before FUD, those are ancient! Then this should be a really good fix |
@starkers I pushed update. PTAL |
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.
{{- if semverCompare ">=1.3-0, <1.10-0" .Capabilities.KubeVersion.GitVersion -}} | ||
{{- print "extensions/v1beta1" -}} | ||
{{- else if semverCompare "^1.10-0" .Capabilities.KubeVersion.GitVersion -}} | ||
{{- print "policy/v1beta1 " -}} |
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.
Super nit-pick: potential extra space here (almost certainly harmless).
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.
@zaneclaes I fixed it. thx
/ok-to-test |
stable/prometheus/Chart.yaml
Outdated
@@ -1,6 +1,6 @@ | |||
apiVersion: v1 | |||
name: prometheus | |||
version: 9.1.1 | |||
version: 9.1.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.
With a change as complex as the apiVersion
, and the introduction of the requirement for Tiller via the .Capabilities
call, I feel this should be more than a patch version change.
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.
9.2.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.
@WarheadsSE I updated the version to 9.2.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.
Minor version upgrade seems right to me for this. I'm unclear on the tide
check, but looks like we need the lgtm
to come from a maintainer..?
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.
@zaneclaes yes, it requires /lgtm
comment from a maintainer.
Silliest question of the PR: how many people are actively using clusters before k8s 1.10? |
@WarheadsSE I'm not sure, but this PR also supports versions prior to 1.10. |
@oke-py And I appreciate that 🙇♂️ TL;DR: TIL @starkers for the sake of my own clarity, can you explain (or point to doc/code) how The problem is then that even with a k8s cluster running 1.16.0, they will end up with objects not compatible when using Helm v2 in any released version.
|
Without tiller I'm actually not sure if or how On the other hand I feel that the majority of people are using tiller.. So the pragmatic thing should be to support this use-case first.. Mostly because this chart is currently broken for anyone with a "current" cluster.. For those who are templating... Perhaps there is a helm way of setting such a value so the template can be updated in one command, however with absolute certainty (because they're already having to maintain their own definition (I assume in git) it's just one sed command for them to fix right? |
it's better to avoid using |
No, the use is viable here. It is just a note that those not using tiller
must manually specify a version greater than 1.9.0 👍
|
@oke-py: GitHub didn't allow me to assign the following users: mgoodness. Note that only helm members, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time. In response to this:
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. |
…sions Signed-off-by: Naoki Oketani <okepy.naoki@gmail.com>
…lper.tpl Signed-off-by: Naoki Oketani <okepy.naoki@gmail.com>
…in helper.tpl Signed-off-by: Naoki Oketani <okepy.naoki@gmail.com>
Signed-off-by: Naoki Oketani <okepy.naoki@gmail.com>
Signed-off-by: Naoki Oketani <okepy.naoki@gmail.com>
/assign @davidkarlsen |
anything still outstanding here to push this along? It's a show stopper for deployment on 1.16 |
@davidkarlsen @mgoodness @gianrubio Could you please review and merge? |
@oke-py ---- Friday, October 18th ---- goodness 10:09 PM zanhsieh 10:10 PM |
Yes, I know, but I found he closed some PRs for stable/prometheus, and so I asked him to do the same for this PR.
What link do you mean? helm members?
What should we do? I can be one of the maintainers? |
This one: https://github.com/helm/charts/blob/master/stable/prometheus/OWNERS
Yes you could, but you need to get this PR or have any previous PR passed in this chart, then open another modification PR to OWNERS file w/ adding yourself to it (of course chart version needs to get bump to latest). Finally asked a helm member to LGTM. See: Once helm member received your PR for adding owners, he should invite you to helm chart org., then PR merged. After that you should be able to LGTM this chart PR. |
I've checked out this file. So, who can review & merge this PR? |
@oke-py |
Any updates on this? |
@gianrubio you are the latest addition to the reviewer team, can you review this long awaited PR ? |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: maorfr, oke-py 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 |
…sions (helm#17268) * [stable/prometheus] migrate API versions from deprecated, removed versions Signed-off-by: Naoki Oketani <okepy.naoki@gmail.com> * [stable/prometheus] set prometheus.podSecurityPolicy.apiVersion in helper.tpl Signed-off-by: Naoki Oketani <okepy.naoki@gmail.com> * [stable/prometheus] set prometheus.{deployment,daemonset}.apiVersion in helper.tpl Signed-off-by: Naoki Oketani <okepy.naoki@gmail.com> * trim whitespace Signed-off-by: Naoki Oketani <okepy.naoki@gmail.com> * [stable/prometheus] bump minor version Signed-off-by: Naoki Oketani <okepy.naoki@gmail.com>
Is this a new chart
What this PR does / why we need it:
In k8s v1.16 some APIs are deprecated and removed.
https://kubernetes.io/blog/2019/07/18/api-deprecations-in-1-16/
As a result, installation failed. I migrate to use supported API versions.
Which issue this PR fixes
(optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close that issue when PR gets merged)Special notes for your reviewer:
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]
[stable/chart]
)