Skip to content

development.md

Latest commit

 

History

History
42 lines (28 loc) · 1.55 KB

development.md

File metadata and controls

42 lines (28 loc) · 1.55 KB
Raw

Development

Build Container Images locally

Create a classic personal access token in GitHub. Set an expiration date and enable the write:packages scope.
Note: Using a token generated by the gh cli is not sufficient.

Login to the ghcr.io registry. When asked for a password, paste the access token:

ko login -u <your_username> --password-stdin ghcr.io

Build image and push to the regsitry:

make images

The pushed image name and tag are logged to the console.

Cloud controller manager

Get started

To run the cloud controller manager locally on your machine, make sure to target the cluster first.

Run make run-cloud-controller-manager to start the controller. It requires you to create a config at ./dev/config.yaml for the cloud-controller-manager. See [./migration/configuration.md] for config reference. This requires you to have the STACKIT CLI installed. The make target will issue a short-lived access-token using the STACKIT CLI.

You can override certain configuration settings for the controller using make variables. The variables are prefixed with CCM_ and represent the corresponding cloud-controller-manager flag. Defaults:

CCM_CONTROLLERS ?= node-route-controller
CCM_CLUSTER_NAME ?= kubernetes
CCM_CLUSTER_CIDR ?= 100.64.0.0/13

Route controller

To test the route controller, you can create a new VPC, routing Table and network using the provided script in hack/setup-vpc.sh <PROJECT_ID>. The script will override your dev/config.yaml with the newly created VPC, routing table and network IDs.