karmada-io
/
karmada
mirror of https://github.com/karmada-io/karmada.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Modify the wrong noun for docs 

Signed-off-by: chen zechun <zechun.chen@daocloud.io>
This commit is contained in:
chen zechun 2022-10-07 23:06:31 +08:00
parent 75a0305a8c
commit e8cad61b06
2 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
docs/keps/cleanup-propagated-resources.md
View File

@ -32,7 +32,7 @@ This document proposes a mechanism to specify that a member cluster resource sho
## Motivation
When a cluster is unjoined, karmada should provide a mechanism to cleanup the resources propagated by karmada. Currently, when unjoin a cluster, `Karamada` first try to remove propagated resource, and will skip remove if the cluster not ready.
When a cluster is unjoined, karmada should provide a mechanism to cleanup the resources propagated by karmada. Currently, when unjoin a cluster, `Karmada` first try to remove propagated resource, and will skip remove if the cluster not ready.
### Goals
@ -71,11 +71,11 @@ By default, `RemoveStrategy` will be `needless` on all cluster. A user must exp
In kubefed's propose, the author suggest add a `BestEffort` strategy, reviewers say we need a certain value, so we should not use it too. `Karamada` use the `BestEffort` strategy, currently.
In kubefed's propose, the author suggest add a `BestEffort` strategy, reviewers say we need a certain value, so we should not use it too. `Karmada` use the `BestEffort` strategy, currently.
#### Needless Strategy
Not need cleanup propagated resources when unjoining cluster. `Karamada` should use this strategy as default value, condsider the business risk.
Not need cleanup propagated resources when unjoining cluster. `Karmada` should use this strategy as default value, condsider the business risk.
#### Required Strategy

4
docs/proposals/caching/README.md
View File

@ -49,9 +49,9 @@ Goals:
#### New Search APIGroup
We propose a new commponent named `karmada-search`, it provides a new api group called `search.karmada.io`, the reason why select the `search` word is because it's more to [OpenSearch](https://opensearch.org) which is a community-driven, Apache 2.0-licensed open source search and analytics suite.
We propose a new component named `karmada-search`, it provides a new api group called `search.karmada.io`, the reason why select the `search` word is because it's more to [OpenSearch](https://opensearch.org) which is a community-driven, Apache 2.0-licensed open source search and analytics suite.
The `karmada-search` component currently supports two types of backend stores, namely `cache` and `opensearch`. It uses the `cache` type as the default backend store of the caching layer for Karamda.
The `karmada-search` component currently supports two types of backend stores, namely `cache` and `opensearch`. It uses the `cache` type as the default backend store of the caching layer for Karmada.
We introduce a new resource type called `ResourceRegistry` in `search.karmada.io` group, it requires end users to manually specify the clusters and resources that need to be cached