Skip to content

Latest commit

 

History

History
102 lines (75 loc) · 2.59 KB

DEVELOPMENT.md

File metadata and controls

102 lines (75 loc) · 2.59 KB
Raw

Development

Getting Started

You’ll need a Kubernetes cluster to run against. You can use KIND to get a local cluster for testing, or run against a remote cluster. Note: Your controller will automatically use the current context in your kubeconfig file (i.e. whatever cluster kubectl cluster-info shows).

Running on the cluster

  1. Install Instances of Custom Resources:
kubectl apply -f config/samples/
  1. Build and push your image to the location specified by IMG:
make docker-build docker-push IMG=<some-registry>/cluster-api-provider-ionoscloud:tag
  1. Deploy the controller to the cluster with the image specified by IMG:
make deploy IMG=<some-registry>/cluster-api-provider-ionoscloud:tag

Uninstall CRDs

To delete the CRDs from the cluster:

make uninstall

Undeploy controller

UnDeploy the controller from the cluster:

make undeploy

Contributing

// TODO(user): Add detailed information on how you would like others to contribute to this project

How it works

This project aims to follow the Kubernetes Operator pattern.

It uses Controllers, which provide a reconcile function responsible for synchronizing resources until the desired state is reached on the cluster.

Test It Out

  1. Install the CRDs into the cluster:
make install
  1. Run your controller (this will run in the foreground, so switch to a new terminal if you want to leave it running):
make run

NOTE: You can also run this in one step by running: make install run

Modifying the API definitions

If you are editing the API definitions, generate the manifests such as CRs or CRDs using:

make manifests

NOTE: Run make --help for more information on all potential make targets

More information can be found via the Kubebuilder Documentation

How to use tilt

Copy this to capi project:

.env

export IONOS_USERNAME=""
export IONOS_PASSWORD=""

tilt-settings.yaml

default_registry: "" # change if you use a remote image registry
provider_repos:
  # This refers to your provider directory and loads settings
  # from `tilt-provider.yaml`
  - ../cluster-api-provider-ionoscloud
enable_providers:
  - ionoscloud
  - kubeadm-bootstrap
  - kubeadm-control-plane
debug:
  ionoscloud:
    port: 30000

ctlptl create cluster kind --name kind-capi-test --registry=ctlptl-registry source .env tilt up in capi project