Add wrapper bash script to deploy the demo #160
Merged
Conversation
This file contains hidden or 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
rogercoll
reviewed
Sep 22, 2025
Collaborator
rogercoll
left a comment
rogercoll
left a comment
There was a problem hiding this comment.
Great feature, this will simplify installations 🎉
I think the script is missing creating the K8s namespace: Error from server (NotFound): error when creating "STDIN": namespaces "opentelemetry-operator-system" not found
Co-authored-by: Roger Coll <roger.coll@elastic.co>
Co-authored-by: Roger Coll <roger.coll@elastic.co>
Co-authored-by: Roger Coll <roger.coll@elastic.co>
Co-authored-by: Roger Coll <roger.coll@elastic.co>
Co-authored-by: Roger Coll <roger.coll@elastic.co>
girodav
commented
Sep 24, 2025
rogercoll
approved these changes
Sep 25, 2025
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.
This PR introduces a script that automates the deployment of demo applications and EDOT, with configurations and wiring already in place. The only required input is Elastic credentials, streamlining the demo launch process.
The original manual configuration remains intact and can still be followed, especially if users prefer to provide a custom OTel Collector configuration.