Skip to content

Refactoring of the stats UI for use in Kubernetes/OpenShift - #632

Open
fboule wants to merge 7 commits into
monarc-project:masterfrom
fboule:stats
Open

fboule wants to merge 7 commits into
monarc-project:masterfrom
fboule:stats

Conversation

@fboule

@fboule fboule commented Oct 12, 2026

Copy link
Copy Markdown

Summary of changes

  • feat: add readme file with quick startup instructions
  • feat: add deployment scripts templates for Monarc stats on OpenShift/Kubernetes
  • refactor: initial import of Monarc front-office statistics for OpenShift

Description

For use with OpenShift or Kubernetes, the images must follow some rules for compatiblity purpose. The build must be reproducible, hence fixed package versions should be used (the base image packages should not be updated for instance). Besides, additional packages must be installed at build time and not at runtime, therefore the database initialization and the new packages installation have been separated.

The main changes are:

  • The use of the official Python 3.12 image based on Debian Bookworm slim
  • The scripts have been split, to only keep the database initialization in the entrypoint and the packages installation in the Dockerfile
  • The Python scripts are part of the build package (configuration, database creation, health monitoring, ...)
  • Other runtime parameters as secrets and DB host name are read from the environment variables.

For use with OpenShift or Kubernetes, the images must follow some rules
for compatiblity purpose. The build must be reproducible, hence fixed
package versions should be used (the base image packages should not be
updated for instance). Besides, additional packages must be installed at
build time and not at runtime, therefore the database initialization and
the new packages installation have been separated.

The main changes are:
- The use of the Debian Bookworm base base image.
- The scripts have been split, to only keep the database initialization
  in the entrypoint and the packages installation in the Dockerfile
- The configuration files such as SMTP server is parametrized at build
  time, but can be overwritten by configmap at runtime.
- Other runtime parameters as secrets and DB host name are read from the
  environment variables.
The base mariadb 10.11 image is rebuilt to startup with default
arguments and is embedded with the Monarc database initialization
scripts.
For use with OpenShift or Kubernetes, the images must follow some rules
for compatiblity purpose. The build must be reproducible, hence fixed
package versions should be used (the base image packages should not be
updated for instance). Besides, additional packages must be installed at
build time and not at runtime, therefore the database initialization and
the new packages installation have been separated.

The main changes are:
- The use of the official Python 3.12 image based on Debian Bookworm
  slim
- The scripts have been split, to only keep the database initialization
  in the entrypoint and the packages installation in the Dockerfile
- The Python scripts are part of the build package (configuration,
  database creation, health monitoring, ...)
- Other runtime parameters as secrets and DB host name are read from the
  environment variables.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants