doc: add MAINTENANCE.md, DEVELOPER.md #40
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Langleu
reviewed
Apr 22, 2024
Comment on lines
+7
to
+8
| TODO: this part is not yet documented outside of the official documentation: https://docs.camunda.io/docs/next/self-managed/setup/deploy/amazon/amazon-eks/dual-region/ | ||
|
|
There was a problem hiding this comment.
TBH, I don't have a good developer setup besides the guide.
Overall, one can run the whole setup on a single cluster (even kind) without the whole DNS chaining etc. but at the end of the day, Elasticsearch will always be problematic as it needs a proper backup solution if one wants failback/failover.
Like we could describe a setup based on kind and host file system, just that I'm not sure the use justifies it.
If AWS remains the way to go.
- Create a Kubernetes cluster (any flavour)
- Adjust values in
camunda-values.ymlinaws/dual-region/kubernetesby utilizing the scriptsaws/dual-region/scripts/
2.1.create_elasticsearch_secrets.shandgenerate_zeebe_helm_values.sh - Deploy
aws/dual-region/kubernetes/region0to namespacecamunda-primary
helm install camunda camunda/camunda-platform -f camunda-values.yml -f region0/camunda-values.yml --create-namespace --namespace camunda-primary
- Deploy
aws/dual-region/kubernetes/region1to namespacecamunda-secondary
helm install camunda camunda/camunda-platform -f camunda-values.yml -f region1/camunda-values.yml --create-namespace --namespace camunda-primary
Langleu
approved these changes
Apr 22, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
https://github.com/camunda/team-infrastructure-experience/issues/160 related