-
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 Initial Experiment Step #165
Conversation
Initial PR to resolve #92 |
Codecov Report
@@ Coverage Diff @@
## master #165 +/- ##
=========================================
+ Coverage 82.13% 82.83% +0.7%
=========================================
Files 26 27 +1
Lines 2418 2587 +169
=========================================
+ Hits 1986 2143 +157
- Misses 312 316 +4
- Partials 120 128 +8
Continue to review full report at Codecov.
|
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.
Minor comments about struct names.
pkg/apis/rollouts/v1alpha1/types.go
Outdated
@@ -144,6 +144,48 @@ type CanaryStrategy struct { | |||
MaxSurge *intstr.IntOrString `json:"maxSurge,omitempty"` | |||
} | |||
|
|||
// RolloutCanaryExperimentStep defines a template that is used to create a experiment for a step | |||
type RolloutCanaryExperimentStep struct { |
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 can imagine a future where ExperimentStep is not just being done as part of Canary, but BlueGreen. May want to name this just RolloutExperimentStep to not box ourselves.
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.
Done
pkg/apis/rollouts/v1alpha1/types.go
Outdated
} | ||
|
||
//RolloutExperimentAdditionalMetadata extra labels to add to the template | ||
type RolloutExperimentAdditionalMetadata struct { |
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.
How about: PodTemplateMetadata
. I would make clear that this metadata will go into the labels/annotations of the actual pod
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.
done
a54de3c
to
23f51ec
Compare
No description provided.