| VMware NSX Container Plugin 4.1.2.1 | 27 February 2024 | Build 23305119 Check for additions and updates to these release notes. |
What's New
NSX Container Plugin 4.1.2.1 is an update release that resolves issues found in earlier releases. For other details about this release, see the NSX Container Plugin 4.1.2 Release Notes.
Compatibility Requirements
| Product |
Version |
| NCP/NSX Tile for Tanzu Application Service (TAS) |
4.1.2.1 |
| NSX |
3.2.3, 4.0.1, 4.1.1, 4.1.2.1 |
| Kubernetes |
1.26, 1.27, 1.28 |
| OpenShift 4 |
4.12, 4.13, 4.14 |
| Kubernetes Host VM OS |
Ubuntu 20.04 Ubuntu 22.04 with kernel 5.15 (both nsx-ovs kernel module and upstream OVS kernel module supported) Ubuntu 22.04 with kernel later than 5.15 (only upstream OVS kernel module supported) RHEL 8.8, 8.9 See notes below. |
| Tanzu Application Service (TAS) |
Ops Manager 2.10 + TAS 2.13 Ops Manager 3.0 + TAS 2.13 Ops Manager 2.10 + TAS 4.0 Ops Manager 3.0 + TAS 4.0 Ops Manager 2.10 + TAS 5.0 Ops Manager 3.0 + TAS 5.0 |
| Tanzu Kubernetes Grid Integrated (TKGI) |
1.18.2 |
Notes:
For all supported integrations, use the Red Hat Universal Base Image (UBI). For more information, https://www.redhat.com/en/blog/introducing-red-hat-universal-base-image.
Support for upgrading to this release:
-
4.1.0. 4.1.1, and all 4.0.x releases.
Resolved Issues
-
Issue 3292003: In an OCP environment, node goes down after applying taint with NoExecute effect
In an OCP environment, if you remove {"effect":"NoExecute", "operator":"Exists"} toleration for the node agent DaemonSet, and add a NoExecute effect taint on a node, for example, test=abc:NoExecute, the node may go down. In this scenario, the node agent pod will be evicted from the node with taint. During node agent pod eviction, it is possible that the node will lose connectivity because the node agent pod does not exit gracefully and the node uplink interface is not configured correctly from br-int back to ens192.
Workaround: Reboot the node VM from vCenter Server.
