Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[demo] - clarify demo upgrade capability in Kubernetes #5655

Merged
merged 11 commits into from
Nov 22, 2024

Conversation

puckpuck
Copy link
Contributor

When the demo is started in a Kubernetes world, we use init-containers to ensure the order of services to be started (e.g., Kafka before fraud detection). However, when upgrading the demo, the order in which services are restarted can not be guaranteed. Because of this, the demo install in Kubernetes has never supported an upgrade operation, and this PR adds a note to clarify that.

@puckpuck puckpuck requested a review from a team as a code owner November 21, 2024 04:26
@opentelemetrybot opentelemetrybot requested a review from a team November 21, 2024 04:27
@opentelemetrybot opentelemetrybot requested a review from a team November 21, 2024 15:08
Copy link
Contributor

@tiffany76 tiffany76 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM with a few small copyedits.

content/en/docs/demo/kubernetes-deployment.md Outdated Show resolved Hide resolved
content/en/docs/demo/kubernetes-deployment.md Outdated Show resolved Hide resolved
@svrnm svrnm added this pull request to the merge queue Nov 22, 2024
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Nov 22, 2024
@svrnm svrnm added this pull request to the merge queue Nov 22, 2024
Merged via the queue into open-telemetry:main with commit e4716bd Nov 22, 2024
17 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

5 participants