You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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/
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.
The text was updated successfully, but these errors were encountered: