Untab documentation
  • Overview
  • Architecture
  • Compatibility
  • Collected information
  • Authentication
  • Setup
    • First steps
    • Installing using the basic manifest
    • Installing using Helm
    • Checking agent status
    • Configuring access to cloud providers (optional)
    • Setting up access on AWS
    • Setting up access on Google Cloud Platform
  • Management
    • Managing user access
    • Troubleshooting
Powered by GitBook
On this page

Was this helpful?

  1. Setup

Installing using the basic manifest

PreviousFirst stepsNextInstalling using Helm

Last updated 5 years ago

Was this helpful?

For the most common scenarios, Untab provides a simple manifest for installing the agent in a cluster. The manifest can be used in the AWS or Google clouds and is configured with the following default settings:

  • A namespace called untab will be created to contain all agent resources

  • No egress proxy will be used

  • Node exporter will be deployed on port 9111 on each machine

To download the manifest, navigate to the "Status" page, then click the "Add cluster" button in the top right corner of the page.

Click on the "Manifest" button to download the Kubernetes YAML manifest, then apply it:

kubectl apply -f untab-manifest.yml

Note that the provided a YAML manifest file contains all of the the necessary information, including authentication tokens. If needed, you can examine and modify the manifest to ensure that it complies with any necessary policies.

The next step is to validate that the agent is working correctly.

Enter the cluster ID (use only letters, numbers, and "." and "-" symbols), then select which cloud provider you are using. Untab can also run on-prem or in other cloud providers - please to set this up.

contact us
Checking agent status