Source: dzone.com
Introduction to Kubernetes Security: Container SecurityCategory: Database, Data, Kubernetes, Ubuntu, Docker, nginx, yaml
Join the DZone community and get the full member experience. Focusing on Kubernetes security, we have to go through container security and their runtimes.
But you have to admit that it is pretty complex and not very user-friendly.
In the end, even though the process itself is a little bit complicated, you can very easily push images to the Docker repository and be sure that it is always the image you intended to run.
The easiest way is to use the built-in mechanism in the Kubernetes secrets: Or you may create a secret by providing a YAML file with the base64 encoded docker config.json: Secret.yml (please note the type has to be kubernetes.io/dockerconfigjson and the data should be placed under .dockerconfigjson): Adding the above secret, you have to keep in mind that it works only in the specified namespace, and anyone in that namespace may be able to read that.
But you have to admit that it is pretty complex and not very user-friendly.
In the end, even though the process itself is a little bit complicated, you can very easily push images to the Docker repository and be sure that it is always the image you intended to run.
The easiest way is to use the built-in mechanism in the Kubernetes secrets: Or you may create a secret by providing a YAML file with the base64 encoded docker config.json: Secret.yml (please note the type has to be kubernetes.io/dockerconfigjson and the data should be placed under .dockerconfigjson): Adding the above secret, you have to keep in mind that it works only in the specified namespace, and anyone in that namespace may be able to read that.
Related Articles
Community Partners
DevOps Careers