docs: self hosting with kubernetes#2589
Conversation
| title: "Remote Runs (Beta)" | ||
| --- | ||
|
|
||
| ## TODO: this needs a refresh |
There was a problem hiding this comment.
mind opening up an issue for this? Happy to make a pr, an issue with the docs label would make it easier to track
| Use the OpenTaco Helm charts for Kubernetes deployments: | ||
|
|
||
| ## Coming soon | ||
| - OpenTaco umbrella chart: `self-hosting/kubernetes/helm-charts/opentaco` |
There was a problem hiding this comment.
Thoughts on having this as a prerequisite in a h2? Might make it easier when scanning through
| kubectl create namespace traefik | ||
| ``` | ||
| </Step> | ||
| <Step title="Install the platform reference chart"> |
There was a problem hiding this comment.
I think we might be able to improve the experience, with a one line for obtaining the chart ? If i was trying to breeze through this i'd have to pause and go obtain the chart then come back.
Wdyt?
| ## Deploy OpenTaco with the umbrella chart | ||
|
|
||
| <Steps> | ||
| <Step title="Prepare your values file"> |
There was a problem hiding this comment.
thoughts on giving a quick preview on what the values file should look like? similar to
https://digger-20-sp-docs-refresh-4.mintlify.app/ce/reference/digger.yml#complete-configuration-example
Helps set up expectations
|
|
||
| If you are using the platform reference chart (Traefik), you can check it with: | ||
|
|
||
| ```bash |
There was a problem hiding this comment.
in trying to optimize for copy/pasting, do you think replacing the get svc command could be replaced with something like
kubectl get ingress <ingress-name> -o jsonpath='{.spec.rules[*].host}'
| <Step title="Create or sync Kubernetes secrets (existing-secret path)"> | ||
| If you are using existing secrets, create or sync them now, then ensure `useExistingSecret: true` and `existingSecretName` entries in `values-opentaco.yaml` match. | ||
|
|
||
| ```bash |
There was a problem hiding this comment.
thoughts on moving the commands into individal code blocks? When doing multiple command its slightly easier to break them up, that way you can use the copy button that shows up beside it
i.e this would become:
kubectl create secret generic ui-secrets \
--from-env-file=helm-charts/secrets-example/ui.env \
-n opentaco --dry-run=client -o yaml | kubectl apply -f -kubectl create secret generic taco-orchestrator-secrets \
--from-env-file=helm-charts/secrets-example/digger-backend.env \
-n opentaco --dry-run=client -o yaml | kubectl apply -f -kubectl create secret generic statesman-secrets \
--from-env-file=helm-charts/secrets-example/statesman.env \
-n opentaco --dry-run=client -o yaml | kubectl apply -f -kubectl create secret generic drift-secrets \
--from-env-file=helm-charts/secrets-example/drift.env \
-n opentaco --dry-run=client -o yaml | kubectl apply -f -kubectl create secret generic taco-sidecar-secrets \
--from-env-file=helm-charts/secrets-example/sidecar.env \
-n opentaco --dry-run=client -o yaml | kubectl apply -f -
| @@ -0,0 +1,280 @@ | |||
| # Profile-based startup guide: | |||
There was a problem hiding this comment.
this is mostly a question do you think it would be worth adding a reference for the docker compose environment variables?
s1ntaxe770r
left a comment
s1ntaxe770r
left a comment
There was a problem hiding this comment.
Solid work @sidpalas !!!, a couple comments and questions in between but thanks for the reorg!
2 participants
🧠 Ai UsageDetails (if applicable):
IMPORTANT: Please disclose any usage of ai tooling while making this change. If you did not use any AI write "NA" below