-
Notifications
You must be signed in to change notification settings - Fork 112
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
docs: fix installation steps in E2E example #1645
Conversation
Signed-off-by: odubajDT <ondrej.dubaj@dynatrace.com>
✅ Deploy Preview for keptn-lifecycle-toolkit ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
Kudos, SonarCloud Quality Gate passed! |
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.
Could you explain a bit more about what the issue is here? Are the scripts other than make install
broken?
I confess that I am troubled by this Getting Started guide. Having the scripts that set everything up is handy for a demo but seem inadequate for a Getting Started Guide since the user does not learn how to do the set up. This is, of course, outside the scope of this PR, but just saying ;-)
This PR looks good. None of the following comment should be seen as a blocker for getting this PR merged. But I agree with @StackScribe. A magic On a different note, there's this comment: "Note To export traces to the OpenTelemetry Collector, you need a KeptnConfig CRD with spec.OTelCollectorUrl specified in the namespace where KLT is installed." The comment is ambiguous though as to whether or not the Since the emission of OTEL metrics is a core use case, should we build OTEL emission and a collector into the demo? |
Hey @agardnerIT @StackScribe . Thank you for your comments, totally agree! We should maybe work on a more specific explanation what is actually hidden behind Thanks! |
Fixes: #1640