Choose a use case & identify prerequisites

In Kubiya, there are limitless possible ways to use your AI Teammates. Kubiya helps you get started by offering out-of-the-box use cases and functionalities, but it's also possible to extend your AI Teammates with custom functionalities and to create custom use cases.

Regardless of whether you choose to set up an out-of-the-box use case or a custom one, it will have certain prerequisites, which include Kubiya resources that you need to set up and in some cases, ones you need to set up in 3rd-party platforms (e.g. a webhook that you need to configure in GitHub). The prequisites for a use case vary depending on the use case.

In this page, you'll learn:

1. The concepts of Tools and Tasks in Kubiya

2. Some of the common use cases for Kubiya AI Teammates

3. How to identify the prerequisites you'll need for your use case

Tools and Tasks: 2 Key Concepts in Kubiya

Kubiya offers both flexibility and extensibility, to meet you and your team's needs and preferences. To explain how, let's start with some context.

In Kubiya, the basic unit of Teammate functionality is called a tool. Functionally speaking, a tool is an atomic action or set of actions that an AI Teammate can perform. From a technical standpoint, a tool is a stateless service written in Kubiya's schema that performs an operation in a given platform.

Examples of tools:

• Create a Lambda function tool

• Get the status of EC2 instances tool

• Search Jira issues tool

• Manage Kubernetes pods tool

You can connect tools to your Kubiya Teammates to equip them with actions you want them to perform. Be aware that in order to perform those actions there are other resources that need to be created & configured beforehand – soon we'll review how to know which resources your Teammate needs in order to perform its actions. But before that, an important point: Kubiya Teammates are designed to solve painful operational problems in your organization, and while tools are powerful, they should be stitched together and paired with additional resources in order to give your organization even more powerful solutions.

While tools give you limitless freedom to build any use case you can imagine, the process of setting up that use case (and managing it) is manual and may be better suited for advanced users more intimately familiar with Kubiya.

Enter tasks. A task is a simplified way to set up a complete use case for your Kubiya Teammates. In addition to tools, a task includes all of the resources and dependencies for that use case. It uses an IaC-oriented approach to get your solution up and running even faster.

Common Use Cases for Kubiya Teammates

You might be wondering about the situations in which Kubiya Teammates can help you and your organization. Here are a few examples:

• Solving Ticket Queues: Have an AI Teammate take charge of your Jira queue - reviewing, resolving, updating and nudging. Consider it Done.

• JIT Cloud Permissions: Access when needed, secured when not. AI-driven JIT Permissions ensure resources are available only when required, seamlessly within your workflow, and without the hassle.

• Infrastructure Provisioning: Automate resource deployment with AI-driven JIT access, budget enforcement, and TTL management, ensuring efficient provisioning aligned with your best practices.

• Q&A Help Desk: Boost your help desk with AI-powered support that leverages your knowledge sources, processes, and tools to manage inquiries, resolve issues, and escalate complex cases – accelerating responses and freeing your team.

• Incident Response: Reimagine incident response with AI-Teammates. Quickly detect, triage, and resolve issues in real time, while closing communication loops to ensure your operations stay on track.

• Budget Enforcement: Maximize ROI with Teammate-powered budget enforcement. Manage spending in real time, eliminate idle resources, and streamline just-in-time access and approval flows.

Here are some use cases Kubiya offers out-of-the-box:

1. Allow JIT AWS IAM Permissions From Slack

2. Automatically Solve Jira Issues

3. Put Your Kubernetes Cluster On Autopilot

4. Allow Dynamic Infrastructure Creation From Slack Requests

How to Identify Prerequisites for Your Use Case

If setting up use case via tasks...

1. Go to Teammates tab in the top-bar menu, then go to Tasks in the left-side menu.

2. Click the Delegate Task button in the top-right corner.

3. Browse the list of tasks to see various pre-made use cases for Kubiya Teammates. Once you've identified the use case you want to set up, select it and click Continue.

4. In this screen, you see the input parameters required for the task you selected. Some of these are Kubiya resources and others are not – for our current purposes, we're only interested in learning which Kubiya resources are required. To do so, simply look for the input parameters that are dropdown selection menus. This is the shortcut to know which resources are Kubiya resources you need to set up.

   

   Once you've taken note of which resources, go ahead and set them up.

If setting up use case manually...

1. Runner – A Kubiya runner enables you to run Kubiya Teammates and all of their dependencies within your Kubernetes cluster. Regardless of your use case, you need a runner. Learn more

2. Integrations – Depending on the tools themselves, you will need to set up integrations so that your AI Teammate can access the platforms in which your Teammate is meant to perform operations.

3. Secrets – In addition to integrations, you might need to add secrets for your AI Teammate to use. For example, API keys for platforms you're integrated with or authentication tokens for platforms for which Kubiya doesn't have a native integration.

4. Knowledge – Any piece(s) of organizational knowledge that your AI Teammate needs in order to perform its responsibilities (if any). For example, the answers to questions developers might ask.

5. Users – People from your organization (e.g. could be needed for granting approvals)

6. Groups – Groups of Kubiya users from your organization