Skip to content

Latest commit

 

History

History
82 lines (53 loc) · 2.98 KB

provision-cluster-and-registry.md

File metadata and controls

82 lines (53 loc) · 2.98 KB
Raw

Provision a cluster and OCI registry

Context

This tutorial shows how to set up a cluster in different environments.

For the control-plane mode, with Kyma Control Plane (KCP) and Kyma runtime (SKR), create two separate clusters following the instructions below.

Procedure

Local cluster setup

  1. Create a k3d cluster:

    k3d cluster create op-kcp --registry-create op-kcp-registry.localhost:8888

# also add for the in-cluster mode only
k3d cluster create op-skr --registry-create op-skr-registry.localhost:8888

  2. Configure the local k3d registry. To reach the registries using localhost, add the following code to your /etc/hosts file:

    # Added for Operator Registries
127.0.0.1 op-kcp-registry.localhost

# also add for the in-cluster mode only
127.0.0.1 op-skr-registry.localhost

  3. Set the IMG environment variable for the docker-build and docker-push commands, to make sure images are accessible by local k3d clusters.

    • For the single-cluster mode:

      # pointing to KCP registry in dual cluster mode  
export IMG=op-kcp-registry.localhost:8888/unsigned/operator-images

    • For the control-plane mode:

      # pointing to SKR registry in dual cluster mode
export IMG=op-skr-registry.localhost:8888/unsigned/operator-images

  4. Once you pushed your image, verify the content. For browsing through the content of the local container registry, use, for example, http://op-kcp-registry.localhost:8888/v2/_catalog?n=100.

Remote cluster setup

Learn how to use a Gardener cluster for testing.

  1. Go to the Gardener account and download your Access Kubeconfig.

  2. Provision a compliant remote cluster using Kyma CLI:

    # gardener_project - Gardener project name
# gcp_secret - Cloud provider secret name (e.g. GCP)
# gardener_account_kubeconfig - path to Access Kubeconfig from Step 1
kyma provision gardener gcp --name op-kcpskr --project ${gardener_project} -s ${gcp_secret} -c ${gardener_account_kubeconfig}

    For example, this could look like kyma provision gardener gcp --name op-kcpskr --project jellyfish -s gcp-jellyfish-secret -c .kube/kubeconfig-garden-jellyfish.yaml.

  3. Create an external registry.

    When using an external registry, make sure that the Gardener cluster (op-kcpskr) can reach your registry.

    You can follow the guide to set up a GCP-hosted artifact registry (GCR).

    CAUTION: For private registries, you may have to configure additional settings not covered in this tutorial.

  4. Set the IMG environment variable for the docker-build and docker-push commands.

    # this an example
# sap-kyma-jellyfish-dev is the GCP project
# operator-test is the artifact registry
export IMG=europe-west3-docker.pkg.dev/sap-kyma-jellyfish-dev/operator-test