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

Osrdyne should clean and update kubernetes ressources #9369

Open
ElysaSrc opened this issue Oct 17, 2024 · 1 comment · May be fixed by #9382
Open

Osrdyne should clean and update kubernetes ressources #9369

ElysaSrc opened this issue Oct 17, 2024 · 1 comment · May be fixed by #9382
Assignees
Labels

Comments

@ElysaSrc
Copy link
Member

Currently, we can have the deployment that end up in inconsistent states, mainly related to upgrading issue not updating the core since it doesn't .

When starting up osrdyne should :

  • Cleanup the stale ScaledObjects if the deployment is not required
  • Upgrade the deployments charts

In order to retrigger a core deployment at boot properly, we should:

  • Select a random string in the Kubernetes Driver at boot
  • Set this string in a label of the deployment
  • When starting up, the deployment should be upgraded (triggering a reload of the containers)

(This mechanism is inspired from the rollme system that is sometimes used in charts)

@ElysaSrc ElysaSrc self-assigned this Oct 17, 2024
@flomonster
Copy link
Contributor

Is it necessary to clean and update k8s resources every time osrdyne starts? A more precise requirement would be that when osrdyne starts up, it should clean up core pods running on a different version.

Instead of using a random string generated at startup, it could use the OSRD_DESCRIBE environment variable. Note that this doesn't work for the dev environment.

@ElysaSrc ElysaSrc linked a pull request Oct 18, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants