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

install --upgrade delete namespace at end of previous version install #198

Closed
n0rad opened this issue Jan 15, 2020 · 2 comments
Closed

install --upgrade delete namespace at end of previous version install #198

n0rad opened this issue Jan 15, 2020 · 2 comments
Labels

Comments

@n0rad
Copy link

n0rad commented Jan 15, 2020

Hi there,

I'm trying to use install --upgrade to validate that a chart is upgradable from one version to another.
At the end of the previous version installation, the namespace is deleted and a new one is created to install current version

I'm testing with CT latest container (2.4.0) against a private repository with changes on a branch.
from the logs changes are well detected :

Testing upgrades of chart 'maxscale => (version: "0.1.1", path: "maxscale")' relative to previous revision 'maxscale => (version: "0.1.0", path: "ct_previous_revision535151147/maxscale")'...

But at the end of the previous install :

...
Deleting release 'maxscale-2semyflfvv'...
>>> helm delete --purge maxscale-2semyflfvv
release "maxscale-2semyflfvv" deleted
Deleting namespace 'maxscale-2semyflfvv'...
>>> kubectl delete namespace maxscale-2semyflfvv --timeout 180s
namespace "maxscale-2semyflfvv" deleted
>>> kubectl get namespace maxscale-2semyflfvv
Namespace 'maxscale-2semyflfvv' terminated.
Testing upgrades of chart 'maxscale => (version: "0.1.1", path: "maxscale")' relative to previous revision 'maxscale => (version: "0.1.1", path: "maxscale")'...
>>> helm install maxscale --name maxscale-mgmh215ffh --namespace maxscale-mgmh215ffh --wait
...
Copy link

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.

@github-actions github-actions bot added the Stale label Nov 30, 2023
Copy link

github-actions bot commented Dec 5, 2023

This issue was closed because it has been stalled for 5 days with no activity.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Dec 5, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant