Stale container image in Example: Deploying Cassandra with a StatefulSet

dshebib commented 6 months ago

This is a Bug Report

Problem The image in https://kubernetes.io/docs/tutorials/stateful-application/cassandra/#using-a-statefulset-to-create-a-cassandra-ring is out-of-date, causing cqlsh (the core commandline tool for cassandra) to fail with an error about an invalid python interpreter. Though the Kubernetes statefulset works as intended and the cluster runs properly, this makes the example hard to explore for intedned functionality. It could be improved by having an up-to-date image so that basic commands can be run within the started pods.

Proposed solution Update the gcr.io/google-samples/cassandra:v13 image or use an up-to-date Dockerhub Cassandra image and update the readiness probe as needed.

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

Additional Information

NAME          READY   STATUS    RESTARTS   AGE
cassandra-0   1/1     Running   0          3m52s
cassandra-1   1/1     Running   0          3m18s
cassandra-2   1/1     Running   0          2m14s
dshebib@DESKTOP:~/playground$ kubectl exec -it cassandra-0 -- sh
# ls
bin   cassandra_data  etc   kubernetes-cassandra.jar  lib64  mnt  proc            root  run.sh  srv  tmp  var
boot  dev             home  lib                       media  opt  ready-probe.sh  run   sbin    sys  usr
# nodetool status
Datacenter: DC1-K8Demo
======================
Status=Up/Down
|/ State=Normal/Leaving/Joining/Moving
--  Address     Load       Tokens       Owns (effective)  Host ID                               Rack
UN  10.244.0.6  124.9 KiB  32           68.5%             209c746e-f576-4856-a0e2-f990dbcec860  Rack1-K8Demo
UN  10.244.0.7  108.89 KiB  32           69.8%             385395a9-532a-4262-9b94-c4d2cf5740bb  Rack1-K8Demo
UN  10.244.0.8  65.87 KiB  32           61.7%             50b1b4ed-e0ac-4b83-b865-cafd9716569f  Rack1-K8Demo

# cqlsh
No appropriate python interpreter found.

k8s-ci-robot commented 6 months ago

This issue is currently awaiting triage.

SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the triage/accepted label.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.

steve-hardman commented 6 months ago

the Kubernetes statefulset works as intended and the cluster runs properly,

It sounds more like an improvment that would need to made for this.

/remove-kind bug /kind feature

steve-hardman commented 6 months ago

/language en /sig docs

sftim commented 6 months ago

/retitle Stale container image in Example: Deploying Cassandra with a StatefulSet

Ayush9026 commented 6 months ago

/assign @Ayush9026

k8s-triage-robot commented 3 months ago

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues 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 as fresh with /remove-lifecycle stale
Close this issue with /close
Offer to help out with Issue Triage

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

/lifecycle stale

vaibhav2107 commented 3 months ago

@Ayush9026 Are you still working on this issue?

k8s-triage-robot commented 2 months ago

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues 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 as fresh with /remove-lifecycle rotten
Close this issue with /close
Offer to help out with Issue Triage

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

/lifecycle rotten

dshebib commented 2 months ago

/remove-lifecycle rotten

kubernetes / website

Stale container image in Example: Deploying Cassandra with a StatefulSet #45351