Multiple osagents on the same node #608
Merged
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.
Description
Added a dynakube annotation
alpha.operator.dynatrace.com/feature-multiple-osagents-on-node
allowing multitenant hostMonitoring (defaults to"false"
).OneAgent mounts:
If dynakube annotation
alpha.operator.dynatrace.com/feature-multiple-osagents-on-node
==true
,nodeSelector
validation is disabled.How can this be tested?
2+ dynakube objects with
hostMonitoring
enabled (orcloudNativeFullStack
withnamespaceSelector
set so that there is no namespace monitored by more than one dynakube).OneAgent pods are expected to have running status.
Note: currently OneAgent prevents two instances from running on the same host.
Checklist