test: use release versions of the elastic-otel-node and elastic-otel-python Docker images, now that we have them #3
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
…python Docker images, now that we have them
|
This should be done in the upstream repo now, elastic#16. Keeping the images up-to-date should be done with a bot (likely renovate) |
jackshirazi
added a commit
that referenced
this pull request
Oct 10, 2024
* docs: add onboarding onprem Operator values * fix: autogenerate level * docs: add Operator commands * enable Go auto instrumentation * exclude operator logs * add missing configuration to the onprem_kube_stack_values.yaml (#1) Signed-off-by: Tetiana Kravchenko <[email protected]> * chore: use OTEL_K8S_NODE_NAME env var * docs: add information about the Helm deployment * add namespace creation command * collector configurations enhancements (#2) * splite otel and ecs pipelines for logs and metrics Signed-off-by: Tetiana Kravchenko <[email protected]> * remove default k8sobjects config; add storeCheckpoints for logs; add clusterName Signed-off-by: Tetiana Kravchenko <[email protected]> * comment out tls.insecure_skip_verify Signed-off-by: Tetiana Kravchenko <[email protected]> * remove in deployment: elasticsearch/apm, remove in daemon: hostmetrics from metrics/node/otel pipeline Signed-off-by: Tetiana Kravchenko <[email protected]> --------- Signed-off-by: Tetiana Kravchenko <[email protected]> * pin Chart version * add Java, Go, Node.js, .NET and Python autoinstrumentation Co-authored-by: jackshirazi <[email protected]> * Update docs/onboarding/8_16/operator/values.yaml Co-authored-by: jackshirazi <[email protected]> * Update docs/onboarding/8_16/operator/README.md Co-authored-by: jackshirazi <[email protected]> * remove k8s_logs_dataset; add configmaps clusterRole rule (#3) * remove k8s_logs_dataset; add configmaps clusterRole rule Signed-off-by: Tetiana Kravchenko <[email protected]> * add a comment for clusterName Signed-off-by: Tetiana Kravchenko <[email protected]> --------- Signed-off-by: Tetiana Kravchenko <[email protected]> * docs: remove suggestion needed backslashes * bump chart version --------- Signed-off-by: Tetiana Kravchenko <[email protected]> Co-authored-by: Tetiana Kravchenko <[email protected]> Co-authored-by: jackshirazi <[email protected]>
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.
/cc @xrmx
@jackshirazi Did you have thoughts/plans on keeping these docker image version tags up to date? Or had you considering using the
latesttag?