Add metadata for transform node role #3361
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
Elasticsearch 7.7.0 introduces the transform node role. Add this new node type to the pod metadata when running a version of Elasticsearch that supports transform. Adjust test cases and default values.
pebrc
added a commit
to pebrc/cloud-on-k8s
that referenced
this pull request
Jul 1, 2020
This reverts commit 284e16d.
pebrc
added a commit
that referenced
this pull request
Jul 1, 2020
david-kow
pushed a commit
to david-kow/cloud-on-k8s
that referenced
this pull request
Jul 17, 2020
Elasticsearch 7.7.0 introduces the transform node role. Add this new node type to the pod metadata when running a version of Elasticsearch that supports transform. Adjust test cases and default values.
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.
Elasticsearch 7.7.0 introduces the transform node role.
The complication here is that we now have version specific default configurations. I chose to just toggle the
transformvalue off in the default config to be able to keep using just one config struct. Technically thetransformvalue does not even exist prior to 7.7.0I am targeting this for 1.3.0 as discussed out-of-band but I am happy to reconsider given that documenting the workaround for users might be unnecessarily complex and confusing.