-
Notifications
You must be signed in to change notification settings - Fork 790
Closed
Description
Fission/Kubernetes version
$ fission version client: fission/core: BuildDate: "2024-01-14T15:43:35Z" GitCommit: 7e8d5dd7 Version: v1.20.1 server: fission/core: BuildDate: "2024-01-14T15:43:35Z" GitCommit: 7e8d5dd7 Version: v1.20.1 $ kubectl version Client Version: version.Info{Major:"1", Minor:"24", GitVersion:"v1.24.17", GitCommit:"22a9682c8fe855c321be75c5faacde343f909b04", GitTreeState:"clean", BuildDate:"2023-08-23T23:44:35Z", GoVersion:"go1.20.7", Compiler:"gc", Platform:"linux/amd64"} Kustomize Version: v4.5.4 Server Version: version.Info{Major:"1", Minor:"24", GitVersion:"v1.24.17", GitCommit:"22a9682c8fe855c321be75c5faacde343f909b04", GitTreeState:"clean", BuildDate:"2023-08-23T23:37:25Z", GoVersion:"go1.20.7", Compiler:"gc", Platform:"linux/amd64"}
Kubernetes platform (e.g. Google Kubernetes Engine)
Standard Kubernetes installed manually.
Describe the bug
When installing fission in the fission
namespace, everything works. But when installing it in another namespace, the fission check
command fails event though I can create and test functions properly:
$ fission check
fission-services
--------------------
× failed to get executor deployment status
× failed to get router deployment status
× failed to get storagesvc deployment status
Error: Error found: failed to get webhook deployment status
× failed to get webhook deployment status
fission-version
--------------------
√ fission is up-to-date
Event though the deployments are ok:
$ kubectl get deployments
NAME READY UP-TO-DATE AVAILABLE AGE
buildermgr 1/1 1 1 4m16s
executor 1/1 1 1 4m16s
kubewatcher 1/1 1 1 4m16s
mqtrigger-keda 1/1 1 1 4m16s
router 1/1 1 1 4m16s
storagesvc 1/1 1 1 4m16s
timer 1/1 1 1 4m16s
webhook 1/1 1 1 4m16s
Using fission check -n
does not fix the issue.
To Reproduce
Install Fission 1.20.1 with this values.yaml:
builderNamespace: mynamespace
functionNamespace: mynamespace
defaultNamespace: mynamespace
Expected result
Fission should be installed and fission check
should return that everything is okay.
Actual result
As shown above, the deployments are OK but fission check
fails.
loggerz
Metadata
Metadata
Assignees
Labels
No labels