Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

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

Tuning NCP parameters for increased PKS Scaling in VMware Enterprise PKS environment (68085)

Last Updated: 7/13/2019Categories: InformationalTotal Views: 3489Language:
English

1 like this article

Subscribe to get an email
newsletter with new updates

1 people found this helpful Please provide article feedback:

Purpose

This article helps you to tune the limits of existing and new clusters when there are scale related issues that manifest into NSX-T Manager being overwhelmed with the number of active NCP instances which is directly proportional to the number of K8s clusters being managed by a single NSX-T instance. The purpose of this article is to document how to use this new capability to update the NCP parameters but not to suggest a value or a range. Any values that need to be set need to be based on engineering approval (NCP and NSX-T team) and would vary by customer’s scale and environment.

Starting from VMware Enterprise PKS 1.4.1, you can manually tune NCP heart beat and rate limits parameters to help scale your PKS deployments. Note that these changes are applicable to NCP 2.4.x only. The following parameters that are part of the NCP.ini file are tunable:

master_timeout

heartbeat_period

update_timeout

In NCP 2.4.1, the recommended values for above parameters are:

master_timeout = 18

heartbeat_period = 6

update_timeout = master_timeout – heartbeart_period = 12

The description for each of these parameters is available under Configmap for ncp.ini in ncp-rc.yml section in the NSX Container Plug-in for Kubernetes and Cloud Foundry Documentation.This documentation lists all parameters in the ncp.ini file, however only the above 3 are configurable with PKS v1.4.1.

Resolution

To perform the updates, we use the Ops Manager CLI. For more information, see updating a simple property section under Opsmanager api documentation .

Instructions to update these parameters in the PKS Tile:

Get the PKS product GUID using the Ops Manager CLI:
# om -k -t <opsman_IP> -u <opsman_username> -p "<opsman_password>" curl -s -p '/api/v0/staged/products' | jq -cr '.[] | select( .type=="pivotal-container-service" ) | .guid'
Sample Output: pivotal-container-service-0d2397b6f4b0ca35be13

Export it as PKS_GUID:
export PKS_GUID=pivotal-container-service-0d2397b6f4b0ca35be13

Or

export PKS_GUID=$(om -k -t <opsman_IP> -u <opsman_username> -p "<opsman_password>" curl -s -p '/api/v0/staged/products' | jq -cr '.[] | select( .type=="pivotal-container-service" ) | .guid')

Update the property values for below parameters:
".properties.network_selector.nsx.ncp-ha-master-timeout"
".properties.network_selector.nsx.ncp-ha-heartbeat-period"
".properties.network_selector.nsx.ncp-ha-update-timeout"

For example, the following commands will update them to 18, 6, 12.

om -k -t <opsman_IP> -u <opsman_username> -p '<opsman_password>' curl -x PUT -p "/api/v0/staged/products/${PKS_GUID}/properties" -d '{ "properties": { ".properties.network_selector.nsx.ncp-ha-master-timeout": { "value": 18}, ".properties.network_selector.nsx.ncp-ha-heartbeat-period": { "value": 6}, ".properties.network_selector.nsx.ncp-ha-update-timeout": { "value": 12} }}'

After this change, you need to Apply-Changes on the PKS tile to make it take effect:

New clusters will be deployed with the new values.

If upgrade-all-instances errand is enabled, all existing clusters will be updated to new values during apply-changes.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
Actualización de Windows vCenter Server de 5,5 a 6,0 con instancia de PSC integrada (2109559)

KB
•
オンプレミスの vCloud Availability 3.0 用の vSphere Client プラグインを使用すると、vCloud Director の userPrincipleName LDAP 認証情報を指定できない (68100)

Results 1-2 of 2

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

Take Our Survey

Support Assistant