This repository was archived by the owner on Jun 17, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 1
Expand file tree
/
Copy pathdocker-compose.yaml
More file actions
50 lines (41 loc) · 1.65 KB
/
docker-compose.yaml
File metadata and controls
50 lines (41 loc) · 1.65 KB
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
39
40
41
42
43
44
45
46
47
48
49
50
version: "3"
services:
xk:
image: exekube/exekube:0.3.0-google
working_dir: /project
environment:
USER: root
ENV: ${ENV:?err}
ORGANIZATION_ID:
BILLING_ID:
TF_INPUT: "0"
TF_LOG:
# TF_VAR_project_id is used to create a GCP project for our environment
# via the gcp-project-init script
# It's then used by modules as a space to create resources in
TF_VAR_project_id: ${ENV}-internal-ops-5cfb85
# TF_VAR_serviceaccount_key will be used by the gcp-project-init script
# to put the service account key upon the creation of the GCP project
# It can then be used by modules to authenticate to GCP
TF_VAR_serviceaccount_key: /project/live/${ENV}/secrets/kube-system/owner.json
# TF_VAR is the default directory for Terraform / Terragrunt
# Used when we run `xk up` or `xk down` without an argument
TF_VAR_default_dir: /project/live/${ENV}/k8s
# TF_VAR_secrets_dir is used by multiple modules to source secrets from
TF_VAR_secrets_dir: /project/live/${ENV}/secrets
# Keyring is used by the gcp-secret-mgmt module
# Also by secrets-fetch and secrets-push scripts
# The GCP KMS keyring name to use
TF_VAR_keyring_name: keyring
ports:
- 8001:8001
volumes:
- .:/project
- ./.config/${ENV}/helm:/root/.helm
- ./.config/${ENV}/terragrunt:/root/.terragrunt
- ./.config/${ENV}/gcloud:/root/.config/gcloud
- ./.config/${ENV}/kube:/root/.kube
# EXEKUBE DEVELOPMENT
# - ../../exekube/modules:/exekube-modules
# ---
command: kubectl proxy --address="0.0.0.0" --accept-hosts ".*"