forked from kubero-dev/kubero
-
Notifications
You must be signed in to change notification settings - Fork 0
/
docker-compose.yaml
38 lines (38 loc) · 1.73 KB
/
docker-compose.yaml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
version: "3"
services:
# Kubero usually runs in a Kubernetes cluster in the kubero namespace
# If you want to run it locally, you can use kind to create a local Kubernetes cluster
kubero:
container_name: "kubero-ui"
build:
context: .
args:
- VERSION=Local-Build
dockerfile: Dockerfile
image: ghcr.io/kubero-dev/kubero/kubero:latest
#command: ["tail", "-f", "/dev/null"]
env_file:
# copy the .env.template file to .env and change the values to your needs
- server/.env
environment:
# change the KUBERO_CONTEXT to the name of your local kind cluster context
# you can find the name by running `kubectl config get-contexts`
# Must be the same as the context name in the kubeconfig file !
#- KUBECONFIG_BASE64=
- KUBECONFIG_PATH=./kubeconfig
- KUBERO_CONTEXT=inClusterContext
- KUBERO_NAMESPACE=kubero
- KUBERO_SESSION_KEY=randomString
ports:
# the UI will be available on http://localhost:8000. Make sure the port is not used by another service
- "8000:2000"
extra_hosts:
# if you are using a local Kubernetes cluster, make sure you use the container name from your
# local kind cluster control plane. You can find the name by running `docker ps` and looking for the
# container name of the control plane. 192.168.65.2 is your host machine IP address.
- "kubero-001-control-plane:192.168.65.2"
volumes:
# run `kind get kubeconfig --internal --name kubero-001 > ./kubeconfig-docker` to get the right config
# modify the server in the config to use the external kubernetes port from your host machine
- ./kubeconfig:/app/server/kubeconfig
- ./server/config.yaml:/app/server/config.yaml