-
Notifications
You must be signed in to change notification settings - Fork 880
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
Add analysis to RolloutExperimentStep #238
Conversation
Codecov Report
@@ Coverage Diff @@
## master #238 +/- ##
==========================================
+ Coverage 85.26% 85.28% +0.02%
==========================================
Files 49 49
Lines 4390 4398 +8
==========================================
+ Hits 3743 3751 +8
Misses 460 460
Partials 187 187
Continue to review full report at Codecov.
|
pkg/apis/rollouts/v1alpha1/types.go
Outdated
@@ -152,7 +152,8 @@ type RolloutExperimentStep struct { | |||
Duration int32 `json:"duration"` | |||
// Templates what templates that should be added to the experiment. Should be non-nil | |||
Templates []RolloutExperimentTemplate `json:"templates"` | |||
//ProgressingDeadlineSeconds Is it ncessary? | |||
//AnalysisTemplate what analysis to run with the experiment | |||
Analysis *RolloutAnalysisStep `json:"analysis,omitempty"` |
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.
Shouldn't this be a list of []ExperimentAnalysisTemplateRef and be named analyses
? This approach means we only support one analysis per experiment step.
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.
I agree with having multiple analyses, but the ExperimentAnalysisTemplateRef doesn't work because it doesn't allow us to inject dynamic values (like podHash) into the analysis.
26f77e6
to
4327aa8
Compare
No description provided.