Bug 1826073 - Rate limiting on Azure
Summary: Rate limiting on Azure
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Cloud Compute
Version: 4.3.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 4.3.z
Assignee: Alberto
QA Contact: Milind Yadav
URL:
Whiteboard:
Depends On: 1826069
Blocks: 1810446
TreeView+ depends on / blocked
 
Reported: 2020-04-20 19:47 UTC by Daneyon Hansen
Modified: 2023-09-07 22:53 UTC (History)
12 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1826069
Environment:
Last Closed: 2020-06-23 20:58:40 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift installer pull 3714 0 None closed [release-4.3] BUG 1826073: Disable client side rate limiting in Azure. 2020-12-28 06:26:17 UTC
Red Hat Knowledge Base (Solution) 4861541 0 None None None 2020-05-19 07:51:51 UTC
Red Hat Product Errata RHBA-2020:2585 0 None None None 2020-06-23 20:58:57 UTC

Comment 1 Michael Gugino 2020-05-19 02:47:50 UTC
It should be noted that while the code has merged in master, this will only affect new installs as far as I can tell.  Anyone that has already installed a cluster will have to make these changes manually unless this config is adopted by one operator or another.

Comment 2 Pedro Amoedo 2020-05-19 07:51:51 UTC
ACK Michael, for those post-installation cases we already have this KCS[1] in place.

[1] - https://access.redhat.com/solutions/4861541

Best Regards.

Comment 5 Milind Yadav 2020-06-15 11:08:35 UTC
VALIDATED on -
[miyadav@miyadav ~]$ oc get clusterversion
NAME      VERSION                             AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.3.0-0.nightly-2020-06-14-170647   True        False         6m15s   Cluster version is 4.3.0-0.nightly-2020-06-14-170647
[miyadav@miyadav ~]$ 


The cloudproviderRatelimit is set to false with the new installation as desired :
[miyadav@miyadav ~]$ oc get configmaps cloud-provider-config -n openshift-config -o yaml
apiVersion: v1
data:
  config: "{\n\t\"cloud\": \"AzurePublicCloud\",\n\t\"tenantId\": \"6047c7e9-b2ad-488d-a54e-dc3f6be6a7ee\",\n\t\"aadClientId\":
    \"\",\n\t\"aadClientSecret\": \"\",\n\t\"aadClientCertPath\": \"\",\n\t\"aadClientCertPassword\":
    \"\",\n\t\"useManagedIdentityExtension\": true,\n\t\"userAssignedIdentityID\":
    \"\",\n\t\"subscriptionId\": \"53b8f551-f0fc-4bea-8cba-6d1fefd54c8a\",\n\t\"resourceGroup\":
    \"miyadav-0615-8kz4v-rg\",\n\t\"location\": \"westus2\",\n\t\"vnetName\": \"miyadav-0615-8kz4v-vnet\",\n\t\"vnetResourceGroup\":
    \"miyadav-0615-8kz4v-rg\",\n\t\"subnetName\": \"miyadav-0615-8kz4v-worker-subnet\",\n\t\"securityGroupName\":
    \"miyadav-0615-8kz4v-node-nsg\",\n\t\"routeTableName\": \"miyadav-0615-8kz4v-node-routetable\",\n\t\"primaryAvailabilitySetName\":
    \"\",\n\t\"vmType\": \"\",\n\t\"primaryScaleSetName\": \"\",\n\t\"cloudProviderBackoff\":
    true,\n\t\"cloudProviderBackoffRetries\": 0,\n\t\"cloudProviderBackoffExponent\":
    0,\n\t\"cloudProviderBackoffDuration\": 6,\n\t\"cloudProviderBackoffJitter\":
    0,\n\t\"cloudProviderRateLimit\": false,\n\t\"cloudProviderRateLimitQPS\": 0,\n\t\"cloudProviderRateLimitBucket\":
    0,\n\t\"cloudProviderRateLimitQPSWrite\": 0,\n\t\"cloudProviderRateLimitBucketWrite\":
    0,\n\t\"useInstanceMetadata\": true,\n\t\"loadBalancerSku\": \"standard\",\n\t\"excludeMasterFromStandardLB\":
    null,\n\t\"disableOutboundSNAT\": null,\n\t\"maximumLoadBalancerRuleCount\": 0\n}\n"
kind: ConfigMap
metadata:
  creationTimestamp: "2020-06-15T09:52:05Z"
  name: cloud-provider-config
  namespace: openshift-config
  resourceVersion: "884"
  selfLink: /api/v1/namespaces/openshift-config/configmaps/cloud-provider-config
  uid: df0ec0aa-5b76-4915-866c-93a748a71f84

Additional Info:
Moved to VERIFIED.

Comment 7 errata-xmlrpc 2020-06-23 20:58:40 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2020:2585


Note You need to log in before you can comment on or make changes to this bug.