Analisis of warnings reported by Kubelinter

[j-rivero]

I have been playing with kubelinter to detect issues related to the charts in this repo. I have implemented the github action to run the linter on charts on my fork. The linter has triggered more than 89 warning of different types. Trying to group them to discuss if they need attention or we can ignore them:

• Lack of memory / CPU requests and limits: https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/#requests-and-limits
• Containers running as root https://kubernetes.io/docs/tasks/configure-pod-container/security-context/
• Do not use latest on container images but tags
• Containers running without the read-only option for the filesystem
• Network space is being shared with the host

[j-rivero]

After a quick chat with @akash-roboticist some comments for the different categories:

• Lack of memory / CPU requests and limits: https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/#requests-and-limits

As a preliminary step, more information needs to be collected on how the different containers are consuming memory/CPU and what the RMF team would expect from them.

• Containers running as root https://kubernetes.io/docs/tasks/configure-pod-container/security-context/

This is a high priority that needs to be addressed.

• Do not use latest on container images but tags

Since the development is ongoing, we are going to keep using latest tags by now.

• Containers running without the read-only option for the filesystem

Good to look. dds config can be read only but database needs inspection.

• Network space is being shared with the host

Worth exploring the limitation.