forked from argoproj/argo-cd
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Issue argoproj#1167 - Document orphaned resources, update proj CLI
- Loading branch information
Alexander Matyushentsev
authored and
Alexander Matyushentsev
committed
Aug 22, 2019
1 parent
7ac9e6f
commit 88453cf
Showing
5 changed files
with
67 additions
and
10 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
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
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,19 @@ | ||
# Orphaned Resources Monitoring | ||
|
||
Orphaned Kubernetes resource is a top-level namespaced resource which does not belong to any Argo CD Application. The Orphaned Resources Monitoring feature allows detecting | ||
orphaned resources, generate a warning and inspect/remove resources using Argo CD UI. | ||
|
||
The Orphaned Resources monitoring is enabled in [Project](projects.md) settings. Once the feature is enabled each project application which target namespace has orphaned resource | ||
will get a warning condition. The orphaned resources can be located using the application details page: | ||
|
||
![orphaned resources](../assets/orphaned-resources.png) | ||
|
||
Before enabling feature you might consider disabling warning. In this case application users are going to see orphaned resources in the UI but application is won't get a warning condition. | ||
|
||
## Exceptions | ||
|
||
Not every resource in the Kuberenetes cluster is controlled by the end user. Following resources are never considered as orphaned: | ||
|
||
* Namespaced resources blacklisted in the project. Usually, such resources are managed by cluster administrators and not supposed to be modified by namespace user. | ||
* `ServiceAccount` with name `default` ( and corresponding auto-generated `ServiceAccountToken` ). | ||
* `Service` with name `kubernetes` in the `default` namespace. |
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
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