We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
"Forward port" is stuck pending when permissions are restricted using a similar ClusterRole:
apiVersion: rbac.authorization.k8s.io/v1 kind: ClusterRole metadata: name: developers-extended rules: - apiGroups: - "*" resources: - "*" verbs: - list - get - watch - apiGroups: - "" resources: - pods/portforward verbs: - get - list - create
Steps to reproduce the bug:
Expected results: port is forwarded or an error message is shown
No
Works using kubectl port-forward svc/myservice 8080:80 and in aptakube using the same kubeconfig in both cases, but doesn't work with Headlamp.
kubectl port-forward svc/myservice 8080:80
Works as expected with Headlamp using cluster admin kubeconfig (using TLS client auth).
The text was updated successfully, but these errors were encountered:
#2936 could be related, as I was using a service account with a token
Sorry, something went wrong.
Having issues as well the fixes in 0.28.1 related to port forward did not fix for me
Having issues as well the fixes in 0.28.1 related to port forward did not work. It just get the Spinning wheel that it is trying.
still not working for me in 0.29.0
No branches or pull requests
Describe the bug
"Forward port" is stuck pending when permissions are restricted using a similar ClusterRole:
To Reproduce
Steps to reproduce the bug:
Expected results: port is forwarded or an error message is shown
Environment (please provide info about your environment):
Are you able to fix this issue?
No
Additional Context
Works using
kubectl port-forward svc/myservice 8080:80
and in aptakube using the same kubeconfig in both cases, but doesn't work with Headlamp.Works as expected with Headlamp using cluster admin kubeconfig (using TLS client auth).
The text was updated successfully, but these errors were encountered: