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

IP addresses of Kubernetes load balancer deployed with static IP (loadBalancerIP) are not marked as allocated in NSX-T IP pools (77006)

Last Updated: 1/31/2020Categories: TroubleshootingTotal Views: 7422Language:
Chinese (Simplified)JapaneseEnglish

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

Kubernetes load balancers are deployed with static IP using the loadBalancerIP setting.

Example of yaml file:
apiVersion: v1
kind: Service
metadata:
labels:
app.kubernetes.io/name: ingress-nginx
app.kubernetes.io/part-of: ingress-nginx
name: ingress-nginx
namespace: ingress-nginx
spec:
loadBalancerIP: 10.10.10.42
ports:
- name: http
port: 80
protocol: TCP
targetPort: http
- name: https
port: 443
protocol: TCP
targetPort: https
selector:
app.kubernetes.io/name: ingress-nginx
app.kubernetes.io/part-of: ingress-nginx
type: LoadBalancer

The IP address assigned to the load balancer is part of the namespace NSX-T IP pool and the IP is not marked as allocated in the NSX-T IP pool

NCP version in used at the time the load balancer is deployed is pre-NCP 2.5.1.

Cause

Pre-NCP 2.5.1, NCP did not track the allocation of static load balancer IP addresses. As a result, NCP may allocate the IP address to a different services causing IP conflicts.

Resolution

This issue is resolved in NCP 2.5.1.
Note: if IP conflicts already exist (i.e. the load balancer IP as been associated for a different service pre-NCP 2.5.1) refer to the Workaround section below.

Workaround

Upgrading to NCP 2.5.1 does not fix the issue if IP conflicts already exist (i.e. the load balancer IP as been associated for a different service pre-NCP 2.5.1).
As a workaround, manual operation is required to clear the IP conflicts and you need to either:

Release the IP from other services.

Change the load balancer IP (loadbalancerIP) to a free IP.

As a workaround, if upgrading to NCP 2.5.1 is not an option, you can manually allocate the load balancer IP addresses in the NSX-T IP pool to ensure they are not assigned for any other services:

1. Find the IP pool id using REST API:
GET /api/v1/pools/ip-pools
Example of output:
{
"results" : [ {
"pool_usage" : {
"total_ids" : 248,
"allocated_ids" : 1,
"free_ids" : 247
},
"subnets" : [ {
"cidr" : "169.254.17.0/24",
"dns_nameservers" : [ ],
"allocation_ranges" : [ {
"start" : "169.254.17.3",
"end" : "169.254.17.250"
} ]
} ],
"resource_type" : "IpPool",
"id" : "b8638189-81ad-44d0-8747-f2c4e8843bd5", <<---- IP Pool id
"display_name" : "SI_Destination_IP_Pool",
"description" : "ServiceInsertion_IP_Pool_for_NS_insertion_at_T0/T1",
"_create_user" : "system",
"_create_time" : 1579798571269,
"_last_modified_user" : "system",
"_last_modified_time" : 1579798571269,
"_system_owned" : true,
"_protection" : "NOT_PROTECTED",
"_revision" : 0
}

2. Mark the IP address as allocated in the IP pool using REST API:
POST /api/v1/pools/ip-pools/{IP_POOL_ID}?action=ALLOCATE
Body:
{
"allocation_id":"{IP_ADDRESS}"
}

3. Verify the allocation using REST API:
GET /api/v1/pools/ip-pools/{IP_POOL_ID}/allocations

Note: if you delete the Kubernetes load balancer, the manual allocations above would need to be manually deleted using the following REST API:
POST /api/v1/pools/ip-pools/{IP_POOL_ID}?action=RELEASE
Body:
{
"allocation_id":"{IP_ADDRESS}"
}

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

KB
•
新しいライブ フロー監視セッションの作成に失敗する (70762)

KB
•
ESXi 主机上保留的容器筛选器过期 (70750)

KB
•
Download and Install VMware Fusion (2014097)

KB
•
展開後に NSX Edge の [説明] フィールドを編集できない (78024)

Results 1-5 of 5

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

Related Versions:

VMware NSX-T Data Center 2.x

VMware NSX-T Data Center

Take Our Survey

Support Assistant