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
Describe the bug
When launching a Testkube test from within a Kubernetes job on a self-hosted Testkube instance using cluster client configuration, the operation fails with a permission error.
Apply the job: kubectl -n testkube apply -f job.yaml
See error:
error: services "testkube-api-server:8088" is forbidden: User "system:serviceaccount:testkube:default" cannot get resource "services/proxy" in API group "" in the namespace "testkube": Azure does not have opinion for this user.)
Attempt to provide missing access rights by defining the following ClusterRole and ClusterRoleBinding:
hey, @aletv8 Testkube version is too old, we don't support such old ones. You need to use either direct option for your client connection or provide enough RBAC for your job to be able to access services/proxy
Describe the bug
When launching a Testkube test from within a Kubernetes job on a self-hosted Testkube instance using cluster client configuration, the operation fails with a permission error.
To Reproduce
Steps to reproduce the behavior:
job.yaml
resource:kubectl -n testkube apply -f job.yaml
Expected behavior
The Job should execute the test successfully, leveraging the provided ClusterRole and ClusterRoleBinding for the permissions.
Version / Cluster
The text was updated successfully, but these errors were encountered: