Skip to content

📗 Hardened docker file - great article to follow and learn from 🗞 #27

@goldbergyoni

Description

@goldbergyoni

🎯 Goal: - Allow building a hardened docker image out of this code so it can be deployed to Docker based productions (e.g., Kubernetes)

🤔 Things to consider:

  • It should be secured (e.g., avoid leaking secrets)
  • Support development mode (i.e., debug image locally)
  • Reasonably sized
  • Receive signals from OS
  • Conform to any other known best practice. @lirantal published a great checklist to follow!. I already wrote an article on this matter, I find Liran's version to be better:)
  • Should be part of the example Microservice and not the repo root
  • Test it. How? It's interesting to read and hunt techniques. At the basic level, the generated image should be inspected with tools like dive, should be executed manually and ensure that signals are received and more. Can we write automated tests for this? Maybe an option to consider

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or requestneeded-nowThings we need to finalize a beta

    Type

    No type

    Projects

    Status

    No status

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions