From 5479e02f4ae728d7e0bf7243d3f29205955cd92e Mon Sep 17 00:00:00 2001 From: Catherine Luse Date: Wed, 21 Apr 2021 23:46:07 -0700 Subject: [PATCH 1/2] Document refresh setting change in v2.5.8 #3133 --- .../hosted-kubernetes-clusters/eks/_index.md | 25 ++++++++++++++++++- 1 file changed, 24 insertions(+), 1 deletion(-) diff --git a/content/rancher/v2.5/en/cluster-provisioning/hosted-kubernetes-clusters/eks/_index.md b/content/rancher/v2.5/en/cluster-provisioning/hosted-kubernetes-clusters/eks/_index.md index 92fab1a1bce..7870edf4f0b 100644 --- a/content/rancher/v2.5/en/cluster-provisioning/hosted-kubernetes-clusters/eks/_index.md +++ b/content/rancher/v2.5/en/cluster-provisioning/hosted-kubernetes-clusters/eks/_index.md @@ -738,4 +738,27 @@ If Rancher and another source attempt to update an EKS cluster at the same time ### Configuring the Refresh Interval -It is possible to change the refresh interval through the setting “eks-refresh-cron". This setting accepts values in the Cron format. The default is `*/5 * * * *`. The shorter the refresh window is the less likely any race conditions will occur, but it does increase the likelihood of encountering request limits that may be in place for AWS APIs. +{{% tabs %}} +{{% tab "Rancher v2.5.8+" %}} + +The `eks-refresh-cron` setting is deprecated. It has been migrated to the `eks-refresh` setting, which is an integer in seconds. + +The default value is 300 seconds. + +The syncing interval can be changed by running `kubectl edit setting eks-refresh`. + +If the `eks-refresh-cron` setting was previously set, the migration will happen automatically. + +The shorter the refresh window, the less likely any race conditions will occur, but it does increase the likelihood of encountering request limits that may be in place for AWS APIs. + +{{% /tab %}} +{{% tab "Before v2.5.8" %}} + +It is possible to change the refresh interval through the setting `eks-refresh-cron`. This setting accepts values in the Cron format. The default is `*/5 * * * *`. + +The shorter the refresh window, the less likely any race conditions will occur, but it does increase the likelihood of encountering request limits that may be in place for AWS APIs. + +{{% /tab %}} +{{% /tabs %}} + + From b1b30e38787b07fcdfd3c86bc127cf73a1d7005d Mon Sep 17 00:00:00 2001 From: Catherine Luse Date: Fri, 23 Apr 2021 12:27:40 -0700 Subject: [PATCH 2/2] Update content/rancher/v2.5/en/cluster-provisioning/hosted-kubernetes-clusters/eks/_index.md Co-authored-by: Caleb Bron --- .../hosted-kubernetes-clusters/eks/_index.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/content/rancher/v2.5/en/cluster-provisioning/hosted-kubernetes-clusters/eks/_index.md b/content/rancher/v2.5/en/cluster-provisioning/hosted-kubernetes-clusters/eks/_index.md index 7870edf4f0b..c496ab47643 100644 --- a/content/rancher/v2.5/en/cluster-provisioning/hosted-kubernetes-clusters/eks/_index.md +++ b/content/rancher/v2.5/en/cluster-provisioning/hosted-kubernetes-clusters/eks/_index.md @@ -741,7 +741,7 @@ If Rancher and another source attempt to update an EKS cluster at the same time {{% tabs %}} {{% tab "Rancher v2.5.8+" %}} -The `eks-refresh-cron` setting is deprecated. It has been migrated to the `eks-refresh` setting, which is an integer in seconds. +The `eks-refresh-cron` setting is deprecated. It has been migrated to the `eks-refresh` setting, which is an integer representing seconds. The default value is 300 seconds. @@ -761,4 +761,3 @@ The shorter the refresh window, the less likely any race conditions will occur, {{% /tab %}} {{% /tabs %}} -