Skip to content

Fix helm upgrade secrets #16676

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.

Sign up for GitHub

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

Draft
sowmya-sl wants to merge 7 commits into
base: main
Choose a base branch
from
Draft

Fix helm upgrade secrets #16676

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
7 commits
Select commit Hold shift + click to select a range
f08c6e8
HELM-728: Persist auth secret across installs and upgrades
sowmya-sl May 12, 2026
e841cad
HELM-728: Persist auth secret annotation on chart during upgrade
sowmya-sl May 26, 2026
dd8f981
HELM-728: Apply auth credentials before LocateChart on upgrade
sowmya-sl May 26, 2026
e36fe62
HELM-728: Add auth secret selection to Helm upgrade form
sowmya-sl May 26, 2026
f9d8551
helm-plugin: add inline basic-auth Secret creation for URL chart flows
sowmya-sl Jun 19, 2026
2cb8b4c
WIP: tmp
sowmya-sl Jun 19, 2026
7468da3
HELM-728: standardize Helm release/chart copy and auth secret wording
sowmya-sl Jun 24, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions frontend/packages/helm-plugin/console-extensions.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -166,7 +166,7 @@
"groupId": "developer-catalog",
"href": "/catalog/ns/:namespace?catalogType=HelmChart",
"label": "%helm-plugin~Helm Chart%",
"description": "%helm-plugin~Browse the catalog to discover and install Helm Charts%",
"description": "%helm-plugin~Browse the catalog to discover and install Helm Chart(s)%",
"icon": { "$codeRef": "helmIcons.helmCatalogIconSVG" }
},
"flags": {
Expand Down Expand Up @@ -194,9 +194,9 @@
"type": "console.catalog/item-type",
"properties": {
"type": "HelmChart",
"title": "%helm-plugin~Helm Charts%",
"title": "%helm-plugin~Helm Chart(s)%",
"catalogDescription": { "$codeRef": "getHelmCatalogTypeDescription" },
"typeDescription": "%helm-plugin~**Helm Charts** are packages for deploying an Application or components of a larger Application.%",
"typeDescription": "%helm-plugin~**Helm Chart(s)** are packages for deploying an Application or components of a larger Application.%",
"filters": [
{
"label": "%helm-plugin~Chart Repositories%",
Expand All @@ -217,7 +217,7 @@
"properties": {
"catalogId": "dev-catalog",
"type": "HelmChart",
"title": "%helm-plugin~Helm Charts%",
"title": "%helm-plugin~Helm Chart(s)%",
"provider": { "$codeRef": "helmChartProvider" }
},
"flags": {
Expand Down
46 changes: 23 additions & 23 deletions frontend/packages/helm-plugin/integration-tests/features/helm-release.feature
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,27 +1,27 @@
@helm @smoke
Feature: Helm Release
Feature: Helm release
As a user, I want to perform actions on the helm release


@pre-condition
Scenario: Create or Select the project namespace
Given user is at the Helm Release tab in admin perspective
Given user is at the Helm release tab in admin perspective
And user has created or selected namespace "aut-ci-helm"


Scenario: Open the Helm tab on the navigation bar when helm charts are absent: HR-05-TC01
Given user is at administrator perspective
When user clicks on the Helm Release tab in admin perspective
Then user is able to see the message "No Helm Releases found"
When user clicks on the Helm release tab in admin perspective
Then user is able to see the message "No Helm releases found"
And user will get the link to install helm charts from software catalog


Scenario: Create Helm Release page details: HR-05-TC02
Scenario: Create Helm release page details: HR-05-TC02
Given user is at Software Catalog page
When user selects Helm Charts type from Software Catalog page
When user selects Helm Chart(s) type from Software Catalog page
And user searches and selects "Nodejs" card from catalog page
And user clicks on the Create button on side bar
Then Create Helm Release page is displayed
Then Create Helm release page is displayed
And release name displays as "nodejs"
And form view radio button is selected by default
And yaml view radio button is enabled
Expand All @@ -30,7 +30,7 @@ Feature: Helm Release

Scenario: Install Helm Chart from +Add Page using Form View: HR-06-TC04
Given user is at Software Catalog page
When user selects Helm Charts type from Software Catalog page
When user selects Helm Chart(s) type from Software Catalog page
And user searches and selects "Nodejs" card from catalog page
And user clicks on the Create button on side bar
And user enters Release Name as "nodejs-release"
Expand All @@ -40,7 +40,7 @@ Feature: Helm Release


Scenario: Helm release status verification: HR-01-TC04
Given user is at the Helm Release tab in admin perspective
Given user is at the Helm release tab in admin perspective
And user is able to see "nodejs-release" in helm page in admin view
And user is able to see the status and status icon of "nodejs-release" under helm releases tab
And user is able to see the "PendingInstall", "PendingUpgrade" and "PendingRollback" options under filter bar
Expand All @@ -53,33 +53,33 @@ Feature: Helm Release
Scenario: Context menu options of helm release: HR-01-TC01
Given user is at the Topology page
When user right clicks on the helm release "nodejs-release" to open the context menu
Then user is able to see the context menu with actions Upgrade and Delete Helm Release
Then user is able to see the context menu with actions Upgrade and Delete Helm release


Scenario: Open the Helm tab on the navigation bar when helm charts are present: HR-05-TC05
Given user is at the Helm Release tab in admin perspective
Given user is at the Helm release tab in admin perspective
Then user will see the helm charts listed


Scenario: Filter out deployed Helm Charts: HR-05-TC06
Given user is at the Helm Release tab in admin perspective
Scenario: Filter out deployed Helm Chart(s): HR-05-TC06
Given user is at the Helm release tab in admin perspective
When user clicks on the filter drop down
And user selects checkbox for the "Deployed" Helm charts
Then the checkbox for the "Deployed" Helm chart is checked
And user selects checkbox for the "Deployed" Helm Charts
Then the checkbox for the "Deployed" Helm Chart is checked
And helm charts with status "Deployed" are listed


Scenario: Helm release details page: HR-05-TC13
Given user is at the Helm Release tab in admin perspective
Given user is at the Helm release tab in admin perspective
When user clicks on the helm release name "nodejs-release"
Then user will see the Details page opened
And user will see the Resources tab
And user will see the Revision History tab
And user will see the Release Notes tab
And user will see the Actions drop down menu with options Upgrade, Rollback, and Delete Helm Release
And user will see the Actions drop down menu with options Upgrade, Rollback, and Delete Helm release


Scenario: Perform Upgrade action on Helm Release through Context Menu: HR-08-TC04
Scenario: Perform Upgrade action on Helm release through Context Menu: HR-08-TC04
Given user is at the Topology page
When user right clicks on the helm release "nodejs-release" to open the context menu
And user clicks on the "Upgrade" action
Expand All @@ -91,7 +91,7 @@ Feature: Helm Release
Scenario: Actions menu on Helm page after helm chart upgrade: HR-08-TC01
Given user is on the Helm page with helm release "nodejs-release"
When user clicks on the Kebab menu
Then user is able to see kebab menu with actions Upgrade, Rollback and Delete Helm Release
Then user is able to see kebab menu with actions Upgrade, Rollback and Delete Helm release


Scenario: Perform the helm chart upgrade for already upgraded helm chart : HR-08-TC02
Expand All @@ -100,10 +100,10 @@ Feature: Helm Release
And user clicks on the "Upgrade" action
And user upgrades the chart Version
And user clicks on the upgrade button
Then user will be redirected to Helm Releases page under Helm tab
Then user will be redirected to Helm releases page under Helm tab


Scenario: Perform Rollback action on Helm Release through Context Menu: HR-08-TC03
Scenario: Perform Rollback action on Helm release through Context Menu: HR-08-TC03
Given user is at the Topology page
And user is on the topology sidebar of the helm release "nodejs-release"
When user clicks on the Actions drop down menu
Expand All @@ -113,10 +113,10 @@ Feature: Helm Release
Then user will be redirected to Topology page


Scenario: Delete Helm Release through Context Menu: HR-01-TC03
Scenario: Delete Helm release through Context Menu: HR-01-TC03
Given user is at the Topology page
When user right clicks on the helm release "nodejs-release" to open the context menu
And user clicks on the "Delete Helm Release" action
And user clicks on the "Delete Helm release" action
And user enters the release name "nodejs-release"
And user clicks on the Delete button
Then user will be redirected to Topology page
10 changes: 5 additions & 5 deletions ...helm-plugin/integration-tests/features/helm/actions-on-helm-release-after-upgrade.feature
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,13 +1,13 @@
@helm @smoke
Feature: Verify the Actions on Helm Release after upgrade
Feature: Verify the Actions on Helm release after upgrade
As a user, I want to perform the actions on the helm releases in topology page

Background:
Given user has created or selected namespace "aut-helm"


@pre-condition
Scenario: Perform Upgrade action on Helm Release through Context Menu: HR-08-TC04
Scenario: Perform Upgrade action on Helm release through Context Menu: HR-08-TC04
Given user has installed helm chart "Nodejs" with helm release name "nodejs-release-1"
And user is at the Topology page
When user right clicks on the helm release "nodejs-release-1" to open the context menu
Expand All @@ -19,18 +19,18 @@ Feature: Verify the Actions on Helm Release after upgrade
Scenario: Actions menu on Helm page after helm chart upgrade: HR-08-TC01
Given user is on the Helm page with helm release "nodejs-release-1"
When user clicks on the Kebab menu
Then user is able to see kebab menu with actions Upgrade, Rollback and Delete Helm Release
Then user is able to see kebab menu with actions Upgrade, Rollback and Delete Helm release


Scenario: Perform the helm chart upgrade for already upgraded helm chart : HR-08-TC02
Given user is on the Helm page with helm release "nodejs-release-1"
When user clicks on the Kebab menu
And user clicks on the "Upgrade" action
And user clicks on the upgrade button
Then user will be redirected to Helm Releases page
Then user will be redirected to Helm releases page


Scenario: Perform Rollback action on Helm Release through Context Menu: HR-08-TC03
Scenario: Perform Rollback action on Helm release through Context Menu: HR-08-TC03
Given user is at the Topology page
And user is on the topology sidebar of the helm release "nodejs-release-1"
When user clicks on the Actions drop down menu
Expand Down
10 changes: 5 additions & 5 deletions ...tend/packages/helm-plugin/integration-tests/features/helm/actions-on-helm-release.feature
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,5 +1,5 @@
@helm @smoke
Feature: Perform Actions on Helm Releases
Feature: Perform Actions on Helm releases
As a user, I want to perform the actions on the helm releases in topology page

Background:
Expand All @@ -21,19 +21,19 @@ Feature: Perform Actions on Helm Releases
Scenario: Context menu options of helm release: HR-01-TC01
Given user is at the Topology page
When user right clicks on the helm release "nodejs-release-2" to open the context menu
Then user is able to see the context menu with actions Upgrade and Delete Helm Release
Then user is able to see the context menu with actions Upgrade and Delete Helm release


Scenario: Actions menu on Helm page: HR-01-TC02
Given user is on the Helm page with helm release "nodejs-release-2"
When user clicks on the Kebab menu
Then user is able to see kebab menu with actions Upgrade, Rollback and Delete Helm Release
Then user is able to see kebab menu with actions Upgrade, Rollback and Delete Helm release


Scenario: Delete Helm Release through Context Menu: HR-01-TC03
Scenario: Delete Helm release through Context Menu: HR-01-TC03
Given user is at the Topology page
When user right clicks on the helm release "nodejs-release-2" to open the context menu
And user clicks on the "Delete Helm Release" action
And user clicks on the "Delete Helm release" action
And user enters the release name "nodejs-release-2"
And user clicks on the Delete button
Then user will be redirected to Topology page
Expand Down
4 changes: 2 additions & 2 deletions frontend/packages/helm-plugin/integration-tests/features/helm/helm-compatibility.feature
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -11,7 +11,7 @@ Feature: Helm Chart
Scenario: Compatible helm charts: HR-02-TC01
Given user is at Add page
When user clicks on the Helm Chart card on the Add page
Then user redirects to Helm Charts page
Then user redirects to Helm Chart(s) page
And user is able to see helm charts


Expand All @@ -26,6 +26,6 @@ Feature: Helm Chart

@regression @manual
Scenario: Check the chart versions in the chart version dropdown if they are compatible with the cluster: HR-02-TC03
Given user is at the Create Helm Release page
Given user is at the Create Helm release page
When user clicks on the Chart Version dropdown menu
Then user will see the chart versions which are compatible with the kubeversion of the cluster
4 changes: 2 additions & 2 deletions frontend/packages/helm-plugin/integration-tests/features/helm/helm-feature-flag.feature
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -17,7 +17,7 @@ Feature: Feature flag for Helm
And user clicks on Save
Then user is not able to see the Helm tab in the navigation menu
And user can not see Helm Chart card in Add page
And user can not see Helm Charts filter in the Software Catalog page
And user can not see Helm Chart(s) filter in the Software Catalog page


@regression @manual
Expand All @@ -30,4 +30,4 @@ Feature: Feature flag for Helm
And user clicks on Save
Then user is able to see the Helm tab in the navigation menu
And user can see Helm Chart card in Add page
And user can see Helm Charts filter in the Software Catalog page
And user can see Helm Chart(s) filter in the Software Catalog page
4 changes: 2 additions & 2 deletions frontend/packages/helm-plugin/integration-tests/features/helm/helm-installation-view.feature
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -20,7 +20,7 @@ Feature: Helm Chart Installation View

@manual
Scenario: Switch from YAML to Form view: HR-04-TC02
Given user is at the Create Helm Release page
Given user is at the Create Helm release page
When user selects the YAML view
And user does some changes in the yaml for helm chart
And user selects the Form view
Expand All @@ -41,7 +41,7 @@ Feature: Helm Chart Installation View
Then user will see Release Name, Replica count as "nodejs-release-3", "3" respectively

@regression
Scenario: When Helm Release is not configurable: HR-04-TC04
Scenario: When Helm release is not configurable: HR-04-TC04
Given user is at Add page
When user selects "Helm Chart" card from add page
And user searches and selects "Httpd Imagestreams" card from catalog page
Expand Down
36 changes: 18 additions & 18 deletions frontend/packages/helm-plugin/integration-tests/features/helm/helm-navigation.feature
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
@helm
Feature: Navigations on Helm Chart
As a user, I want to navigate to different pages related to Helm Charts
As a user, I want to navigate to different pages related to Helm Chart(s)

Background:
Given user has created or selected namespace "aut-helm"
Expand All @@ -11,17 +11,17 @@ Feature: Navigations on Helm Chart
Scenario: Open the Helm tab on the navigation bar when helm charts are absent: HR-05-TC01
When user clicks on the Helm tab in dev perspective
Then user will be redirected to Helm releases page
And user is able to see the message "No Helm Releases found"
And user is able to see the message "No Helm releases found"
And user will get the link to install helm charts from software catalog


@smoke
Scenario: Create Helm Release page details: HR-05-TC02
Scenario: Create Helm release page details: HR-05-TC02
Given user is at Add page
When user selects "Helm Chart" card from add page
And user searches and selects "Nodejs" card from catalog page
And user clicks on the Create button on side bar
Then Create Helm Release page is displayed
Then Create Helm release page is displayed
And release name displays as "nodejs"
And form view radio button is selected by default
And yaml view radio button is enabled
Expand All @@ -30,7 +30,7 @@ Feature: Navigations on Helm Chart

@smoke
Scenario: Yaml view editor for Install Helm Chart page: HR-05-TC03
Given user is at Create Helm Release page
Given user is at Create Helm release page
When user selects YAML view
Then user is able to see YAML editor

Expand All @@ -55,45 +55,45 @@ Feature: Navigations on Helm Chart


@regression
Scenario: Filter out deployed Helm Charts: HR-05-TC06
Scenario: Filter out deployed Helm Chart(s): HR-05-TC06
Given user is at the Helm page
When user clicks on the filter drop down
And user selects checkbox for the "Deployed" Helm charts
Then the checkbox for the "Deployed" Helm chart is checked
And user selects checkbox for the "Deployed" Helm Charts
Then the checkbox for the "Deployed" Helm Chart is checked
And helm charts with status "Deployed" are listed


@regression @manual
Scenario: Filter out failed Helm Charts: HR-05-TC07
Scenario: Filter out failed Helm Chart(s): HR-05-TC07
Given user is at the Helm page
When user clicks on the filter drop down
And user selects checkbox for the "Failed" Helm charts
Then the checkbox for the "Failed" Helm chart is checked
And user selects checkbox for the "Failed" Helm Charts
Then the checkbox for the "Failed" Helm Chart is checked
And helm charts with status "Failed" are listed


@regression @manual
Scenario: Filter out other Helm charts: HR-05-TC08
Scenario: Filter out other Helm Charts: HR-05-TC08
Given user is at the Helm page
When user clicks on the filter drop down
And user selects checkbox for the "Other" Helm charts
Then the checkbox for the "Other" Helm chart is checked
And user selects checkbox for the "Other" Helm Charts
Then the checkbox for the "Other" Helm Chart is checked
And helm charts with status "Other" are listed


@regression
Scenario: Select all filters: HR-05-TC09
Given user is at the Helm page
When user clicks on the filter drop down
And user selects checkbox for the "All" Helm charts
Then the checkbox for the "All" Helm chart is checked
And user selects checkbox for the "All" Helm Charts
Then the checkbox for the "All" Helm Chart is checked


@regression
Scenario: Clear all filters: HR-05-TC10
Given user is at the Helm page
When user clicks on the filter drop down
And user selects checkbox for the "All" Helm charts
And user selects checkbox for the "All" Helm Charts
And user clicks on the clear all filters button
Then "All" filters selected will get removed

Expand All @@ -113,4 +113,4 @@ Feature: Navigations on Helm Chart
And user will see the Resources tab
And user will see the Revision History tab
And user will see the Release Notes tab
And user will see the Actions drop down menu with options Upgrade, Rollback, and Delete Helm Release
And user will see the Actions drop down menu with options Upgrade, Rollback, and Delete Helm release
Loading