◆ Apache Airflow

Resolve Kubernetes deployment errors

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 taskWe need to fix the Kubernetes deployment errors for the new customer data pipeline. Find the…+
We need to fix the Kubernetes deployment errors for the new customer data pipeline. Find the logs for the `customer-data-processor` pod on the staging cluster and restart the deployment once the issues are resolved.
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 push the `customer-data-processor` deployment to production, let's make sure it's…+
Before we push the `customer-data-processor` deployment to production, let's make sure it's resilient. Add a health check endpoint to the pod, increase the liveness probe timeout to 60 seconds, and ensure the deployment strategy allows for zero downtime updates.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentThe `customer-data-processor` pod keeps crashing immediately after deployment, and I'm getting…+
The `customer-data-processor` pod keeps crashing immediately after deployment, and I'm getting a 'CrashLoopBackOff' error in Kubernetes.
The `customer-data-processor` pod keeps crashing immediately after deployment, and I'm getting a 'CrashLoopBackOff' error. I've checked the image name and resource limits, but it's still failing. I'm worried it's a deeper configuration issue or a dependency I'm missing. What's the most likely cause here, and what's the first thing I should check that I might be overlooking?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI keep getting called in to fix Kubernetes deployment errors for new data pipelines that fail…+
I keep getting called in to fix Kubernetes deployment errors for new data pipelines that fail in staging.
I keep getting called in to fix Kubernetes deployment errors for new data pipelines that fail in staging, often due to subtle configuration issues or missing environment variables. I lose hours debugging these. What habit should I change in my deployment process to catch these issues earlier, before they hit staging and cause delays for the analytics team?
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 Airflow'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.