Skip to content
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

Containerization of Kitodo Docker / Kubernetes #6394

Open
marinhio75 opened this issue Feb 3, 2025 · 1 comment
Open

Containerization of Kitodo Docker / Kubernetes #6394

marinhio75 opened this issue Feb 3, 2025 · 1 comment
Labels
development fund 2025 A candidate for the Kitodo e.V. development fund.

Comments

@marinhio75
Copy link


name: Task for the development fund
about: A working package which may be sponsored by the Kitodo e.V. development fund.
labels: development fund 2025
assignees: ''


Description

Why should Kitodo be containerized? Containerizing Kitodo enhances flexibility, scalability, and maintenance by ensuring a consistent environment, simplifying deployments, enabling dynamic scaling, and facilitating seamless updates, especially in distributed or cloud-based environments.

Expected Benefits of this Development

Containerizing Kitodo offers numerous advantages in terms of flexibility, scalability, and maintenance. By using Docker or Kubernetes, Kitodo and all its dependencies can run in isolated containers, ensuring a consistent environment across different systems. This minimizes compatibility issues between operating systems and significantly simplifies deployments.

Additionally, containerization allows for easy scaling, as instances can be dynamically started or stopped based on demand. Updates and maintenance can be performed seamlessly by replacing individual containers without downtime. Especially in distributed or cloud-based environments, this approach simplifies operations and enables integration into modern DevOps workflows.

Estimated Costs and Complexity

Please try to estimate the costs and / or the complexity of the development.

high ~ more than 10 working days

Too much outdated software would have to be loaded into the container, everything that is not part of the package e.g. Tomcat 9, Java 11 etc.

@marinhio75 marinhio75 added the development fund 2025 A candidate for the Kitodo e.V. development fund. label Feb 3, 2025
@BartChris
Copy link
Collaborator

BartChris commented Feb 3, 2025

Sounds interesting, I would like to ask: Is this really related to the development of the Software or is it more related to deployment/infrastructure? What would be the expected outcome? Docker configuration files and images? Kubernetes configuration files? In order to be useful those have to be updated when the underlying software changes. So that would be a continuous tasks.
We had a similar issue in the past: #4313

With the old issue in mind: Are we striving for something which is mostly used for development purposes or for production purposes?
Edit: An evaluation from what is missing from existing images to achieve the respective goals would be interesting: https://github.com/slub/kitodo-production-docker/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
development fund 2025 A candidate for the Kitodo e.V. development fund.
Projects
None yet
Development

No branches or pull requests

2 participants