◆ Apache Cassandra

Run Cassandra on Kubernetes

This is real work, not a feature someone invented — it comes from real job ads and real questions people asked. Below are four ready AI prompts: get it done, make it easy for the next person to say yes to, work out the right move when you are stuck, and stop it coming back.

4prompts

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskDeploy a 3-node cluster for the 'recommendation_engine' in the 'dev' namespace on Kubernetes.…+
Deploy a 3-node cluster for the 'recommendation_engine' in the 'dev' namespace on Kubernetes. Ensure it's accessible to the development team.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
BImprove — make it easier to acceptBefore we move the 'customer_preferences' service to production on Kubernetes, review the…+
Before we move the 'customer_preferences' service to production on Kubernetes, review the current deployment configuration. Suggest improvements for persistent storage, resource limits, and auto-scaling policies to handle variable load and ensure data durability.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentA node running the 'product_inventory' service on Kubernetes just failed, and its pod isn't…+
The 'product_inventory' service running on Kubernetes just lost a node, and the pod isn't restarting automatically.
A node running the 'product_inventory' service on Kubernetes just failed, and its pod isn't restarting automatically. The product team is reporting stale inventory data. I'm not sure if it's a persistent volume claim issue, a Kubernetes scheduler problem, or a liveness probe misconfiguration. What's the immediate action to restore the pod and prevent future failures?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternEvery time we deploy a stateful application like this database on Kubernetes, I encounter…+
Managing stateful applications like this database on Kubernetes consistently leads to unexpected downtime and data inconsistencies.
Every time we deploy a stateful application like this database on Kubernetes, I encounter unexpected downtime or data consistency issues. It feels like I'm always reacting to problems with storage, networking, or pod lifecycle. What habit should I change to proactively design and manage these deployments for stability and reliability?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?

Questions people actually ask

honest answers, no sign-up

Every task here was seen in the real world. Someone doing the job named it, a real job ad asked for it, or a lot of people asked about it online.

If nothing real showed a task, it is not on the page. That is the whole rule.

They are the same job approached four ways, because what you need depends on where you are.

Get it done today. Make it easy for the next person to say yes to. Work out the right move when you are stuck. Learn the pattern so the job stops coming back.

For most of these jobs it can carry the heavy thinking - draft it, sort it, check it, rehearse it with you.

It cannot sit in your chair, take the blame when a number is wrong, or notice what nobody wrote down. Let it do the first 80%. Keep the last 20% that is truly yours.

No. Copy any prompt and paste it into the AI you already use. No account, no score, no wall in the way.

Any of them. The prompts describe the work rather than naming a product, so they are not tied to one assistant.

That is also why they keep working when you switch.

Change it freely. Every prompt is a starting line, not a rule.

Put in your real numbers, your real names and your real deadline. The more you make it yours, the better the answer comes back.

The tasks come from real job ads, published job data and the questions people ask in public forums.

The steps come from Apache Cassandra's own documentation, with practitioner sources for the traps the manual does not mention.

Push once. Ask it to sharpen the weakest part and to say what it assumed.

Most wrong answers come from a missing detail rather than a bad prompt - tell it the thing it could not know.