Getting started

Get started using Claudie¶

Before you begin, please make sure you have the following prerequisites installed and set up:

Claudie needs to be installed on an existing Kubernetes cluster, which it uses to manage the clusters it provisions. For testing, you can use ephemeral clusters like Minikube or Kind. However, for production environments, we recommend using a more resilient solution since Claudie maintains the state of the infrastructure it creates.
Claudie requires the installation of cert-manager in your Kubernetes cluster. To install cert-manager, use the following command:
```
kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.12.0/cert-manager.yaml
```

For adding support for other cloud providers, open an issue or propose a PR.

Download and extract Claudie manifests from our release page:

wget https://github.com/berops/claudie/releases/latest/download/claudie.zip && unzip claudie.zip -d claudie

Deploy Claudie into your management Kubernetes cluster:
```
kubectl apply -k claudie
```

Deploy input manifest secret which Claudie uses to create infrastructure across various hyperscalers:
```
kubectl create secret generic input-manifest --from-file=input-manifest.yaml -n claudie
```

Check the supported providers for input manifest examples. For an input manifest spanning all supported hyperscalers checkout out this example.

Label the input-manifest secret created in the previous step to enable the Claudie frontend service to recognize it as part of Claudie and initiate the creation of the specified infrastructure.
```
kubectl label secret input-manifest claudie.io/input-manifest=claudie-testing -n claudie
```
If you wish to adjust your already created input manifest you can do so without deleting or replacing the secret itself:
```
kubectl create secret generic input-manifest --from-file=input-manifest.yaml -n claudie -oyaml --dry-run=client | kubectl
apply -f -
```
Deleting existing secret deletes provisioned infrastructure!

Claudie outputs base64 encoded kubeconfig secret <cluster-name>-<cluster-hash>-kubeconfig in the namespace where it is deployed:

Recover kubeconfig of your cluster by running:

kubectl get secrets -n claudie -l claudie.io/output=kubeconfig -o jsonpath='{.items[0].data.kubeconfig}' | base64 -d > your_kubeconfig.yaml

Use your new kubeconfig:

kubectl get pods -A --kubeconfig=your_kubeconfig.yaml

To remove your cluster and its associated infrastructure, delete the cluster definition block from the input-manifest and update the secret:

kubectl create secret generic input-manifest --from-file=input-manifest.yaml -n claudie -oyaml --dry-run=client | kubectl apply -f -

To delete all clusters defined in the input manifest, delete the secret. This triggers the deletion process, removing the infrastructure and all data associated with the manifest.
```
kubectl delete secret input-manifest -n claudie
```