Kubernetes Crew

Put Your Kubernetes Cluster On Autopilot

Whether you're an expert Kubernetes operator or a newcomer, Kubernetes Crew can help you.

Speed up MTTR

Work smarter, not harder. Detect, understand, and resolve Kubernetes issues before they start costing your org.

24/7 Kubernetes reliability

Rest easy knowing you always have someone manning the Kubernetes helm.

Optimize Kubernetes Operations

Maximize resource efficiency, minimize costs, and automate routine tasks—all with precision.

Rapid time-to-automation

Get your AI Teammates up and running in minutes.

Want to get started?

Prerequisites

• A Kubernetes cluster

• A Kubiya runner (must be a local runner)

• Grant your Kubiya runner with access to your namespaces

• A Slack integration (the Kubiya Slack app)

• A Slack channel in which Kubiya Slack app is added

Set up the Kubernetes Crew use case

1. Go to the New Use Cases page
2. Select Kubernetes Crew and click Continue

   
3. Follow the on-screen instructions

   1. If you haven't created a runner yet, no problem. In the Select Runner drop-down, choose Create a Runner and follow the on-screen instructions.

   
4. Click Save and Continue. Behind the scenes this is running Terraform Plan.

   
5. If the plan is successful, you'll be brought to a screen showing a summary of the resources that will be created. To finish setup, click Delegate. This will run a Terraform Apply.

   
6. Refresh the screen and check that the use case's status is Active. If so, then the Terraform Apply was successful and you are ready to use your use case.

For a full breakdown of setting it up, see our guide on setting up pre-built use cases.

Permissions & Access

By default, Kubiya local runners have access to the kubiya namespace only. For this use case, your local runner will need access to your cluster's other namespaces.

Here's a guide on how to do so.

Make sure to grant your Kubiya runner access to your namespaces. Otherwise, the Kubernetes Crew will not have access.

How to use the Kubernetes Crew

There are two ways to use the Kubernetes Crew:

1. Webhooks

2. Proactively with requests

Webhooks

By default, the Kubernetes Crew setup contains webhooks that detect events you should know about. Whenever one of those events occur, the Kubernetes Crew will automatically look into it and update you in the Slack channel you designated during configuration.

When you receive a webhook alert, be sure to click into the thread to see the full details, ask follow up questions, and request actions.

Proactive Requests

At any time, you can also go to the Kubi Jr. app in Slack and send a message asking the Kubernetes Crew questions or to perform any Kubernetes operations.

For example, you can ask questions like:

1. Which pods are consuming the most CPU and memory in the last hour?

2. Are there any pods running with privileged containers?

3. Can you help me to understand traffic routing to pods in kubiya namespace?

4. Check the services defined in the kubiya namespace to see which pods they route to.

5. Can you validate all the CA certs within this cluster and let me know the expiration date?

6. Can you analysis the reason of "Crashloopback" pod on default namespace.

7. Can you send me the list of node names having events?

8. Can you enable debug container for pod/agent-manager-5b85f7f6d8-n92sc

9. Can you send me the list of all the pods having more than 5 restarts in all namespaces.

10. Can you get me the list of pods where resource is not defined.

11. Can you get me the list of incorrect configurations in this k8s clusters.

Congrats, you're ready to go! Now, go get to know your new teammates for Kubernetes operations 😃