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
the script returns immediately without any output.
Trying to do the same thing in another project with a CRD named toolchain which has a service account with a role which only allows access to that resource I get the following response.
{
"kind": "Status",
"apiVersion": "v1",
"metadata": {},
"status": "Failure",
"message": "watch.stable.liatr.io \"toolchains\" is forbidden: User \"system:serviceaccount:toolchain:operator-slack\" cannot get resource \"watch\" in API group \"stable.liatr.io\" in the namespace \"toolchain\"",
"reason": "Forbidden",
"details": {
"name": "toolchains",
"group": "stable.liatr.io",
"kind": "watch"
},
"code": 403
}
If I add a resource named watch to my role I do not get any response at all so my guess is that the client is sending "watch" instead of the resource name to the Kubernetes API.
The text was updated successfully, but these errors were encountered:
iffyio
added a commit
to iffyio/kubernetes-client
that referenced
this issue
May 19, 2019
Currently, URLs for namespaced watches for CRD
objects are incorrectly formatted (the result instead
tries to do a GET on a CRD named `watch`), causing k8s to
return a 404.
This patch corrects this issue
Fixesgodaddy#468
Currently, URLs for namespaced watches for CRD
objects are incorrectly formatted (the result instead
tries to do a GET on a CRD named `watch`), causing k8s to
return a 404.
This patch corrects this issue
Fixes#468
Using the deployment-notifier.js example works but if I change
to
the script returns immediately without any output.
Trying to do the same thing in another project with a CRD named toolchain which has a service account with a role which only allows access to that resource I get the following response.
If I add a resource named watch to my role I do not get any response at all so my guess is that the client is sending "watch" instead of the resource name to the Kubernetes API.
The text was updated successfully, but these errors were encountered: