Learn how to install the Application Connector module locally (on k3d) or on your remote cluster.
- Access to a Kubernetes (v1.24 or higher) cluster
- Go
- Docker
- kubectl
- kubebuilder
You can build and run the Application Connector Manager in the Kubernetes cluster without Kyma. For the day-to-day development on your machine, you don't always need to have it controlled by Kyma's Lifecycle Manager.
Run the following commands to deploy Application Connector Manager in a target Kubernetes cluster, such as k3d:
-
Clone the project.
git clone https://github.com/kyma-project/application-connector-manager.git && cd application-connector-manager/
-
Set the Application Connector Manager image name.
NOTE: You can use the local k3d registry or your Docker Hub account to push intermediate images.
export IMG=<DOCKER_USERNAME>/custom-application-connector-manager:0.0.1
-
Test the code.
make test
-
Build and push the image to the registry.
make module-image
-
Create a target namespace.
kubectl create ns kyma-system
-
Deploy Application Connector Manager.
make deploy
-
Verify if Application Connector Manager is deployed.
kubectl get deployments -n kyma-system
You should get a result similar to this example:
NAME READY UP-TO-DATE AVAILABLE AGE application-connector-controller-manager 1/1 1 1 20s
When using a local k3d cluster, you can also use the local OCI image registry that comes with it. Thanks to that, you don't need to push the Application Connector module images to a remote registry and you can test the changes in the Kyma installation set up entirely on your machine.
-
Clone the project.
git clone https://github.com/kyma-project/application-connector-manager.git && cd application-connector-manager/
-
Build the manager locally and run it in the k3d cluster.
make -C hack/local run-without-lifecycle-manager
-
If you want to clean up the k3d cluster, use the
make -C hack/local stop
make target.