Update k8s boot/strap priority agent version #3018
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
New Relic shouldn't exist after removing it from the load path, so we shouldn't need to check for it
hannahramadan
requested review from
kaylareopelle and
tannalynn
as code owners
hannahramadan
commented
Jan 16, 2025
kaylareopelle
approved these changes
Jan 16, 2025
tannalynn
approved these changes
Jan 16, 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.
Previously, when the new relic ruby agent was installed via in a customer's
Gemfileand attempted to be installed through the k8s operator, the agent version listed inGemfilewould take priority. Now, if the agent is installed via operator when both are present, the Gemfile version will be removed and the operator version will be used.Closes #2890