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.

Sign up for GitHub

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

Jump to bottom

Fix: correct user's responsiblity for cleanup during namespace switch #202

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Fix: correct user's responsiblity for cleanup during namespace switch #202

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion src/content/docs/upgrade-install-new-operator.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -99,7 +99,7 @@ We offer a feature that allows users to configure the namespace for their applic
There are two scenarios in which this feature can be utilized:

- Assigning a New Namespace: Users can set a new namespace using `DSCInitialization` instance before creating the `DataScienceCluster` instance.
- Switching to a New Namespace: Users have the option to switch to a new namespace after resources have already been established in the application's current namespace. It's important to note that in this scenario, only specific resources (such as deployments, configmaps, networkpolicies, roles, rolebindings, secrets etc) will be removed from the old application namespace during cleanup. For namespace-scoped CRD instances, users will be responsible to cleanup themselves.
- Switching to a New Namespace: Users have the option to switch to a new namespace after resources have already been established in the application's current namespace. It's important to note that in this scenario, users will be responsible to cleanup resources themselves (such as namespace-scoped CRD instances, deployments, configmaps, networkpolicies, roles, rolebindings, secrets etc) from the old application namespace.

### Upgrade from v2.0/v2.1 to v2.2 and forth release

Expand Down