TCA Workload cluster whereabouts allocates duplicate IP

Products

• VMware Telco Cloud Infrastructure

Issue/Introduction

• Duplicate IP is being observed in the pods
• Deleting of pods is not assigning new IPs, again same IP or duplicate IP gets allocated.
• This is not an issue from TCA 3.2 version, the issue is with the whereabouts version less than 0.9 has a problem allocating duplicate IP's to pods.
  • Whereabouts assign duplicate IP

Environment

TCA 3.x

Cause

• In whereabouts version less than 0.9, issue causing duplicate IP address assignments in Kubernetes

Resolution

• Upgrading to Whereabouts 0.9.0 or later is recommended to benefit from improved IP address management and concurrency fixes.
• We have script to detect and clean up duplicate IP address in the cluster, kindly refer Whereabouts duplicate IP detect and cleanup script
• Resolved in TCA 3.3.0.1
• To assist installing whereabouts 0.9.0 in TCA prior to 3.3.0.1 version, we request to raise a ticket with Broadcom support to get some assistance.

Additional Information

• Patching whereabouts package will initiate the rollout update of whereabouts Pods.

  • If Kubernetes (k8s) is < 1.27:

    • Adopt TCP 5.0.2 otherwise the whereabouts 0.9.0 patch won’t be persistent following a TKG upgrade.

  • If Kubernetes (k8s) is >= 1.27:

    • First, apply the whereabouts 0.9.0 patch, then adopt TCP 5.1.1 (5.1 is also usable, but 5.1.1 is preferred). The whereabouts 0.9.0 patch will be persistent following a TKG upgrade.

•  What does `patch upload` do?
  • It will upload the bundle and container images to the Airgap server.
• What does `patch check` do?
  • It will check the apply status of the patch.
• What does `kb apply` do?
  1. Create a v0.9.0 whereabout Package on the workload cluster
  2. Update the version in PackageInstall to v0.9.0 to upgrade whereabouts.
  3. If whereabout isn’t installed, it will do nothing.

Note: Both 5.0.2 and 5.1.1 (or 5.1) ensure whereabouts 0.9.0 persists throughout the k8s lifecycle. If customer foreseen upgrade of k8s in the same TCP release Broadcom recommend to adopt 5.0.2 and 5.1.1 instead of apply patch multiple times