CSPL-2438 - Changes to add identifier for SOK deploymens #1249
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
akondur
changed the title
vivekr-splunk
approved these changes
Nov 10, 2023
It was auto-generated with a build - maybe there are newer libraries for the golang version? |
akondur
changed the title
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.
Splunk Operator for Kubernetes(SOK) will add an environment variable
SPLUNK_RESOURCE_LIMITS_SOURCEto all of its Splunk deployments in order to indicate the source for resource limits calculationsNote: If a customer introduces this environment variable unknowingly we have other checks as well in place to hopefully catch it in Splunk. On a failure of the same, we can inform the customer of such a setting in resolve the issue.