Remove duplication (#2898)
* Remove depplication Signed-off-by: mooncake <xcoder@tenxcloud.com> * Remove duplciate words Signed-off-by: mooncake <xcoder@tenxcloud.com> * Fix issue Signed-off-by: mooncake <xcoder@tenxcloud.com>
This commit is contained in:
Bily Zhang
k8s-ci-robot
parent
79748734e6
commit
d0d8d09f67
|
|
@ -348,7 +348,7 @@ to that LRS along with their current status and status change timestamp.
|
|||
+ [I6] If a cluster is removed from the federation then the situation
|
||||
is equal to multiple [E4]. It is assumed that if a connection with
|
||||
a cluster is lost completely then the cluster is removed from the
|
||||
the cluster list (or marked accordingly) so
|
||||
cluster list (or marked accordingly) so
|
||||
[[E6]](#heading=h.in6ove1c1s8f) and [[E7]](#heading=h.37bnbvwjxeda)
|
||||
don't need to be handled.
|
||||
|
||||
|
|
@ -383,7 +383,7 @@ To calculate the (re)scheduling moves for a given FRS:
|
|||
1. For each cluster FRSC calculates the number of replicas that are placed
|
||||
(not necessary up and running) in the cluster and the number of replicas that
|
||||
failed to be scheduled. Cluster capacity is the difference between the
|
||||
the placed and failed to be scheduled.
|
||||
placed and failed to be scheduled.
|
||||
|
||||
2. Order all clusters by their weight and hash of the name so that every time
|
||||
we process the same replica-set we process the clusters in the same order.
|
||||
|
|
|
|||
|
|
@ -61,7 +61,7 @@ making the assumption that your test can run a pod on every node in a
|
|||
cluster is not a safe assumption, as some other tests, running at the
|
||||
same time as yours, might have saturated one or more nodes in the
|
||||
cluster. Similarly, running a pod in the system namespace, and
|
||||
assuming that that will increase the count of pods in the system
|
||||
assuming that will increase the count of pods in the system
|
||||
namespace by one is not safe, as some other test might be creating or
|
||||
deleting pods in the system namespace at the same time as your test.
|
||||
If you do legitimately need to write a test like that, make sure to
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
This is an announcement for the 2017 Kubernetes Leadership Summit, which will occur on June 2nd, 2017 in San Jose, CA.
|
||||
This event will be similar to the [Kubernetes Developer's Summit](/events/2016/developer-summit-2016/Kubernetes_Dev_Summit.md) in November
|
||||
2016, but involving a smaller smaller audience comprised solely of leaders and influencers of the community. These leaders and
|
||||
2016, but involving a smaller audience comprised solely of leaders and influencers of the community. These leaders and
|
||||
influences include the SIG leads, release managers, and representatives from several companies, including (but not limited to)
|
||||
Google, Red Hat, CoreOS, WeaveWorks, Deis, and Mirantis.
|
||||
|
||||
|
|
|
|||
|
|
@ -138,7 +138,7 @@ or case-handling in `kubectl`.
|
|||
|
||||
In essence, a plugin binary must be able to run as a standalone process, completely independent of `kubectl`.
|
||||
|
||||
* When `kubectl` is executed with a subcommand _foo_ that does not exist exist in the command tree, it will attempt to look
|
||||
* When `kubectl` is executed with a subcommand _foo_ that does not exist in the command tree, it will attempt to look
|
||||
for a filename `kubectl-foo` (`kubectl-foo.exe` on Windows) in the user's `PATH` and execute it, relaying all arguments given
|
||||
as well as all environment variables to the plugin child-process.
|
||||
|
||||
|
|
|
|||
|
|
@ -150,7 +150,7 @@ The site would be forum.k8s.io, and would be linked to from the homepage and maj
|
|||
- [Discussion on the pros and cons of each](https://meta.discourse.org/t/discourse-vs-email-mailing-lists/54298)
|
||||
- We have enough churn and new Working Groups that we could pilot a few, opt-in for SIGs that want to try it?
|
||||
- A community forum is asynchronous, whereas chat is realtime.
|
||||
- This doesn't solve our Slack lock-in concerns, but can be a good first step in being more active in running our own community properties so that we can build out own own resources.
|
||||
- This doesn't solve our Slack lock-in concerns, but can be a good first step in being more active in running our own community properties so that we can build out own resources.
|
||||
- Ghost have [totally migrated to Discourse](https://twitter.com/johnonolan/status/980872508395188224?s=12) and shut down their Slack.
|
||||
- We should keep an eye on this and see what data we can gleam from this. Engage with Ghost community folks to see what lessons they've learned.
|
||||
- Not sure if getting rid of realtime chat entirely is a good idea either.
|
||||
|
|
|
|||
|
|
@ -519,7 +519,7 @@ appropriate end to end tests.
|
|||
reasons for using quotas is indeed to improve performance. If this
|
||||
is a problem in the field, merely turning off quotas (or selectively
|
||||
disabling project quotas) on the filesystem in question will avoid
|
||||
the problem. Against the possibility that that cannot be done
|
||||
the problem. Against the possibility that cannot be done
|
||||
(because project quotas are needed for other purposes), we should
|
||||
provide a way to disable use of quotas altogether via a feature
|
||||
gate.
|
||||
|
|
|
|||
|
|
@ -23,7 +23,7 @@ Familiarize yourself with the [community membership requirements doc](/community
|
|||
These topics will be covered during bi-weekly standups/workshops. The suggested activities will be covered in the mentee's normal day to day. Know something that should be added? Start a convo/add a PR - your comments are appreciated.
|
||||
|
||||
### Current Member Cohort Topics
|
||||
* Effective communication in our our ecosystem
|
||||
* Effective communication in our ecosystem
|
||||
* Kubernetes Governance 101 (what's a SIG?, OWNERS files, steering committee, etc.)
|
||||
* Identifying & understanding issue backlog and prioritization
|
||||
* Contributing to testing (how to run tests and create new ones)
|
||||
|
|
|
|||
|
|
@ -13,7 +13,7 @@ If you'd like to contribute, please read the [conventions](/contributors/devel/k
|
|||
### Add new commands / subcommands / flags
|
||||
* [Simplify support for multiple files](https://github.com/kubernetes/kubernetes/issues/24649)
|
||||
* Manifest that can specify multiple files / http(s) URLs
|
||||
* [Default manifest manifest](https://github.com/kubernetes/kubernetes/issues/3268) (ala Dockerfile or Makefile)
|
||||
* [Default manifest](https://github.com/kubernetes/kubernetes/issues/3268) (ala Dockerfile or Makefile)
|
||||
* Unpack archive (tgz, zip) and then invoke “-f” on that directory
|
||||
* URL shortening via default URL prefix
|
||||
* [Imperative `set` commands](https://github.com/kubernetes/kubernetes/issues/21648)
|
||||
|
|
|
|||
Loading…
Reference in New Issue