You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
📜 Description
Showing incorrect manifest on app details page if 2 similar named k8s objects are deployed in 2 namespaces...
👟 Reproduction steps
Create 2 service accounts with the same name in 2 different namespaces.
Deploy and go to the app details page.
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
Details
🌍 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
The text was updated successfully, but these errors were encountered:
rishabhtayal72
changed the title
Showing incorrect manifest on app details page
Showing incorrect manifest on app details page for 2 same names k8s objects
Aug 29, 2023
📜 Description
Showing incorrect manifest on app details page if 2 similar named k8s objects are deployed in 2 namespaces...
👟 Reproduction steps
Create 2 service accounts with the same name in 2 different namespaces.
Deploy and go to the app details page.
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
Details
🌍 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
The text was updated successfully, but these errors were encountered: