-
Notifications
You must be signed in to change notification settings - Fork 137
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Infer csi-usage based on csi-driver-availability #4039
base: main
Are you sure you want to change the base?
Conversation
Codecov ReportAttention: Patch coverage is
❗ Your organization needs to install the Codecov GitHub app to enable full functionality. Additional details and impacted files@@ Coverage Diff @@
## main #4039 +/- ##
==========================================
- Coverage 64.66% 64.65% -0.02%
==========================================
Files 397 397
Lines 26478 26462 -16
==========================================
- Hits 17121 17108 -13
+ Misses 8027 8025 -2
+ Partials 1330 1329 -1
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
config/helm/chart/default/templates/Common/operator/install-config.yaml
Outdated
Show resolved
Hide resolved
|
||
return dk.CloudNativeFullstackMode() || isAppMonitoringWithCSI || isHostMonitoringWithCSI | ||
func (dk *DynaKube) NeedsReadOnlyOneAgents() bool { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Since we are dropping the feature flag, do we still need this check or can it just be a check if CSI driver is used in case of host agent?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
see comment below
9ce0ed7
to
e8da9b1
Compare
Co-authored-by: Albian Krasniqi <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm and it also worked for me
Description
DAQ-1438
Removes the following:
spec.oneAgent.applicationMonitoring.useCSIDriver: true/false
:oneagent-readonly-host-fs
feature-flagSo the expected behavior is:
applicationMonitoring
IF the csi-driver was installedcloudNativeFullstack
hostMonitoring
IF the csi-driver was installedWhat if I have 4 nodes, and only 2 have CSI drivers on them, and I want to use the csi-driver on the 2 nodes where it is available and not use it where it is not? (the "hybrid" configuration)
How can this be tested?
I tested the following 3 configs, in 2 scenarios:
With CSI deployed (
make deploy/helm
)a. Application monitoring -> injected apps have csi-volume
b. Host monitoring -> deployed OS agents have csi-volume
b. Cloud Native Fullstack -> injected apps and deployed OS agents have csi-volume
With CSI deployed (
make deploy/helm/no-csi
)a. Application monitoring -> injected apps have NO csi-volume, does the downloading in the init-container
b. Host monitoring -> deployed OS agents have a not-readonly
host-root
mountb. Cloud Native Fullstack -> validation webhook denies it