-
Notifications
You must be signed in to change notification settings - Fork 36
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
* Create FAQ.md * Update FAQ.md
- Loading branch information
Showing
1 changed file
with
12 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,12 @@ | ||
1. "I deleted the a namespace but it is stuck in terminating because the razee components can't be deleted." | ||
- see next | ||
1. "I can't delete a razee resource" | ||
- `kubectl patch <RemoteResource> <my-rr> --type='merge' -p '{"metadata":{"finalizers":null}}'` | ||
- If you are trying to clean up a cluster and you delete the razee controllers before cleaning up the custom resources, | ||
you are removing the code necessary to clean up your resources. We use `Finalizers` to manage resource lifecycle; if | ||
you delete the controllers before deleting the resource, our code is no longer running to remove the finalizer. | ||
- ie. You have the deployment `remoteresource-controller` running in the razee namespace, then you create custom resource | ||
RemoteResource `my-rr` in the razee namespace, then you delete the razee namespace. Kubernetes will delete all | ||
resources, it deletes the deployments first (like remoteresource-controller). Then it tries to delete `my-rr`; it | ||
gets stuck in terminating because the `remoteresource-controller` no longer exists to remove the finalizer from | ||
`my-rr`. Which in effect means the razee namespace gets stuck in terminating. |