-
Notifications
You must be signed in to change notification settings - Fork 667
Bug 1891314: Return helm charts based on the installed kubernetes version #7012
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
Bug 1891314: Return helm charts based on the installed kubernetes version #7012
Conversation
pedjak
left a comment
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.
PR is not implemented according to https://issues.redhat.com/browse/HELM-12 acceptance criteria.
9c6a7cf to
8a605eb
Compare
|
/test backend |
|
/retest |
|
/retest |
pkg/helm/handlers/handlers.go
Outdated
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.
@akashshinde ^^
|
|
|
@akashshinde @pedjak I would prefer if we make it default that all chart are filtered based on compatibility as this is the direction that we are looking at for Helm catalog by default. It also removes the need to change the UI for this. We can have an option to send all charts unfiltered that UI can use when required but there is no need for fetching unfiltered charts right now so it would be great if we can consider that. |
|
@rohitkrai03 thanks for the feedback.. we can revert the default behaviour... |
pedjak
left a comment
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.
please look at the existing comments, there are still some unaddressed.
44afe28 to
500e7a2
Compare
|
/retitle Bug 1891314: Return helm charts based on the installed kubernetes version |
|
@akashshinde: This pull request references Bugzilla bug 1891314, which is valid. The bug has been moved to the POST state. The bug has been updated to refer to the pull request using the external bug tracker. 3 validation(s) were run on this bug
DetailsIn 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. |
|
/cherry-pick release-4.6 |
|
@pedjak: once the present PR merges, I will cherry-pick it on top of release-4.6 in a new PR and assign it to you. DetailsIn 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. |
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.
Usually a helm chart that support pre-release versions specifies kubeVersion range with a -0 at the end. Below is a helm chart metadata from our catalog that support pre-release version -
- apiVersion: v2
appVersion: 10.0.0
created: "2020-11-03T14:58:13.7979+05:30"
dependencies:
- alias: sch
name: ibm-sch
repository: '@sch'
version: 1.2.15
description: |-
IBM Order management Software Enterprise Edition v10 provides cross-channel order orchestration capabilities to enable intelligent brokering of orders across many disparate systems. It also provides a global view of inventory across the supply chain and enables business users to make changes to order process.
Documentation
For additional details regarding install parameters check http://ibm.biz/oms-helm-readme.
License
By installing this product you accept the license terms http://ibm.biz/oms-license and http://ibm.biz/oms-apps-license.
digest: 47f7bae2c23ceec955c497ddd3f1d2adeea08238363a849c3ffc0ebefb9125ff
home: http://ibm.biz/oms-home
icon: https://raw.githubusercontent.com/IBM/charts/master/logo/ibm-oms-logo.png
keywords:
- oms
- sterling
- yantra
- order
- fulfillment
- om
- amd64
- ppc64le
- framework
- Commercial
- RHOCP
- Other
kubeVersion: '>=1.16.0-0'
maintainers:
- name: IBM
name: ibm-oms-ent-prod
type: application
urls:
- https://redhat-developer.github.com/redhat-helm-charts/charts/ibm-oms-ent-prod-5.1.0.tgz
version: 5.1.0There 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.
Added 81e25d7
cc: @rohitkrai03
|
/assign |
|
@akashshinde I created a Added below apiVersion: helm.openshift.io/v1beta1
kind: HelmChartRepository
metadata:
name: ibm-sample-repo
spec:
name: ibm-sample-repo
connectionConfig:
url: https://raw.githubusercontent.com/IBM/charts/master/repo/ibm-helmThe repo has in total 38 charts in it's index.yaml. Out of 38 only 5 specifies Right now in the console i am getting all 38 Helm charts from the backend. So technically the above reported bug is fixed but I see the same number of charts in a cluster where no filtering is available so the filtering might not be working as expected. On a pre-release kubernetes cluster I would expect only those charts to show up which have Not sure how the filtering it working at the moment but i think there might be some issue here with the filtering. If you want i can share the cluster with you. |
If kubernetes pre-release cluster version is
|
81e25d7 to
c0040ab
Compare
|
After discussions with @akashshinde it seems the current filtering logic should work for all of our use cases. The above shared cluster has something wrong because it shows |
rohitkrai03
left a comment
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
|
@akashshinde: The following test failed, say
Full PR test history. Your PR dashboard. DetailsInstructions 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. I understand the commands that are listed here. |
|
/approve |
|
/assign @spadgett |
|
/retest |
|
@spadgett Can you take a look at this ? There are few changes in |
|
@christianvogt can you please take a look at this ? |
pkg/server/server.go
Outdated
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.
We'll want to make sure this is logged by default. @jhadvig Do you know offhand?
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.
We should fall back to the env var at least on failure.
pkg/server/server.go
Outdated
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 guess it's OK to check only once on startup since the API server is upgraded before the other cluster operators. There might be a small window during upgrades where we show charts for the previous version after the API servers are upgraded.
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.
Note that I believe the kube version is available as an environment variable in the pod, so we could conceivably avoid needing to make this request (although not for off-cluster mode).
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.
c0040ab to
739ad74
Compare
spadgett
left a comment
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
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: akashshinde, pedjak, rohitkrai03, spadgett The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
@akashshinde: All pull requests linked via external trackers have merged: Bugzilla bug 1891314 has been moved to the MODIFIED state. DetailsIn 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. |
|
@pedjak: #7012 failed to apply on top of branch "release-4.6": DetailsIn 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. |
onlyCompatibleflag is provided to/api/helm/charts/index.yamlAPI which drops the unsupported charts from the response.Ref: https://issues.redhat.com/browse/HELM-12