Closed duxing closed 1 year ago
@justinsb can you take a look when you have a chance?
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.
This bot triages issues and PRs according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/lifecycle rotten
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.
This bot triages issues and PRs according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle rotten
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.
This bot triages issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/reopen
/remove-lifecycle rotten
Please send feedback to sig-contributor-experience at kubernetes/community.
/close not-planned
@k8s-triage-robot: Closing this issue, marking it as "Not Planned".
A question for legacy
etcd-manager
:Not the most exciting topic but I can't find a better place for this question (
etcd-manager
has been archived in favor of this project)I'm stuck on this old version(
3.0.20190930
) ofetcd-manager
and noticed the same behavior on the latest version ofetcd-manager
too:the control store is reusing the path for backup (reference). is this desired?
the data from the control store are being used for both
controller
andbackupcontroller
. for example, control store contains data to see if a cluster is new (reference)with the current set up, if we specify a S3 bucket for backup, e.g.
s3://foobar
, the object hierarchy will look like this:where to me what would make more sense would be:
so that
backup
dir will contain backup data only, preventing accidentally deleting the control files