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
Some node types are unlikely to be in the owner hierarchy of a Pod: Service, Ingress, Route, Namespace. In the interest of keeping the Kubernetes permissions granted to Cryostat minimal, these permissions are not granted when deploying Cryostat with the operator.
If for some reason a user has a Pod owned by one of these unlikely parents, Cryostat will attempt to look up that parent and fail with insufficient permissions. This can lead to no targets being available in the targets dropdown (see exception in cryostatio/cryostat-operator#234). Even though it's unlikely, we should remove these KubernetesNodeTypes to ensure this can't happen.
The text was updated successfully, but these errors were encountered:
Some node types are unlikely to be in the owner hierarchy of a Pod: Service, Ingress, Route, Namespace. In the interest of keeping the Kubernetes permissions granted to Cryostat minimal, these permissions are not granted when deploying Cryostat with the operator.
If for some reason a user has a Pod owned by one of these unlikely parents, Cryostat will attempt to look up that parent and fail with insufficient permissions. This can lead to no targets being available in the targets dropdown (see exception in cryostatio/cryostat-operator#234). Even though it's unlikely, we should remove these
KubernetesNodeTypes
to ensure this can't happen.The text was updated successfully, but these errors were encountered: