-
Notifications
You must be signed in to change notification settings - Fork 39.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
Enable changing times on volume attach/detach reconciling sync to fixing impact to AWS #39551
Enable changing times on volume attach/detach reconciling sync to fixing impact to AWS #39551
Conversation
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.
this doesn't actually fix the underlying problem but will unblock users who are seeing AWS API call flooding due to volume checks.
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.
Couple of early comments
// successive executions. This has been increased from every 100 ms to | ||
// 1 minute since the timing has created an enormous amount of API traffic on | ||
// such clouds as AWS. | ||
reconcilerLoopPeriod time.Duration = 1 * time.Minute |
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.
This doesn't increase or decrease the rate of API calls, and break a lot of things (by reducing the rate at which the attach detach controller can react, so let's leave this alone.
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.
will do
reconcilerSyncDuration time.Duration = 5 * time.Second | ||
// This has been increased from every 5 seconds to every 5 minutes since | ||
// the timing has created an enormous amount of API traffic on such clouds as AWS. | ||
reconcilerSyncDuration time.Duration = 5 * time.Minute |
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.
Let's make this 1 minute instead of 5 (which will still reduce the rate 12x times). There is a tradeoff--without this check we could potentially reintroduce the AWS bug of wrong volume being attached.
Also maybe make this value configurable/enabled/disable in the same PR?
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.
@saad-ali that is the second PR that I wanted to drop. Since I am not super familiar with wiring in the cobra options.
Will let this build run, and then wire in the cobra options. @saad-ali has asked for both in the same PR. |
A couple of unit tests are failing on osx. I am going to run some build tests tonight. Also need to update openapi. |
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.
Some preliminary comments.
@@ -80,6 +80,8 @@ func (s *CloudControllerManagerServer) AddFlags(fs *pflag.FlagSet) { | |||
fs.Float32Var(&s.KubeAPIQPS, "kube-api-qps", s.KubeAPIQPS, "QPS to use while talking with kubernetes apiserver") | |||
fs.Int32Var(&s.KubeAPIBurst, "kube-api-burst", s.KubeAPIBurst, "Burst to use while talking with kubernetes apiserver") | |||
fs.DurationVar(&s.ControllerStartInterval.Duration, "controller-start-interval", s.ControllerStartInterval.Duration, "Interval between starting controller managers.") | |||
fs.BoolVar(&s.DisableReconciliation, "disable-reconcile", false, "Disable Volume Reconcilation") | |||
fs.DurationVar(&s.ReconcilerLoopPeriod, "reconcile-loop-period", 5 * time.Minute,"The wait time between volume reconciliation") |
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.
Default 1 minutes please :)
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.
That is really short. What is the side effect of doing at 5?
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 had another idea - but it may not work if ReconcilerLoopPeriod
is declared as a Duration. We can keep one variable int32
or something and if it is -1
- that means disable the sync otherwise the value means sync interval in seconds.
Basically lesser the knobs and switches we have - it is probably better.
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.
Understand that, but I alway look for the big red button. We are shutting down important code, and accidentally shutting it down would not be nice.
@@ -80,6 +80,8 @@ func (s *CloudControllerManagerServer) AddFlags(fs *pflag.FlagSet) { | |||
fs.Float32Var(&s.KubeAPIQPS, "kube-api-qps", s.KubeAPIQPS, "QPS to use while talking with kubernetes apiserver") | |||
fs.Int32Var(&s.KubeAPIBurst, "kube-api-burst", s.KubeAPIBurst, "Burst to use while talking with kubernetes apiserver") | |||
fs.DurationVar(&s.ControllerStartInterval.Duration, "controller-start-interval", s.ControllerStartInterval.Duration, "Interval between starting controller managers.") | |||
fs.BoolVar(&s.DisableReconciliation, "disable-reconcile", false, "Disable Volume Reconcilation") |
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 DisableAttachDetachReconcilerSync
? So it is clear this flag is for the attach detach controller, and this is the sync subcomponent of the reconciler (not the whole reconciler). And ReconcilerSyncLoopPeriod
?
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
if time.Since(rc.timeOfLastSync) > rc.syncDuration { | ||
|
||
if rc.disableReconciliation { | ||
glog.V(5). Info("Not reconciling volumes as reconciliation is diabled via the command line flag") |
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 Skipping "attached volumes still attached" check since it is disabled via the command line
.
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.
Let me know how my change strikes you :)
if rc.disableReconciliation { | ||
glog.V(5). Info("Not reconciling volumes as reconciliation is diabled via the command line flag") | ||
} else if time.Since(rc.timeOfLastSync) > rc.syncDuration { | ||
glog.V(5).Info("Reconciling volumes") |
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 Starting "attached volumes still attached" check
.
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.
Let me know how my change strikes you :)
And I broke the build. Will fix on linux ... SGTM |
Review please @kris-nova |
// are still attached to the node and udpate the status if they are not. | ||
if time.Since(rc.timeOfLastSync) > rc.syncDuration { | ||
|
||
if rc.disableReconciliation { |
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.
We are not disable reconciliation. DisableAttachDetachReconcilerSync flag Saad suggested is only for disable rc.sync() below.
So rc. reconcile() should not be changed at all. Only change as below
if !rc. DisableAttachDetachReconcilerSync {
rc.Sync()
}
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 guess this might be the reason for the test failures.
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.
Fixed
@jingxu97 / @saad-ali I noticed that ebf796a#diff-2b533d4422a255f4bd8521394e285679 shows that we have openapi auto-generated. What is the magic command for that?? |
a5ea375
to
3aab5d2
Compare
// This flag enables or disables reconcile. Is false by default, and thus enabled. | ||
DisableReconciliation bool | ||
// ReconcilerSyncDuration is the amount of time the reconciler sync states loop | ||
// wait between successive executions. Is set to 5 min by default. |
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.
These names should make it clearer these options are related to volume attach/detach reconciliation
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.
@saad-ali made some recommendations
// Reconciler runs a periodic loop to reconcile the desired state of the with | ||
// the actual state of the world by triggering attach detach operations. | ||
// This flag enables or disables reconcile. Is false by default, and thus enabled. | ||
DisableReconciliation 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.
What are the side effects of disabling reconciliation? Is reconciliation the mechanism that updates mounted config file and secret volumes when they change in the API?
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.
@saad-ali care to comment?
|
||
// reconcilerSyncDuration is the amount of time the reconciler sync states loop | ||
// wait between successive executions | ||
reconcilerSyncDuration time.Duration = 5 * time.Second |
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.
Is this changing from 5 seconds to 5 minutes?
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.
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.
If reconciliation has varying cost for different volume types, is a single tuning interval across all types what we want?
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.
make reconcilerSyncDuration time very long might cause problem discussed in issue #33760 when state is out of sync. It explained the main reason we added sync loop here. Since this PR makes configurable, I think 1 min is good enough for most of the cases. This is a tradeoff between overhead and reducing the window of state out sync.
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.
What would you recommend @liggitt? We are planning to drop this in as an emergency release on Tuesday.
As I mentioned in #39526
TLDR;
Anyone that is using 1.4.6 or 1.4.7 in AWS will exceed their rate limits with as little as 20 PV attached to a cluster. We have one account that is at about 24k API calls per hour because of timeouts. This makes PV unusable on AWS.
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 Jordan, as a concerned lead I have no idea what the impacts or risks to this change are, and all I'm seeing is "might", "could", and "flake" on both sides of the fix / existing state.
Anything that needs to get cherry-picked that is important had better have a clear definition so people can understand them.
Please add that - removing the label until someone can summarize.
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.
Specifically, a comment was made:
this increases the change of mounting the wrong volume to the pod
which is incredibly terrifying.
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 wrong volume will be only mounted if:
- Volume is detached from pod, outside of k8s system (like AWS console)
- Node is rebooted.
#1 is not a huge concern because - usually we don't recommend users to detach volumes attached to nodes/pods.
#2 is bit of a problem and I am damned for saying this - but as long as time it takes for a reboot to complete is more than time specified here - we would be perhaps okay. But even original fix isn't a complete fix for #33760 as commented by @jingxu97
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.
Was that an "OR" or an "AND"? If it's an AND, that resolves my concern (because I agree 1 is PIBKAC). If it's an OR, then that's a really important thing to document, and very scary, and should be part of the flag documentation.
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.
It is an "OR". @gnufied lists two possible scenarios that the problem might happen.
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.
Comments
// Reconciler runs a periodic loop to reconcile the desired state of the with | ||
// the actual state of the world by triggering attach detach operations. | ||
// This flag enables or disables reconcile. Is false by default, and thus enabled. | ||
DisableReconciliation 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.
@saad-ali care to comment?
// This flag enables or disables reconcile. Is false by default, and thus enabled. | ||
DisableReconciliation bool | ||
// ReconcilerSyncDuration is the amount of time the reconciler sync states loop | ||
// wait between successive executions. Is set to 5 min by default. |
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.
@saad-ali made some recommendations
|
||
// reconcilerSyncDuration is the amount of time the reconciler sync states loop | ||
// wait between successive executions | ||
reconcilerSyncDuration time.Duration = 5 * time.Second |
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.
// are still attached to the node and udpate the status if they are not. | ||
if time.Since(rc.timeOfLastSync) > rc.syncDuration { | ||
|
||
if rc.disableReconciliation { |
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.
Fixed
@k8s-bot unit test this |
3aab5d2
to
620477e
Compare
reconciliation is main loop for controller to attach/detach volumes. It
checks the current state and desired state and determine whether to attach
or detach volumes. If it is disabled, attach/detach will not happen at all.
…On Fri, Jan 6, 2017 at 9:34 PM, Jordan Liggitt ***@***.***> wrote:
***@***.**** commented on this pull request.
------------------------------
In pkg/apis/componentconfig/types.go
<#39551 (review)>
:
> @@ -772,6 +773,14 @@ type KubeControllerManagerConfiguration struct {
// Zone is treated as unhealthy in nodeEvictionRate and secondaryNodeEvictionRate when at least
// unhealthyZoneThreshold (no less than 3) of Nodes in the zone are NotReady
UnhealthyZoneThreshold float32
+ // Reconciler runs a periodic loop to reconcile the desired state of the with
+ // the actual state of the world by triggering attach detach operations.
+ // This flag enables or disables reconcile. Is false by default, and thus enabled.
+ DisableReconciliation bool
What are the side effects of disabling reconciliation? Is reconciliation
the mechanism that updates mounted config file and secret volumes when they
change in the API?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#39551 (review)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ASSNxRB5Ta6aFICgmc1QQgOjEKoIXYoDks5rPyPZgaJpZM4LdMaG>
.
--
- Jing
|
@@ -80,6 +80,8 @@ func (s *CloudControllerManagerServer) AddFlags(fs *pflag.FlagSet) { | |||
fs.Float32Var(&s.KubeAPIQPS, "kube-api-qps", s.KubeAPIQPS, "QPS to use while talking with kubernetes apiserver") | |||
fs.Int32Var(&s.KubeAPIBurst, "kube-api-burst", s.KubeAPIBurst, "Burst to use while talking with kubernetes apiserver") | |||
fs.DurationVar(&s.ControllerStartInterval.Duration, "controller-start-interval", s.ControllerStartInterval.Duration, "Interval between starting controller managers.") | |||
fs.BoolVar(&s.DisableAttachDetachReconcilerSync, "disable-attach-detach-reconcile", false, "Disable volume attach detach reconcilation") | |||
fs.DurationVar(&s.ReconcilerSyncLoopPeriod, "reconcile-sync-loop-period", 5*time.Minute, "The wait time between volume attach detach reconciliation") |
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.
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 think you might set it up as line 47
NodeMonitorPeriod: metav1.Duration{Duration: 5 * time.Second},
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.
Yes, follow the patten of the existing vars. Pass the current value in as the default for the flag. Define the default you want in NewCloudControllerManagerServer
Review status: 0 of 8 files reviewed at latest revision, 10 unresolved discussions. pkg/controller/volume/attachdetach/attach_detach_controller.go, line 68 at r1 (raw file): Previously, chrislovecnm (Chris Love) wrote…
Updated PR with cobra comments. Comments from Reviewable |
Thanks! Review status: 0 of 8 files reviewed at latest revision, 10 unresolved discussions. Comments from Reviewable |
Review status: 0 of 8 files reviewed at latest revision, 10 unresolved discussions. pkg/apis/componentconfig/types.go, line 779 at r3 (raw file): Previously, chrislovecnm (Chris Love) wrote…
Jin responded to this. Comments from Reviewable |
@saad-ali I have a couple of other tweaks I will push in after this. Fixing times on two tests, and removing dead code in reconciler. I am letting e2e run now, but will be in shortly. |
Ack. |
and the option to shut off reconciliation.
df5eb50
to
a973c38
Compare
@saad-ali last e2e was successful, now waiting on this one to run. The release notes are up to date now, and the changes that were requested are in. |
Cool, I'll take another look |
Jenkins unit/integration failed for commit a973c38. Full PR test history. The magic incantation to run this job again is Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
@@ -408,6 +408,10 @@ func StartControllers(controllers map[string]InitFunc, s *options.CMServer, root | |||
go volumeController.Run(stop) | |||
time.Sleep(wait.Jitter(s.ControllerStartInterval.Duration, ControllerStartJitter)) | |||
|
|||
if s.ReconcilerSyncLoopPeriod.Duration < time.Second { | |||
return fmt.Errorf("Duration time must be greater than one second as set via command line option reconcile-sync-loop-period. One minute is recommended.") |
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.
Remove the recommendation part.
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
@@ -181,6 +182,8 @@ func (s *CMServer) AddFlags(fs *pflag.FlagSet) { | |||
fs.Float32Var(&s.SecondaryNodeEvictionRate, "secondary-node-eviction-rate", 0.01, "Number of nodes per second on which pods are deleted in case of node failure when a zone is unhealthy (see --unhealthy-zone-threshold for definition of healthy/unhealthy). Zone refers to entire cluster in non-multizone clusters. This value is implicitly overridden to 0 if the cluster size is smaller than --large-cluster-size-threshold.") | |||
fs.Int32Var(&s.LargeClusterSizeThreshold, "large-cluster-size-threshold", 50, "Number of nodes from which NodeController treats the cluster as large for the eviction logic purposes. --secondary-node-eviction-rate is implicitly overridden to 0 for clusters this size or smaller.") | |||
fs.Float32Var(&s.UnhealthyZoneThreshold, "unhealthy-zone-threshold", 0.55, "Fraction of Nodes in a zone which needs to be not Ready (minimum 3) for zone to be treated as unhealthy. ") | |||
fs.BoolVar(&s.DisableAttachDetachReconcilerSync, "disable-attach-detach-reconcile", false, "Disable volume attach detach reconciler sync. Disabling this may cause volumes to be mismatched with pods. Use wisely.") |
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.
disable-attach-detach-reconcile
-> disable-attach-detach-reconcile-sync
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
@@ -181,6 +182,8 @@ func (s *CMServer) AddFlags(fs *pflag.FlagSet) { | |||
fs.Float32Var(&s.SecondaryNodeEvictionRate, "secondary-node-eviction-rate", 0.01, "Number of nodes per second on which pods are deleted in case of node failure when a zone is unhealthy (see --unhealthy-zone-threshold for definition of healthy/unhealthy). Zone refers to entire cluster in non-multizone clusters. This value is implicitly overridden to 0 if the cluster size is smaller than --large-cluster-size-threshold.") | |||
fs.Int32Var(&s.LargeClusterSizeThreshold, "large-cluster-size-threshold", 50, "Number of nodes from which NodeController treats the cluster as large for the eviction logic purposes. --secondary-node-eviction-rate is implicitly overridden to 0 for clusters this size or smaller.") | |||
fs.Float32Var(&s.UnhealthyZoneThreshold, "unhealthy-zone-threshold", 0.55, "Fraction of Nodes in a zone which needs to be not Ready (minimum 3) for zone to be treated as unhealthy. ") | |||
fs.BoolVar(&s.DisableAttachDetachReconcilerSync, "disable-attach-detach-reconcile", false, "Disable volume attach detach reconciler sync. Disabling this may cause volumes to be mismatched with pods. Use wisely.") | |||
fs.DurationVar(&s.ReconcilerSyncLoopPeriod.Duration, "attach-detach-reconcile-period", s.ReconcilerSyncLoopPeriod.Duration, "The reconciler sync wait time between volume attach detach. This duration must be larger than one second, and increasing this value from the default my allow for volume mismatches.") |
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.
attach-detach-reconcile-period
-> attach-detach-reconcile-sync-period
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.
default my allow for volume
-> default my increase the likelihood of volume
?
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.
typo fixing
@@ -635,3 +635,5 @@ garbage-collector-enabled | |||
viper-config | |||
log-lines-total | |||
run-duration | |||
disable-attach-detach-reconcile | |||
attach-detach-reconcile-period |
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.
Remember to update these after rename above.
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
// This flag enables or disables reconcile. Is false by default, and thus enabled. | ||
DisableAttachDetachReconcilerSync bool | ||
// ReconcilerSyncLoopPeriod is the amount of time the reconciler sync states loop | ||
// wait between successive executions. Is set to 5 min by default. |
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.
5 min
-> 5 sec
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
@@ -57,6 +57,7 @@ func NewReconciler( | |||
loopPeriod time.Duration, | |||
maxWaitForUnmountDuration time.Duration, | |||
syncDuration time.Duration, | |||
disableReconciliation 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.
disableReconciliation
->disableReconcilerSync
?
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.
Ditto for attach_detach_controller.go
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, and renamed a couple stragglers.
https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/pr-logs/pull/39551/pull-kubernetes-unit/12293/ <- same open API stuff that was failing over the weekend. No idea what is up |
Jenkins Bazel Build failed for commit ac49139. Full PR test history. The magic incantation to run this job again is Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
Failing UT issue looks like #39604 which is a marked a flake, so it should pass if we run it often enough. |
@k8s-bot bazel test this |
/lgtm |
Marking P0 to get merged ASAP for tomorrow's release. |
Automatic merge from submit-queue (batch tested with PRs 39628, 39551, 38746, 38352, 39607) |
Chris this is merged. Can you please prepare the cherry pick to 1.5 and once that is complete we can do the 1.4 cherry pick |
…51-upstream-release-1.4 Automated cherry pick of #39551 upstream release 1.4
#What this PR does / why we need it:
We are currently blocked by API timeouts with PV volumes. See #39526. This is a workaround, not a fix.
Special notes for your reviewer:
A second PR will be dropped with CLI cobra options in it, but we are starting with increasing the reconciliation periods. I am dropping this without major testing and will test on our AWS account. Will be marked WIP until I run smoke tests.
Release note: