-
Notifications
You must be signed in to change notification settings - Fork 157
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
Unable to see the replicasets and pods using admin user #4206
Comments
I see the following errors in logs,
|
Hi! I am not administrator, neither developer, nor consultant from Weave. So the below only my POV:
|
@gecube, thank you for the comments. I can get it working using an external ingress with AWS Cognito integration, but I need to authenticate using the admin creds that log me in without access to the pods. If weave gitops doesn't show the pods, then it's useless for us. By reading the documentation, they mentioned it shows the pods, replicasets, etc. I do see deployments and other k8s objects except pods and replicaset. I am assuming it might be due to the permission issue. |
Hm. strange... maybe I am wrong.. I checked the docs for weave gitops... Please take a look Here: https://github.com/weaveworks/weave-gitops/blob/main/doc/img/02-workload-detail.png we don't see any rs and pods but here: https://github.com/weaveworks/weave-gitops/blob/main/doc/img/03-graph.png we see. It is very interesting, which permission do have weave gitops itself, as it utilises RBAC of k8s. Let's say you don't have for your OIDC user permission in RBAC of k8s to see deployments, and then weave gitops won't allow you to see them. |
I think the issue is that it was compiled against old fluxcd library versions: 591cc3d |
I understand as I have already upgraded the Flux version to 2.30, and I can see the helmrelease API version is v2 and the kustomize API version is v1, all latest. |
Weave GitOps is in need of maintainers! Thank you for the feedback, it is good to understand as an outsider (who does not use ArgoCD) what is it that people mean when they say "an Argo-style UI" - it's never been as clear to me as it is right now. Is that the main feature you're looking for in a UI? The ability to see drill-down dependencies or parent-child relationships between objects, and to see (for example) the fact that a pod is stuck in crashloopbackoff? |
It would be beneficial for developers to have a UI portal to manage helm releases, live deployments, and replicasets in addition to the Flux CLI. |
I'm working with some Headlamp devs to get the Flux plugin into the catalog, it's making some excellent progress It's currently a bit of a lift to get it installed, but if you're interested in trying it out, all of the information is here It is heavily inspired by Weave GitOps (the flux parts, anyway) |
There are 2 different questions here,
I can log in via both authentications but cannot see the replicasets and pods.
If I try to bypass the adminUser, the pod fails with CrashLoopRecovery.
Can I bypass the adminUser as I can login via AD OIDC?
How can I see the replicasets, pods and pod logs?
I have checked the RBAC clusterRole and have allowed full access and added admin user to impersonationResourceNames list.
Environment
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Actual Behavior
I'm not seeing any of these, except the deployments, helm releases.
Additional Context (screenshots, logs, etc)
The text was updated successfully, but these errors were encountered: