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

Marketplace: kwasm provisioning jobs/pods remain after helm delete #12

Open
vdice opened this issue Sep 3, 2024 · 0 comments
Open

Marketplace: kwasm provisioning jobs/pods remain after helm delete #12

vdice opened this issue Sep 3, 2024 · 0 comments

Comments

@vdice
Copy link
Collaborator

vdice commented Sep 3, 2024

This is a placeholder issue that actually isn't specific to the SpinKube Azure Marketplace chart but I wanted to document pending a potential fix upstream* (in the kwasm-operator, or in the future, runtime-class-manager project).

The kwasm/rcm provisioning job(s) and their corresponding pod(s) persist even after deleting the helm release for this chart. As a result, when the SpinKube Marketplace extension is uninstalled, the same behavior will be seen.

*A potential fix could be to allow configuration of a TTL for the provisioner job (eg spinkube/runtime-class-manager#199)

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

No branches or pull requests

1 participant