-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
base: main
Are you sure you want to change the base?
[demo] - clarify demo upgrade capability in Kubernetes #5655
Conversation
> **Note** The OpenTelemetry Demo Helm chart does not support being upgraded | ||
> from one version to another. If you need to upgrade the chart, you must first | ||
> delete the existing release and then install the new version. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
> **Note** The OpenTelemetry Demo Helm chart does not support being upgraded | |
> from one version to another. If you need to upgrade the chart, you must first | |
> delete the existing release and then install the new version. | |
{{% alert title="Note" color="info" %}} | |
The OpenTelemetry Demo Helm chart does not support being upgraded | |
from one version to another. If you need to upgrade the chart, you must first | |
delete the existing release and then install the new version. | |
{{% /alert %}} |
we prefer to make use of the docsy shortcode for alerts, since it gives us more flexibility in styling
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I updated this note, and all other notes in this file to use the docsy shortcode
Co-authored-by: Juliano Costa <[email protected]>
There was a problem hiding this 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.
Co-authored-by: Tiffany Hrabusa <[email protected]>
Co-authored-by: Tiffany Hrabusa <[email protected]>
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.