Move off kubernetes
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 18/100
- Issue type
- Refactor
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- google-cloud, kubernetes
- Domain
- cloud, devops, infrastructure
Research direction
Review the migration references in #4230, #4663, #4635, #4077, and #3481, then inventory the Kubernetes components listed here, including the unresolved exechost. Done means the listed services have been migrated to their proposed Google Cloud replacements or removed, and Kubernetes-specific deployments and agents are no longer needed.
Written by the indexing model from the issue text.
Description
Now that Google has managed certs, there isn't a good reason to use kubernetes anymore. We should we able to migrate off as follows:
- apiserver -> move it into dark-editor canvas, rest in cloud run (#4230)
- bwdserver -> cloud run (https://github.com/darklang/dark/issues/4663, #4635 )
- cronchecker -> google cloud scheduler (https://github.com/darklang/dark/issues/4077)
- nginx/cert-manager -> replaced by google managed certs on bwdserver (https://github.com/darklang/dark/issues/4635)
- editor-deployment -> deprecated and removing
- exechost -> ??
- garbage-collector -> removed once traces in cloud storage (#3481)
- tunnel2-deployment -> not necessary once no user code run in k8s (queueworker, apiserver and bwdserver)
- honeycomb-agent -> only used for k8s
- queueworker -> cloud run
- Dominant language
- F#
- Stars
- 2.2k
- Forks
- 115
- Avg merge
- 17h 28m
- Merged PRs (30d)
- 50
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from darklang/dark
-
Difficulty 5/5 Over a week Newbie friendliness 18/100
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
-
Component: CRONs Open
Difficulty 5/5 Over a week Newbie friendliness 15/100
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
-
later
Difficulty 5/5 Over a week Newbie friendliness 20/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
bug confmap/provider/googlesecretmanagerprovider needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
open-telemetry/opentelemetry-collector-contrib#51273 · 2 comments ·
-
Feature needs-triage pulumi/registry
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
infrastructure launch: scale production
Difficulty 2/5 Half a day Newbie friendliness 72/100
Practitionist/familiarise_web#1772 ·