Re: [kubernetes/kubernetes] Need fencing in HA recovery process (#12338)

4 views
Skip to first unread message

Michail Kargakis

unread,
Jun 9, 2017, 3:53:31 PM6/9/17
to kubernetes/kubernetes, k8s-mirror-storage-misc, Team mention

@kubernetes/sig-storage-misc


You are receiving this because you are on a team that was mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

fejta-bot

unread,
Dec 26, 2017, 5:24:24 PM12/26/17
to kubernetes/kubernetes, k8s-mirror-storage-misc, Team mention

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

Prevent issues from auto-closing with an /lifecycle frozen comment.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or @fejta.
/lifecycle stale

fejta-bot

unread,
Jan 25, 2018, 5:33:21 PM1/25/18
to kubernetes/kubernetes, k8s-mirror-storage-misc, Team mention

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten
/remove-lifecycle stale

kfox1111

unread,
Jan 26, 2018, 3:07:49 PM1/26/18
to kubernetes/kubernetes, k8s-mirror-storage-misc, Team mention

/remove-lifecycle rotten

fejta-bot

unread,
Apr 26, 2018, 4:42:47 PM4/26/18
to kubernetes/kubernetes, k8s-mirror-storage-misc, Team mention

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.

/lifecycle stale

fejta-bot

unread,
May 26, 2018, 5:28:56 PM5/26/18
to kubernetes/kubernetes, k8s-mirror-storage-misc, Team mention

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.

/lifecycle rotten
/remove-lifecycle stale

k8s-ci-robot

unread,
Jun 25, 2018, 6:16:06 PM6/25/18
to kubernetes/kubernetes, k8s-mirror-storage-misc, Team mention

Closed #12338.

fejta-bot

unread,
Jun 25, 2018, 6:16:10 PM6/25/18
to kubernetes/kubernetes, k8s-mirror-storage-misc, Team mention

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.


Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

kvaps

unread,
Sep 20, 2018, 4:47:59 AM9/20/18
to kubernetes/kubernetes, k8s-mirror-storage-misc, Team mention

Hi, I wrote and currently testing my own implementation of fencing. It uses classic fence-agents from clusterlabs, but it can use something else, if you interested in it, please take a look:
https://github.com/kvaps/kube-fencing

Reply all
Reply to author
Forward
0 new messages