Skip to content

Commit

Permalink
refactor: remove Kardinal Manager yaml file (#33)
Browse files Browse the repository at this point in the history
We want users and devs deploying Kardinal Manager with the Kardinal CLI
command instead of using kubectl, so we are removing the YAML file for
Kardinal Manager to reinforce this, otherwise we will have conflicts
while deploying Kardinal Manager if there are existing resources
deployed with kubectl.
  • Loading branch information
leoporoli authored Jul 11, 2024
1 parent 2ce038f commit f71df5b
Show file tree
Hide file tree
Showing 2 changed files with 13 additions and 82 deletions.
33 changes: 13 additions & 20 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -324,39 +324,32 @@ minikube tunnel

## Deploying Kardinal Manager to local cluster

Configure it by setting the following environment variables:
You can use tilt deploy and keeping the image hot-reloading:

```bash
KARDINAL_MANAGER_CLUSTER_CONFIG_ENDPOINT=http://localhost:8080/tenant/{36e22127-3c9e-4110-aa83-af552cd94b88}/cluster-resources
KARDINAL_MANAGER_FETCHER_JOB_DURATION_SECONDS=10
```

or in the `kardinal-manager/deployment/k8s.yaml`:

```yaml
env:
- name: KARDINAL_MANAGER_CLUSTER_CONFIG_ENDPOINT
# This is valid for reaching out the Kardinal Kontrol if this is running on the host
value: "http://localhost:8080/tenant/36e22127-3c9e-4110-aa83-af552cd94b88/cluster-resources"
- name: KARDINAL_MANAGER_FETCHER_JOB_DURATION_SECONDS
value: "10"
tilt up
```

NOTE: you can get your tenant UUID by running any CLI command
Or you can use the Kardinal CLI to deploy it

You can use tilt deploy and keeping the image hot-reloading:
Option 1: Using Kloud Kardinal Kontrol

```bash
tilt up
# the Kloud Kontrol will always pull the latest image version from Docker Hub
kardinal manager deploy kloud-kontrol
```

Or manually build it:
Option 2: Using the local Kardinal Kontrol with Minikube (better for the dev flow)

```bash
# First set the docker context to minikube
# First build the image

# set the docker context to minikube
eval $(minikube docker-env)
docker load < $(nix build ./#kardinal-manager-container --no-link --print-out-paths)
kubectl apply -f kardinal-manager/deployment
# the local-minikube Kontrol will use the image builded
kardinal manager deploy local-minikube
```
## Deploying Redis Overlay Service to local cluster
Expand Down
62 changes: 0 additions & 62 deletions kardinal-manager/deployment/k8s.yaml

This file was deleted.

0 comments on commit f71df5b

Please sign in to comment.