Open Mena2871 opened 3 years ago
Fission/Kubernetes version
$ fission --version client: fission/core: BuildDate: "2021-06-16T10:24:16Z" GitCommit: 6fbd4878be785ded8f14eb9f8b8bc747946a2b8f Version: 1.13.0 server: fission/core: BuildDate: "2021-06-16T09:47:41Z" GitCommit: 6fbd4878be785ded8f14eb9f8b8bc747946a2b8f Version: 1.13.0 $ kubectl version Client Version: version.Info{Major:"1", Minor:"18", GitVersion:"v1.18.2", GitCommit:"52c56ce7a8272c798dbc29846288d7cd9fbae032", GitTreeState:"clean", BuildDate:"2020-04-17T08:59:10Z", GoVersion:"go1.14.2", Compiler:"gc", Platform:"linux/amd64"} Server Version: version.Info{Major:"1", Minor:"17", GitVersion:"v1.17.5", GitCommit:"e0fccafd69541e3750d460ba0f9743b90336f24f", GitTreeState:"clean", BuildDate:"2020-04-16T11:35:47Z", GoVersion:"go1.13.9", Compiler:"gc", Platform:"linux/amd64"}
Kubernetes platform (e.g. Google Kubernetes Engine) AWS EC2 deployed cluster
Describe the bug Fission-workflows is throwing an error attempting to validate environment spec
To Reproduce
Deploy fission-workflows 0.6.0 using README.
helm install --wait -n fission-workflows fission-charts/fission-workflows --version 0.6.0.
Expected result fission-workflows installed on top of fission
Actual result helm install is throwing the error below:
Screenshots/Dump file
Error: unable to build kubernetes objects from release manifest: error validating "": error validating data: ValidationError(Environment.spec): unknown field "TerminationGracePeriodSeconds" in io.fission.v1.Environment.spec
Additional context Changing TerminationGracePeriod to terminationGracePeriod in charts/fission-workflows/templates/deployment.yaml fixed the issue
Fission/Kubernetes version
Kubernetes platform (e.g. Google Kubernetes Engine) AWS EC2 deployed cluster
Describe the bug Fission-workflows is throwing an error attempting to validate environment spec
To Reproduce
Deploy fission-workflows 0.6.0 using README.
Expected result fission-workflows installed on top of fission
Actual result helm install is throwing the error below:
Screenshots/Dump file
Additional context Changing TerminationGracePeriod to terminationGracePeriod in charts/fission-workflows/templates/deployment.yaml fixed the issue