-
Notifications
You must be signed in to change notification settings - Fork 8.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Pod can't be started with sysctls custom settings #11962
Comments
This issue is currently awaiting triage. If Ingress contributors determines this is a relevant issue, they will accept it by applying the The Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
Does it work if you do not customize PodSecurityContext ? |
yes, it works perfectly. and if i edit deployment like
it stats fine:
|
At least for 2 sysctl arguments, the error message is unknown value ;
So this is not a bug but a misconfiguration of sysctl arguments. That kind of config is not in controller code as it just passes that from template to the Kubernetes API /remove-kind bug I think you should manually try those sysctl commands and see what fits |
/kind support |
but manually it works. workaround with additional modification after helm_release - it works without problem. ps. almost same problem is with keda addon. But i will report it later, as it is not so critical. |
There is a word about unsupported. Have you checked
|
@longwuyuan if i manually (or even with terraform) updating deployment after initial helm install - it starts to work as expected. About unsupported sysctl parameters i've read, but it is different. |
Then its a parsing problem. Have you played with the string. |
yes, i've tried next versions: nothing works. |
reduce upper port number to 60000 and try |
try
|
or maybe ;
I am not sure how to solve but I am sure this is not controller code as these keys & values are passed straight from the rendered template to the kubeapi-server .... you can enable debug and check the json payload |
i also tried outside of dynamic set:
and
gives:
and
gives |
Please come talk on Kubernetes Slack as there are not many resources here. The error message is proof that this is about parsing and var interpolation. I think that this works without terraform or ArgoCD type of tools so its not a problem with the controller. Some expert of these tools has to comment how to inject int instead of string etc etc. |
This is stale, but we won't close it automatically, just bare in mind the maintainers may be busy with other tasks and will reach your issue ASAP. If you have any question or request to prioritize this, please reach |
Hello,
What happened:
i'm getting next warning, which prevents to start nginx pod:
deploy was done via terraforms helm_release resource:
values are rendered like:
as i see, there is somehow additional chars passed there:
but if i write nex:
it fails on apply stage like:
Why? how it is possible to provide values, so it will work?
What you expected to happen:
Simple notation works without issues.
NGINX Ingress controller version (exec into the pod and run nginx-ingress-controller --version.):
installed with chart 4.10.4
The text was updated successfully, but these errors were encountered: