Issue with k8s.io/docs/tutorials/stateful-application/zookeeper/

[singhania]

This is a Bug Report

Problem:
Solution on zookeeper on kubernetes page does not have the latest version of zookeeper.
Proposed Solution:
It will be helpful if this zookeeper deployment can use new docker with latest zookeeper version.

Page to Update:
https://kubernetes.io/docs/tutorials/stateful-application/zookeeper/

Latest

[sftim]

/kind cleanup
/priority backlog

[fejta-bot]

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]

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

[fejta-bot]

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

[k8s-ci-robot]

@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.

[r-joyce]

Is there any plans to still do this? The image used in the article is about 3 years old now. It's honestly a well written example in my opinion, but sucks that once it's completed to realize how old of a version it is. Also doesn't look like there's a newer image in that repository from what I can tell.

There is a more up to date version on Docker Hub which can be found here, but that is also a completely different image and requires a complete rewrite. Ideally a newer image should just be pushed, but I don't know who's in charge of that.

---

Edit: Link to the container registry

[sftim]

/reopen

We should still do this.
/remove-lifecycle rotten

[sftim]

/triage accepted

[k8s-ci-robot]

@sftim: Reopened this issue.

In response to this:

/reopen

We should still do this.
/remove-lifecycle rotten

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.

[fejta-bot]

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-contributor-experience at kubernetes/community.
/lifecycle stale

[aravindputrevu]

I was routed to here from #28837 by @sftim , I wrote a tutorial on a stateful app Elasticsearch.

It'd be great to have some stateful app tutorials on the k8s.io website as it is visited by many devs. Moreover, these are general-purpose datastores that could help many to get started with.

[k8s-triage-robot]

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:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[sftim]

/remove-lifecycle rotten

[sftim]

/lifecycle frozen

[k8s-triage-robot]

This issue has not been updated in over 1 year, and should be re-triaged.

You can:

• Confirm that this issue is still relevant with /triage accepted (org members only)
• Close this issue with /close

For more details on the triage process, see https://www.kubernetes.dev/docs/guide/issue-triage/

/remove-triage accepted

[tengqm]

/triage accepted

[tengqm]

Looks like this image was built 6 years ago and never updated.

[tengqm]

Check: https://github.com/kow3ns/kubernetes-zookeeper/blob/master/docker/Dockerfile

[Gauravpadam]

Looks like this issue is still relevant, Can I work on it?

[tengqm]

@Gauravpadam Sure you can work on it. Anyone can volunteer to contribute. Please bear in mind that we will need a working example, end to end. 3.4.10 is not too old a release for zookeeper. There is 3.9.0 on dockerhub, for example, but it doesn't mean everybody should use the latest version.
When fixing this issue, please get your hands dirty by setting up this cluster environment. There may be some tricks along the way. I heard that someone spent 2 weeks to get this up and running. Be well prepared, ;).

[Gauravpadam]

Thanks for the heads up @tengqm! I'd like to try and help with this issue, Will start working on it

[bianjp]

Thanks for the heads up @tengqm! I'd like to try and help with this issue, Will start working on it

What approach would you take? Upgrading https://github.com/kow3ns/kubernetes-zookeeper/ or rewrite the tutorial to use https://hub.docker.com/_/zookeeper? It seems that kow3ns never responds to any issue or pull request.

[sftim]

/remove-lifecycle frozen

IMO: fixes are welcome, but if this rots and gets closed, that's a sign that it wasn't important to people.

[bianjp]

I have made a pull request to the official zookeeper image to add custom init scripts support (31z4/zookeeper-docker#167). This will allow easier setup of myid for ZooKeeper cluster.

After that PR is accepted, I'd like to make a pull request to rewrite the tutorial to use latest official zookeeper image.