Open Heaven25333 opened 4 months ago
@Heaven25333 I think this is due to the lack of RBAC permissions for the user, grant the required role/permissions to the user and this error will be resolved. https://kubernetes.io/docs/reference/access-authn-authz/rbac/#kubectl-create-rolebinding
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle rotten
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten
What happened ( ):
Anything else we need to know?:I have two versions of k8s here, one is version 1.24 and the other is version 1.26. When I call the API to query the deployment information, the 1.24 version can work normally, but the 1.26 version will return 403. Please help me check
Environment:
1.26
):29.0.0
)