Loading

×Sorry to interrupt
This page has an error. You might just need to refresh it.
[NoErrorObjectAvailable] Uncaught ReferenceError: addCTracking is not defined
Failing descriptor: {markup://c:KM_ArticleThemeLayout}

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

K8S service creation stuck with waiting for service IP with error "Exceed maximum number of pools on the Load balancer service" (71372)

Last Updated: 8/23/2019Categories: TroubleshootingTotal Views: 11738Language:
Chinese (Simplified)JapaneseEnglish

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

When you create a K8S service, its pending at waiting for service IP.

In the ncp logs, you see that server pool limit is exhausted on the cluster load balancer.

In the /var/vcap/sys/log/ncp/ncp.stdout.log on master node, you see the entries similar to:
response body {u'error_code': 23500, u'related_errors': [{u'error_code': 23704, u'error_message': u'Exceed maximum number of pools on the Load balancer service. The maximum size of pools for SMALL load balancerservice form factor is 20, current size of pools is 21.
1 2019-08-08T14:23:03.213Z 543c4597-5883-4078-94f8-b9c69fd144e6 NSX 17660 - [nsx@6876 comp="nsx-container-ncp" subcomp="ncp" level="ERROR" errorCode="NCP00050"] nsx_ujo.ncp.nsx.manager.base_k8s_nsxapi Failed to UPDATE virtual server

When you check the LB server pool count from edge vm, you see that pool limit is already reached.
get load-balancer <load-balancer-ID> pools

Cause

This issue occurs when the server pool limit is exhausted on the PKS cluster load balancer. In VMware NSX-T 2.3.1 supports only 20 server pools per small load balancer. For more information, see Scaling Load Balancer Resources section in VMware NSX-T 2.3.1 Documentation .

Auto scaling for PKS cluster LB was introduced in NCP and it creates a new load balancer if the current LB reaches the Virtual Server (VS) limit, however we don’t have any auto scaling if the server pool count reaches the limit.

Resolution

To resolve this issue, upgrade to VMware NSX-T 2.4 to increase the Small LB server pool limit to 60.

For more information, see Scaling Load Balancer Resources section in VMware NSX-T 2.4 Documentation .

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

Additional Resources

KB
•
vApp テンプレートから vApp をデプロイすると、「ハブの「リソース」が仮想マシンのホスト アフィニティ ルールに違反しています (Hub "Resources" violates VM host affinity rule)」というエラーが表示される (71366)

KB
•
将磁盘添加到 vCloud Director for Service Providers 中的虚拟机时出现错误“未设置 StoragePlacementSpec 所需属性 podSelectionSpec” (71365)

KB
•
对文件 /opt/vmware/vcloud-director/data/transfer 解压存档失败：cpio：chown (71340)

KB
•
Customer Purchasing Program FAQ - オンライン ツールと移行 (71388)

KB
•
尝试通过 api 删除计算机前缀时出现错误“400 错误请求 (400 bad request)” (71344)

Results 1-5 of 5

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware PKS

Related Versions:

VMware PKS 1.x

VMware NSX-T Data Center 2.x

VMware NSX-T Data Center

Take Our Survey

Support Assistant