ericyau82 comments

Results 4 comments of


                                            ericyau82

the service cannot be started when using in k8s pod and response "find: The environment is too large for exec()."

yup, many environment variables is set by our deployment script before (around 40 up are set) 00|

the service cannot be started when using in k8s pod and response "find: The environment is too large for exec()."

thx for your reply not really, actually those variable are set by the deployer(our team use gitlab to trigger a common deployer for deploying the project. And, i can just...

the service cannot be started when using in k8s pod and response "find: The environment is too large for exec()."

btw, finding most of the environment variables are come from the Kubernetes control plane services now (glowing up to over 4000 as our testing projects are using the same Kubernetes...

the service cannot be started when using in k8s pod and response "find: The environment is too large for exec()."

yup, might able to seperate the namespace, but needing to check with infra. teammates for the feasibility (don't know if much effort for changing their monitoring tool settings if seperating...