Apono Connector for Kubernetes
How to install a Connector on a Kubernetes cluster to integrate Kubernetes with Apono
Last updated
Was this helpful?
How to install a Connector on a Kubernetes cluster to integrate Kubernetes with Apono
Last updated
Was this helpful?
To integrate with Kubernetes and start managing JIT access to Kubernetes resources, you must first install a connector in your Kubernetes cluster.
This is can be done by one of the following methods:
Helm
Terraform
An Apono connector is installed in the cloud platform managing your Kubernetes resource. The installation is made by running a Helm command with the necessary parameters.
An existing Kubernetes project on one of the following platforms:
Google Kubernetes Engine (GKE)
Elastic Kubernetes Service (EKS)
Azure Kubernetes Engine (AKS)
Kubernetes (self-managed)
Helm
kubectl
Select any Kubernetes integration in the Catalog.
From the drop-down list on the next page select Add a New Connector, and then select Help.
Copy the token displayed toward the bottom of the page.
Run the following Helm command in a terminal:
Without permissions
If you would like to install the connector in Kubernetes, but not grant Apono access to read or manage access to Kubernetes resources, use this code:
With permissions
If you would like to install the connector in Kubernetes and grant Apono access to read and manage access to Kubernetes resources, use this code:
Where:
[APONO_TOKEN] is the token copied from the integration page in the previous step.
[CONNECTOR_NAME] is any name you choose to give the connector.
Helm will finish with a message that the apono-connector has been installed.
Interested in HA for the connector?
Add this variable to the Helm chart to create one or more replicas of the Apono connector instance:
--set-string replicaCount=<number_of_replicas>
The Kubernetes Connector is now installed.
Return to the Add new integration form from step 1 for EKS, GKE, AKS or self-managed Kubernetes.
The Connector is found by the form, marked by a green checkmark
You can now integrate Apono with your Kubernetes instance
If you are managing more than one Kubernetes cluster, you must be certain that the current context points to the cluster into which the Apono connector is to be added.
Get the current context with kubectl config current-context
Set the current context with kubectl config use-context [clustername]
An Apono connector is installed in the cloud platform managing your Kubernetes resource. The installation is made by adding an Apono module to your Terraform configuration.
A Kubernetes project on one of the following platforms:
Google Kubernetes Engine (GKE)
Elastic Kubernetes Service (EKS)
Azure Kubernetes Engine (AKS)
Kubernetes (self-managed)
Terraform with the following providers:
Helm
Kubernetes
AWS
Select any Kubernetes integration in the Catalog.
From the drop-down list on the next page select Add a New Connector, and then select Terraform.
Copy the token displayed toward the bottom of the page.
Add the following to your Terraform module.
If you would like to install the connector in Kubernetes, but not grant Apono access to read or manage access to Kubernetes resources, use this code:
If you would like to install the connector in Kubernetes and grant Apono access to read and manage access to Kubernetes resources, use this code:
Where:
[APONO_TOKEN] is the token copied from the integration page in the previous step.
[CONNECTOR_NAME] is any name you choose to give the connector.
Run terraform init
. It will finish with the message:
"Terraform has been successfully initialized!"
Run terraform apply
. It will finish with the message:
"Apply complete! Resources: (N) added.."
The Kubernetes Connector is now installed.
Return to the Add new integration form from step 1 for EKS, GKE, AKS or self-managed Kubernetes.
The Connector is found by the form, marked by a green checkmark
You can now integrate Apono with your Kubernetes instance
Read more .
Complete the integration with , , or .
Complete the integration with , , or .
Return to the , and select one of the following Kubernetes integrations: