-
Notifications
You must be signed in to change notification settings - Fork 38.7k
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
Promote ImageMaximumGCAge to beta #123424
Conversation
66d3970
to
48107ba
Compare
48107ba
to
2d2c5e2
Compare
PR looks good. You addressed the feedback in the review in separate PRs so I think this is good to me. /lgtm |
LGTM label has been added. Git tree hash: b2705470e06a2364ca30af9251a73a526436f248
|
/triage accepted |
/label api-review Very minor issue in kubelet config tests and we need api approver help. |
pkg/features/kube_features.go
Outdated
@@ -1153,7 +1154,7 @@ var defaultKubernetesFeatureGates = map[featuregate.Feature]featuregate.FeatureS | |||
|
|||
LoadBalancerIPMode: {Default: false, PreRelease: featuregate.Alpha}, | |||
|
|||
ImageMaximumGCAge: {Default: false, PreRelease: featuregate.Alpha}, | |||
ImageMaximumGCAge: {Default: true, PreRelease: featuregate.Beta}, |
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.
move this line so it is in alphabetical order in the list of features, that helps minimize conflicts
conf.ImageMaximumGCAge = metav1.Duration{Duration: 1} | ||
return conf | ||
}, | ||
errMsg: "invalid configuration: ImageMaximumGCAge feature gate is required for Kubelet configuration option ImageMaximumGCAge", | ||
}, { | ||
name: "imageMaximumGCAge should not be negative", | ||
configure: func(conf *kubeletconfig.KubeletConfiguration) *kubeletconfig.KubeletConfiguration { | ||
conf.FeatureGates = map[string]bool{"ImageMaximumGCAge": true} |
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.
keep these lines... if we have to toggle the gate back off, we don't want to have to mess with this unit test to test this behavior
conf.ImageMaximumGCAge = metav1.Duration{Duration: -1} | ||
return conf | ||
}, | ||
errMsg: "invalid configuration: imageMaximumGCAge -1ns must not be negative", | ||
}, { | ||
name: "imageMaximumGCAge should not be less than imageMinimumGCAge", | ||
configure: func(conf *kubeletconfig.KubeletConfiguration) *kubeletconfig.KubeletConfiguration { | ||
conf.FeatureGates = map[string]bool{"ImageMaximumGCAge": true} |
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.
keep these lines... if we have to toggle the gate back off, we don't want to have to mess with this unit test to test this behavior
test/e2e_node/image_gc_test.go
Outdated
@@ -41,7 +40,7 @@ const ( | |||
checkGCFreq time.Duration = 30 * time.Second | |||
) | |||
|
|||
var _ = SIGDescribe("ImageGarbageCollect", framework.WithSerial(), framework.WithNodeFeature("GarbageCollect"), func() { |
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.
the feature is still required, right? it just happens to be beta now
test/e2e_node/image_gc_test.go
Outdated
if initialConfig.FeatureGates == nil { | ||
initialConfig.FeatureGates = make(map[string]bool) | ||
} | ||
initialConfig.FeatureGates[string(kubefeatures.ImageMaximumGCAge)] = true |
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.
does it hurt anything to keep the feature explicitly turned on in the test?
and set to be on by default, adapting e2e tests for it Signed-off-by: Peter Hunt <pehunt@redhat.com>
2d2c5e2
to
cb39dfc
Compare
thanks @liggitt done! |
/lgtm |
LGTM label has been added. Git tree hash: 88a6e244dd79e781c4434d51a2069fecf343b1fc
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: haircommander, liggitt, mrunalp The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
What type of PR is this?
/kind feature
What this PR does / why we need it:
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: