Deprecate certain fields in HumioCluster and remove use of unused env… #771
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.
…ironment variables
Previously the operator would automatically append these to the environment variables for pods, but as of LogScale 1.89.0 they are no longer needed/used and we can use the default behavior. To override default behavior it is possible to do that by referring to the LogScale documentation and setting the relevant environment variables.
The environment variables no longer set for pods running LogScale 1.89.0 and newer:
Since this changes the environment variables list for pods if running LogScale 1.89.0+ it means cluster pods will be replaced when upgrading to an operator version with these changes.