[
https://issues.apache.org/jira/browse/FLINK-31493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-31493:
-----------------------------------
Labels: helm stale-major (was: helm)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issues has been marked as
Major but is unassigned and neither itself nor its Sub-Tasks have been updated
for 60 days. I have gone ahead and added a "stale-major" to the issue". If this
ticket is a Major, please either assign yourself or give an update. Afterwards,
please remove the label or in 7 days the issue will be deprioritized.
> helm upgrade does not work, because repo path does not follow helm standards
> ----------------------------------------------------------------------------
>
> Key: FLINK-31493
> URL: https://issues.apache.org/jira/browse/FLINK-31493
> Project: Flink
> Issue Type: Bug
> Components: Kubernetes Operator
> Reporter: Emmanuel Leroy
> Priority: Major
> Labels: helm, stale-major
>
> the helm repo for flink-operator is a folder that includes the version, which
> is not following the helm chart repo standards.
> In a standard helm repo, the repo URL is the name of the product (without
> version) and then the folder includes the different versions of the chart.
> This is an issue because the repo itself needs to be installed every time the
> version is upgraded, as opposed to adding the repo once and then upgrading
> the version.
> When attempting to add the latest repo, helm will complain that the repo
> already exists. It is necessary to first remove the repo, and then add the
> updated one.
> When trying to upgrade the chart, it doesn't work, because helm expects the
> chart of the previous version to be in the same repo, but it cannot be found
> in the newly added repo.
> So the chart needs to be uninstalled, then the new one installed.
> The solution is to use a common path for all versions of the chart, and
> maintain a manifest with the various versions (instead of different folders
> with different manifests)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
