Skip to content
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

Resources listing for Helm charts breaks if the chart refers to another namespace #486

Open
cienijr opened this issue Nov 22, 2024 · 0 comments · May be fixed by #487
Open

Resources listing for Helm charts breaks if the chart refers to another namespace #486

cienijr opened this issue Nov 22, 2024 · 0 comments · May be fixed by #487

Comments

@cienijr
Copy link

cienijr commented Nov 22, 2024

I was originally going to open this issue at rancher/dashboard, but I started going through the code and realized the problem was actually here.

The summarizer for apps.catalog.cattle.io is not properly setting the namespace of deployed Helm resources. When the relationships are processed by steve, it fallbacks to the using namespace of the release, since there's nothing set on the summary.

Below are extra info that I was originally gonna report to rancher/dashboard:

Describe the bug
On the Resources tab of Installed App, the UI is ignoring the namespace of the resources deployed with Helm and instead lists the release namespace for all of them. This not only results in incorrect display, but also when clicking in a given resource it uses the wrong namespace as well, resulting in an error page.

Expected Result
The interface should list the correct namespaces for each deployed resource and the links should also point to the right namespace.

Screenshots
In this screenshot, both ecr-credentials-updater-aws-registry-kube-system and ecr-credentials-updater-aws-registry-test-namespace RoleBindings belong to kube-system and test-namespace, respectively. But the UI wrongly points to av-infra (the namespace that the chart is installed to).

image

When clicking on one of them, it results in an error, since its trying to get the resource from the wrong namespace:
image

Here's a few screenshots from the API viewer:

At spec.resources, all entries have their namespace properly set:
image

But the metadata.relationships used by the UI is wrong - all resources are prefixed with av-infra, instead of the correct namespaces:
image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant