Local Test Setup in the Control Plane Mode Using k3d

Supported Versions

Golang: v1.22.5

k3d: v5.6.0

k3s: v1.27.4-k3s1 (default)

kubectl:

Client Version: v1.30.2

Server Version: v1.27.4+k3s1

docker:

Client Version: v26.1.4

Server: Docker Desktop v4.31.0

Engine Version: v26.1.4

Context

This tutorial shows how to configure a fully working e2e test setup including the following components:

Lifecycle Manager
Runtime Watcher on a remote cluster
template-operator on a remote cluster as an example

This setup is deployed with the following security features enabled:

Strict mTLS connection between Kyma Control Plane (KCP) and SKR clusters
SAN Pinning (SAN of client TLS certificate needs to match the DNS annotation of a corresponding Kyma CR)

Procedure

KCP Cluster Setup

Create a local KCP cluster:

k3d cluster create kcp-local --port 9443:443@loadbalancer \
--registry-create k3d-registry.localhost:0.0.0.0:5111 \
--k3s-arg '--disable=traefik@server:0' \
--k3s-arg --tls-san=host.k3d.internal@server:*

Open /etc/hosts file on your local system:
```
sudo nano /etc/hosts
```
Add an entry for your local k3d registry created in step 1:
```
127.0.0.1 k3d-registry.localhost
```

Install the following prerequisites required by Lifecycle Manager:

Istio CRDs using istioctl:

brew install istioctl && \
istioctl install --set profile=demo -y

cert-manager by Jetstack:

kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.13.3/cert-manager.yaml

Deploy Lifecycle Manager in the cluster:

make local-deploy-with-watcher IMG=europe-docker.pkg.dev/kyma-project/prod/lifecycle-manager:latest

TIP: If you get an error similar to the following, wait a couple of seconds and rerun the command.

Error from server (InternalError): error when creating "STDIN": Internal error occurred: failed calling webhook "webhook.cert-manager.io": failed to call webhook: Post "https://cert-manager-webhook.cert-manager.svc:443/mutate?timeout=10s": no endpoints available for service "cert-manager-webhook"

Custom Lifecycle Manager image deployment

If you want to test a custom image of Lifecycle Manager, run the following:

# build your local image
make docker-build IMG=k3d-registry.localhost:5111/<your-image-name>:<your-image-tag>
# push the image to the local registry
make docker-push IMG=k3d-registry.localhost:5111/<your-image-name>:<your-image-tag>
# deploy Lifecycle Manager using the image (note the change to port 5000 which is exposed in the cluster)
make local-deploy-with-watcher IMG=k3d-registry.localhost:5000/<your-image-name>:<your-image-tag>

Create a ModuleTemplate CR using modulectl. The ModuleTemplate CR includes component descriptors for module installations.

In this tutorial, we will create a ModuleTemplate CR from the template-operator repository. Adjust the path to your template-operator local directory or any other reference module operator accordingly.

cd <local path to template operator repository>

# generate the manifests and save them to the template-operator.yaml file
make build-manifests

# create the a ModuleTemplate CR and save it to the template.yaml file
modulectl create --config-file ./module-config.yaml --registry http://k3d-registry.localhost:5111 --insecure

Verify images pushed to the local registry:

curl http://k3d-registry.localhost:5111/v2/_catalog\?n\=100

The output should look like the following:

{"repositories":["component-descriptors/kyma-project.io/module/template-operator"]}

Open the generated template.yaml file and change the following line:
```
 <...>
   - baseUrl: k3d-registry.localhost:5111
 <...>
```
To the following:
```
<...>
  - baseUrl: k3d-registry.localhost:5000
<...>
```
You need the change because the operators are running inside of two local k3d clusters, and the internal port for the k3d registry is set by default to 5000.
Apply the template:
```
kubectl apply -f ./template.yaml
```

SKR Cluster Setup

Create a local Kyma runtime (SKR) cluster:

k3d cluster create skr-local --k3s-arg --tls-san=host.k3d.internal@server:*

Create a Kyma CR and a Remote Secret

Switch the context for using the KCP cluster:
```
kubectl config use-context k3d-kcp-local
```

Generate and apply a sample Kyma CR and its corresponding Secret on KCP:

cat <<EOF | kubectl apply -f -
apiVersion: v1
kind: Secret
metadata:
  name: kyma-sample
  namespace: kcp-system
  labels:
    "operator.kyma-project.io/kyma-name": "kyma-sample"
    "operator.kyma-project.io/managed-by": "lifecycle-manager"
data:
  config: $(k3d kubeconfig get skr-local | sed 's/0\.0\.0\.0/host.k3d.internal/' | base64 | tr -d '\n')
---
apiVersion: operator.kyma-project.io/v1beta2
kind: Kyma
metadata:
  annotations:
    skr-domain: "example.domain.com"
  name: kyma-sample
  namespace: kcp-system
spec:
  channel: regular
EOF

Running Lifecycle Manager on a local machine and not on a cluster

If you are running Lifecycle Manager on your local machine and not as a deployment on a cluster, use the following to create a Kyma CR and Secret:

cat << EOF | kubectl apply -f -
---
apiVersion: v1
kind: Secret
metadata:
   name: kyma-sample
   namespace: kcp-system
   labels:
      "operator.kyma-project.io/kyma-name": "kyma-sample"
      "operator.kyma-project.io/managed-by": "lifecycle-manager"
data:
   config: $(k3d kubeconfig get skr-local | base64 | tr -d '\n')
---
apiVersion: operator.kyma-project.io/v1beta2
kind: Kyma
metadata:
   annotations:
     skr-domain: "example.domain.com"
   name: kyma-sample
   namespace: kcp-system
spec:
   channel: regular
   modules:
   - name: template-operator
EOF

Watcher and Module Installation Verification

Check the Kyma CR events to verify if the SKRWebhookIsReady condition is set to True. Also make sure if the state of the template-operator is Ready and check the overall state.

status:
   activeChannel: regular
   conditions:
      - lastTransitionTime: "2023-02-28T06:42:00Z"
        message: skrwebhook is synchronized
        observedGeneration: 1
        reason: SKRWebhookIsReady
        status: "True"
        type: Ready
   lastOperation:
      lastUpdateTime: "2023-02-28T06:42:00Z"
      operation: kyma is ready
   modules:
      - channel: regular
        fqdn: kyma-project.io/module/template-operator
        manifest:
           apiVersion: operator.kyma-project.io/v1beta2
           kind: Manifest
           metadata:
              generation: 1
              name: kyma-sample-template-operator-3685142144
              namespace: kcp-system
        name: template-operator
        state: Ready
        template:
           apiVersion: operator.kyma-project.io/v1beta2
           kind: ModuleTemplate
           metadata:
              generation: 1
              name: moduletemplate-template-operator
              namespace: kcp-system
        version: 1.2.3
   state: Ready

(Optional) Check the Functionality of the Watcher Component

Switch the context to use the SKR cluster:
```
kubectl config use-context k3d-skr-local
```
Change the channel of the template-operator module to trigger a watcher event to KCP:
```
  modules:
  - name: template-operator
    channel: fast
```

Verify logs

By watching the skr-webhook deployment logs, verify if the KCP request is sent successfully:

1.6711877286771238e+09    INFO    skr-webhook    Kyma UPDATE validated from webhook 
1.6711879279507768e+09    INFO    skr-webhook    incoming admission review for: operator.kyma-project.io/v1alpha1, Kind=Kyma 
1.671187927950956e+09    INFO    skr-webhook    KCP    {"url": "https://host.k3d.internal:9443/v1/lifecycle-manager/event"} 
1.6711879280545895e+09    INFO    skr-webhook    sent request to KCP successfully for resource default/kyma-sample 
1.6711879280546305e+09    INFO    skr-webhook    kcp request succeeded

In Lifecycle Manager's logs, verify if the listener is logging messages indicating the reception of a message from the watcher:

{"level":"INFO","date":"2023-01-05T09:21:51.01093031Z","caller":"event/skr_events_listener.go:111","msg":"dispatched event object into channel","context":{"Module":"Listener","resource-name":"kyma-sample"}}
{"level":"INFO","date":"2023-01-05T09:21:51.010985Z","logger":"listener","caller":"controllers/setup.go:100","msg":"event coming from SKR, adding default/kyma-sample to queue","context":{}}                                                                            
{"level":"INFO","date":"2023-01-05T09:21:51.011080512Z","caller":"controllers/kyma_controller.go:87","msg":"reconciling modules","context":{"controller":"kyma","controllerGroup":"operator.kyma-project.io","controllerKind":"Kyma","kyma":{"name":"kyma-sample","namespace":"default"},"namespace":"default","name":"kyma-sample","reconcileID":"f9b42382-dc68-41d2-96de-02b24e3ac2d6"}}
{"level":"INFO","date":"2023-01-05T09:21:51.043800866Z","caller":"controllers/kyma_controller.go:206","msg":"syncing state","context":{"controller":"kyma","controllerGroup":"operator.kyma-project.io","controllerKind":"Kyma","kyma":{"name":"kyma-sample","namespace":"default"},"namespace":"default","name":"kyma-sample","reconcileID":"f9b42382-dc68-41d2-96de-02b24e3ac2d6","state":"Processing"}}

Cleanup

Run the following command to remove the local testing clusters:

k3d cluster rm kcp-local skr-local

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

04-local-test-setup.md

04-local-test-setup.md

Local Test Setup in the Control Plane Mode Using k3d

Supported Versions

Context

Procedure

KCP Cluster Setup

SKR Cluster Setup

Create a Kyma CR and a Remote Secret

Watcher and Module Installation Verification

(Optional) Check the Functionality of the Watcher Component

Verify logs

Cleanup

Files

04-local-test-setup.md

Latest commit

History

04-local-test-setup.md

File metadata and controls

Local Test Setup in the Control Plane Mode Using k3d

Supported Versions

Context

Procedure

KCP Cluster Setup

SKR Cluster Setup

Create a Kyma CR and a Remote Secret

Watcher and Module Installation Verification

(Optional) Check the Functionality of the Watcher Component

Verify logs

Cleanup