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: User in group doesn't get permission to resources in Kubernetes namespace, when the group permissions are updated #4885

Closed
2 tasks done
mahesh-hegde opened this issue Apr 5, 2024 · 1 comment
Assignees
Labels
bug Something isn't working

Comments

@mahesh-hegde
Copy link

📜 Description

This bug occurs once in a while randomly.

We have a fairly normal setup with bunch of groups which provide permissions to kubernetes namespaces.

When we add a new namespace to the group G, the user in Group G is not able to see the newly added namespace.

But when I go to users page, remove the user from said group G, and re-add to the group, the user is able to see the group again.

It appears like a caching related issue.

👟 Reproduction steps

Was not able to reproduce it reliably since it occurs pretty rarely, like once in a two weeks.

👍 Expected behavior

As soon as new kubernetes namespace access is added to the group, user belonging to the group should be able to access the resources in the namespace.

👎 Actual Behavior

The user is not seeing the namespace, until we remove them from the group and re-add to the group.

☸ Kubernetes version

v1.28.2

Cloud provider

Oracle Cloud (OCI)

🌍 Browser

Chrome

🧱 Your Environment

No

✅ Proposed Solution

This might have to do with the caching or permission update mechanisms. Not familiar with the inner workings of devtron, therefore cannot decide a proposed solution. :)

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

  • I checked and didn't find any similar issue

🏢 Have you read the Code of Conduct?

@mahesh-hegde mahesh-hegde added the bug Something isn't working label Apr 5, 2024
@abhibhaw
Copy link
Member

abhibhaw commented Oct 3, 2024

Hey @mahesh-hegde did you encounter this issue again recently? I believe this has been resolved. Feel free to reopen if this still exists.

@abhibhaw abhibhaw closed this as completed Oct 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants