-
Notifications
You must be signed in to change notification settings - Fork 13
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
ELASTIC_APM_ACTIVATION_METHOD=K8S_ATTACH
, prefer ELASTIC_APM_SERVER_URL
; integration.yml workflow tweak
#87
Merged
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
github-actions
bot
added
the
apm-k8s-attacher
Mutating Webhook to attach apm agents on k8s
label
Jan 8, 2024
…th java, but not the Node.js or other APM agents
estolfo
previously approved these changes
Jan 10, 2024
trentm
changed the title
test: drop redundant kind cluster creation in integration.yml workflow
docs: prefer singular Jan 10, 2024
ELASTIC_APM_SERVER_URL
; integration.yml workflow tweak
…es.yaml This means that custom 'webhookConfig.agent.*' names do not need to repeat this envvar. It *does* mean that newer Node.js and .NET APM agents that use the newer value (used to be 'K8S') will be required for the 'activation_method' to get set correctly. Closes: #91
trentm
changed the title
docs: prefer singular
Jan 11, 2024
ELASTIC_APM_SERVER_URL
; integration.yml workflow tweakELASTIC_APM_ACTIVATION_METHOD=K8S_ATTACH
, prefer ELASTIC_APM_SERVER_URL
; integration.yml workflow tweak
How I tested the ELASTIC_APM_ACTIVATION_METHOD change
We'll be using this image later.
Run this to install the chart:
For example:
|
@jackshirazi Please take a look |
estolfo
approved these changes
Jan 12, 2024
jackshirazi
approved these changes
Jan 12, 2024
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.
lovely, thanks!
FYI: for the |
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.
Set ELASTIC_APM_ACTIVATION_METHOD=K8S_ATTACH in code rather than values.yaml
This means that custom 'webhookConfig.agent.*' names do not need to repeat this
envvar. It does mean that newer Node.js and .NET APM agents that use the
newer value (used to be 'K8S') will be required for the 'activation_method' to
get set correctly.
Also:
ELASTIC_APM_SERVER_URL
, because the plural only works with the java agent. The use cases in the tests were probably fine, but there was one case in docs where the plural was being suggested for possible Node.js APM agent use.Closes: #91