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

Bug: Showing incorrect manifest on app details page for 2 namespaces #9

Open
1 task done
rishabhtayal72 opened this issue Aug 27, 2023 · 0 comments · May be fixed by #15
Open
1 task done

Bug: Showing incorrect manifest on app details page for 2 namespaces #9

rishabhtayal72 opened this issue Aug 27, 2023 · 0 comments · May be fixed by #15

Comments

@rishabhtayal72
Copy link
Owner

rishabhtayal72 commented Aug 27, 2023

📜 Description

Showing incorrect manifest on app details page if 2 similar named k8s objects are deployed in 2 different namespaces.

👟 Reproduction steps

  1. Create 2 service accounts with the same name in 2 different namespaces.
  2. Deploy and go to the app details page.
  3. Comparing the manifests for the 2 service accounts, it'll appear both are same, meaning both manifests will belong to the same namespace.

👍 Expected behavior

metadata.namespace should have been different for the 2 identical objects.

👎 Actual Behavior

metadata.namespace are same. Meaning both manifests are shown for same object.

☸ Kubernetes version

EKS 1.24

Cloud provider

AWS

🌍 Browser

Chrome

🧱 Your Environment

NA

✅ Proposed Solution

NA

👀 Have you spent some time to check if this issue has been raised before?

  • I checked and didn't find any similar issue
@rishabhtayal72 rishabhtayal72 changed the title Bug: Showing incorrect manifest on app details page if 2 same named k8s objects are deployed in 2 different namespaces Bug: Showing incorrect manifest on app details page for 2 namespaces Aug 29, 2023
This was referenced Aug 29, 2023
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