KoalaOps currently supports GKE (Google Cloud) and EKS (AWS). We assume that your clusters (or at least one cluster) are already configured and operational. If you need help provisioning a new cluster, please contact us and we’ll be happy to assist. To use KoalaOps, you are required to connect every k8s cluster you intend to use.
KoalaOps pulls information from the cluster using our agent, configures your code (k8s manifests, CI/CD etc), and performs operations (via CLI or agent) according to the clusters configured for the organization and for each service.
Koala currently requires two extremely common tools to be installed in the cluster. Please make sure your cluster has them installed (or let us know if you need us to support alternatives). You can use Helm or direct kubectl installation.
cert-manager needs an “Issuer” to generate new certificates. You can install a basic configuration using Let’s Encrypt by applying the following to your cluster (replace the email address with your own):
Make sure you’re authenticated to your cloud provider’s cluster
The Koala Agent installation requires your to be authenticated to your cluster. See more details on how to do so in the Koala Agent Requirements section.
You will need the following information about the cluster:
Here is an example of how to extract those values from the GCP console:
You can register the cluster using either the Google Web App or the Koala CLI. Find the instructions for both options below.
Open the web app and on the left side menu click Clusters -> Connect. Fill in:
Click the ‘Register’ button.
Install the agent using helm
: copy the command that was generated after clicking on Register into your terminal:
You can always fetch this command in the future from the clusters list section.
Open the web app and on the left side menu click Clusters -> Connect. Fill in:
Click the ‘Register’ button.
Install the agent using helm
: copy the command that was generated after clicking on Register into your terminal:
You can always fetch this command in the future from the clusters list section.
koala cluster register cluster-name -p <project ID> -z <zone>
Then:
helm install
command pre-populated with the unique API key for the cluster, which will install the agent. If needed, you can customize the namespace in which the agent will run.You will need the following information about the cluster:
Here is an example of how to extract those values from the GCP console:
You can register the cluster using either the Google Web App or the Koala CLI. Find the instructions for both options below.
Open the web app and on the left side menu click Clusters -> Connect. Fill in:
Click the ‘Register’ button.
Install the agent using helm
: copy the command that was generated after clicking on Register into your terminal:
You can always fetch this command in the future from the clusters list section.
Open the web app and on the left side menu click Clusters -> Connect. Fill in:
Click the ‘Register’ button.
Install the agent using helm
: copy the command that was generated after clicking on Register into your terminal:
You can always fetch this command in the future from the clusters list section.
koala cluster register cluster-name -p <project ID> -z <zone>
Then:
helm install
command pre-populated with the unique API key for the cluster, which will install the agent. If needed, you can customize the namespace in which the agent will run.You will need the following information about the cluster:
Here is an example of how to extract those values from the AWS console:
Open the web app and on the left side menu click Clusters -> Connect. Fill in:
The organization field reflects your current Koala organization which can only be changed by using the dropdown on the top left part of the Koala console next to the Koala logoaws.
Click the ‘Register Cluster’ button.
Install the agent using helm
: copy the command that was generated after clicking on Register into your terminal:
You can always fetch this command in the future from the clusters list section.
Kubernetes Ingress is an API object that provides routing rules to manage access to services within a Kubernetes cluster. It acts as a single entry point for external traffic to your Kubernetes services, making it easier to manage and expose your applications to the world.
To enable ingress for your services in the cluster, you should configure the DNS for your domain to point to the cluster. This should be done in your DNS provider.
If a service is deployed in a single cluster, you can directly point the DNS to the cluster’s external IP address. You can see it in your cloud provider’s console, or in the cluster list in app.koalaops.com.
If you’re using a load balancer across clusters, we will soon add support for that, but for now you’ll need to continue to manage that manually. Please continue with the configuration as you would without KoalaOps.
KoalaOps currently supports GKE (Google Cloud) and EKS (AWS). We assume that your clusters (or at least one cluster) are already configured and operational. If you need help provisioning a new cluster, please contact us and we’ll be happy to assist. To use KoalaOps, you are required to connect every k8s cluster you intend to use.
KoalaOps pulls information from the cluster using our agent, configures your code (k8s manifests, CI/CD etc), and performs operations (via CLI or agent) according to the clusters configured for the organization and for each service.
Koala currently requires two extremely common tools to be installed in the cluster. Please make sure your cluster has them installed (or let us know if you need us to support alternatives). You can use Helm or direct kubectl installation.
cert-manager needs an “Issuer” to generate new certificates. You can install a basic configuration using Let’s Encrypt by applying the following to your cluster (replace the email address with your own):
Make sure you’re authenticated to your cloud provider’s cluster
The Koala Agent installation requires your to be authenticated to your cluster. See more details on how to do so in the Koala Agent Requirements section.
You will need the following information about the cluster:
Here is an example of how to extract those values from the GCP console:
You can register the cluster using either the Google Web App or the Koala CLI. Find the instructions for both options below.
Open the web app and on the left side menu click Clusters -> Connect. Fill in:
Click the ‘Register’ button.
Install the agent using helm
: copy the command that was generated after clicking on Register into your terminal:
You can always fetch this command in the future from the clusters list section.
Open the web app and on the left side menu click Clusters -> Connect. Fill in:
Click the ‘Register’ button.
Install the agent using helm
: copy the command that was generated after clicking on Register into your terminal:
You can always fetch this command in the future from the clusters list section.
koala cluster register cluster-name -p <project ID> -z <zone>
Then:
helm install
command pre-populated with the unique API key for the cluster, which will install the agent. If needed, you can customize the namespace in which the agent will run.You will need the following information about the cluster:
Here is an example of how to extract those values from the GCP console:
You can register the cluster using either the Google Web App or the Koala CLI. Find the instructions for both options below.
Open the web app and on the left side menu click Clusters -> Connect. Fill in:
Click the ‘Register’ button.
Install the agent using helm
: copy the command that was generated after clicking on Register into your terminal:
You can always fetch this command in the future from the clusters list section.
Open the web app and on the left side menu click Clusters -> Connect. Fill in:
Click the ‘Register’ button.
Install the agent using helm
: copy the command that was generated after clicking on Register into your terminal:
You can always fetch this command in the future from the clusters list section.
koala cluster register cluster-name -p <project ID> -z <zone>
Then:
helm install
command pre-populated with the unique API key for the cluster, which will install the agent. If needed, you can customize the namespace in which the agent will run.You will need the following information about the cluster:
Here is an example of how to extract those values from the AWS console:
Open the web app and on the left side menu click Clusters -> Connect. Fill in:
The organization field reflects your current Koala organization which can only be changed by using the dropdown on the top left part of the Koala console next to the Koala logoaws.
Click the ‘Register Cluster’ button.
Install the agent using helm
: copy the command that was generated after clicking on Register into your terminal:
You can always fetch this command in the future from the clusters list section.
Kubernetes Ingress is an API object that provides routing rules to manage access to services within a Kubernetes cluster. It acts as a single entry point for external traffic to your Kubernetes services, making it easier to manage and expose your applications to the world.
To enable ingress for your services in the cluster, you should configure the DNS for your domain to point to the cluster. This should be done in your DNS provider.
If a service is deployed in a single cluster, you can directly point the DNS to the cluster’s external IP address. You can see it in your cloud provider’s console, or in the cluster list in app.koalaops.com.
If you’re using a load balancer across clusters, we will soon add support for that, but for now you’ll need to continue to manage that manually. Please continue with the configuration as you would without KoalaOps.