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
Error: ClusterRoleBinding in version "v1" cannot be handled as a ClusterRoleBinding: v1.ClusterRoleBinding.Subjects: []v1.Subject: v1.Subject.Namespace: ReadString: expects " or n, but found 1, error found in #10 byte of ...|mespace":555555}]}
What you expected to happen:
Changed to 555555o and it worked, doesn't like all numeric namespaces
How to reproduce it:
Anything else we need to know:
/kind bug
The text was updated successfully, but these errors were encountered:
Error: ClusterRoleBinding in version "v1" cannot be handled as a ClusterRoleBinding: v1.ClusterRoleBinding.Subjects: []v1.Subject: v1.Subject.Namespace: ReadString: expects " or n, but found 1, error found in #10 byte of ...|mespace":55555}]}
|..., bigger context ...|t","name":"nginx-test-ingress-nginx","namespace":55555}]}
|...
NGINX Ingress controller version: 0.43.0
Kubernetes version (use
kubectl version
): 1.18.9Environment:
uname -a
):What happened:
Error: ClusterRoleBinding in version "v1" cannot be handled as a ClusterRoleBinding: v1.ClusterRoleBinding.Subjects: []v1.Subject: v1.Subject.Namespace: ReadString: expects " or n, but found 1, error found in #10 byte of ...|mespace":555555}]}
What you expected to happen:
Changed to 555555o and it worked, doesn't like all numeric namespaces
How to reproduce it:
Anything else we need to know:
/kind bug
The text was updated successfully, but these errors were encountered: