# Agilicus Connector Kubernetes

- Link: https://www.agilicus.com/anyx-guide/kubernetes-connector-install/
- Published: 2024-05-14T00:25:41+00:00
- Author: Don Bowman

1. [Home](https://www.agilicus.com/)
 2. Agilicus Connector Kubernetes

![Agilicus Connector Kubernetes](https://www.agilicus.com/www/90da5ea8-undraw_teaching_re_g7e3.
svg)

Agilicus Connector. Cloud Native.

---

## Kubernetes Connector Install

Install the Agilicus Connector, via a Container, in your Kubernetes Cluster. Use
this to reach local services with no public Ingress.

[CONTACT](https://www.agilicus.com/contact-us/)

## Agilicus Connector Kubernetes Install

[⌊connector-install-manual⌉⌊connector-install-manual⌉[

The Kubernetes install is intended for **advanced** usage only. It is for users 
who are integrating with a larger system. As a pre-requisite, you will need kubectl
installed on the machine you will do the installation from.

The steps initially are similar:

 1. Create a new Connector in admin
 2. Select “Install’
 3. Download the binary (using the alternative manual install, see [link](https://www.agilicus.com/anyx-guide/agilicus-connector/)
    for all binaries etc)
 4. Select ‘Manual’. Change –install/–kubernetes-install to **–kubernetes-install**.
    Adjust other parameters as needed
 5. The command will output as below.
 6. Inspect the generated YAML, adjust if necessary
 7. Installl with kubectl apply

    ```has-text-color
    $ agilicus-agent client --kubernetes-install  --challenge-id XXXXXX --challenge-code XXXXXX
    INFO[2023-05-30T18:26:47-04:00] Starting connector - version v0.200.6
    INFO[2023-05-30T18:27:00-04:00] creating connector instance
    INFO[2023-05-30T18:27:01-04:00] Join a connector cluster
    INFO[2023-05-30T18:27:01-04:00] Output Kubernetes YAML
    INFO[2023-05-30T18:27:01-04:00] Now run:
    kubectl apply -f /tmp/agilicus-agent-921551629/agilicus-agent.yaml && rm -rf /tmp/agilicus-agent-921551629
    INFO[2023-05-30T18:27:01-04:00]
    INFO[2023-05-30T18:27:01-04:00] Installation Complete
    INFO[2023-05-30T18:27:01-04:00]
    ```

### Theory of Operation

A small (1G) PVC will be created. This will hold the small amount of configuration(
service account updates)

When creating network services, use the same name service resolution you would normally
use in Kubernetes (e.g. SERVICE.NAMESPACE)

A Deployment will be created with replicas=1

---