[keepalive-vip] Are there any plans to update the project?

Question

[keepalive-vip] Are there any plans to update the project?

ms4720 opened this issue 7 years ago · 7 comments

Hi,

Are there any plans to update the project? It does not work with k8s v1.10. If there are no plans to update could you mark it as abandoned to make things clearer.

Thanks

Answer 1 · 2018-06-08T19:34:50.000Z

@ms4720 after a couple of delayed PRs being merged I returned the development to my personal repo https://github.com/aledbf/kube-keepalived-vip

Answer 2 · 2018-06-09T04:15:11.000Z

OK thanks

…

On Sat, Jun 9, 2018, 3:35 AM Manuel Alejandro de Brito Fontes < ***@***.***> wrote: @ms4720 <https://github.com/ms4720> after a couple of delayed PRs being merged I returned the development to my personal repo https://github.com/aledbf/kube-keepalived-vip — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#2907 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AACRxbH_xVYyGDCaGeEYDL5aVTdQixXkks5t6tHogaJpZM4UUhsI> .

Answer 3 · 2018-07-02T06:47:51.000Z

Looks like this project is in a bad shape right now. One has to pick up bits and peaces from issues and pull requests, in order to get it up and running :(

Answer 4 · 2018-09-30T07:38:59.000Z

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

Answer 5 · 2018-10-30T08:27:07.000Z

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

Answer 6 · 2018-11-29T09:14:05.000Z

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

Answer 7 · 2018-11-29T09:14:13.000Z

@fejta-bot: Closing this issue.

In response to this:

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

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.