Skip to content

Latest commit

 

History

History
72 lines (49 loc) · 2.48 KB

INSTALL.kind.md

File metadata and controls

72 lines (49 loc) · 2.48 KB
Raw

Warning Make sure you are using the correct version of these instructions by using the link in the release notes for the version you're trying to install. If you're not sure, check our latest release.

Install Korifi on kind

This document integrates our install instructions with specific tips to install Korifi locally using kind.

Initial setup

Export the following environment variables:

ROOT_NAMESPACE="cf"
KORIFI_NAMESPACE="korifi-system"
ADMIN_USERNAME="kubernetes-admin"
BASE_DOMAIN="apps-127-0-0-1.nip.io"

apps-127-0-0-1.nip.io will conveniently resolve to 127.0.0.1 using nip.io, which is exactly what we need.

Cluster creation

In order to access the Korifi API, we'll need to expose the cluster ingress locally. To do it, create your kind cluster using a command like this:

cat <<EOF | kind create cluster --config=-
kind: Cluster
apiVersion: kind.x-k8s.io/v1alpha4
nodes:
- role: control-plane
  extraPortMappings:
  - containerPort: 80
    hostPort: 80
    protocol: TCP
  - containerPort: 443
    hostPort: 443
    protocol: TCP
EOF

Container registry

We recommend you use DockerHub as your container registry.

Dependencies

No changes here, follow the common instructions.

Pre-install configuration

No changes here, follow the common instructions. For the container registry credentials Secret, we recommend you create an access token on DockerHub.

Install Korifi

No changes here, follow the common instructions. If using DockerHub as recommended above, set the following values:

  • api.packageRepository: index.docker.io/<username>/packages;
  • kpackImageBuilder.builderRepository: index.docker.io/<username>/kpack-builder;
  • kpackImageBuilder.dropletRepository: index.docker.io/<username>/droplets.

If $KORIFI_NAMESPACE doesn't exist yet, you can add the --create-namespace flag to the helm invocation.

Post-install Configuration

Yon can skip this section.

Test Korifi

No changes here, follow the common instructions. When running cf login, make sure you select the entry associated to your kind cluster (kind-kind by default).