Updated helm install example to use proper security defaults

[Xartos]

⚠️ IMPORTANT ⚠️: This is a public repository. Make sure to not disclose:

• personal data beyond what is necessary for interacting with this Pull Request;
• business confidential information, such as customer names.

Quality gates:

• I'm aware of the Contributor Guide and did my best to follow the guidelines.
• I'm aware of the Glossary and did my best to use those terms.

When installing the demo application according to this section the deployment will result in a warning about it not following the restricted PSS.

$ helm upgrade --install ...
.
.
.
W1107 13:24:08.331340  347415 warnings.go:70] would violate PodSecurity "restricted:latest": 
  allowPrivilegeEscalation != false (container "welkin-user-demo" must set securityContext.allowPrivilegeEscalation=false), 
  unrestricted capabilities (container "welkin-user-demo" must set securityContext.capabilities.drop=["ALL"]), 
  runAsNonRoot != true (pod or container "welkin-user-demo" must set securityContext.runAsNonRoot=true), 
  seccompProfile (pod or container "welkin-user-demo" must set securityContext.seccompProfile.type to "RuntimeDefault" or "Localhost")
.
.
.

This would solve that issue

[AlbinB97]

nice catch 👍

[cristiklein]

Please make these changes part of the user-demo Helm Chart. For the sake of "GitOps-ness", I'd like the Helm command to only include stuff which is not pre-determined.

[Xartos]

Please make these changes part of the user-demo Helm Chart. For the sake of "GitOps-ness", I'd like the Helm command to only include stuff which is not pre-determined.

Right, yea I thought about that in the beginning, but seeing that it's not set at all by default I thought that was intentional. But I'll change it 👍

[cristiklein]

Yup, the "would violate PodSecurity" warning is gone. Thank you!