TKGI: Expected behavior if a running TKGI release version reaches End Of Life / End Of Support (EOL/EOS)
Article ID: 375604
Updated On:
Products
Issue/Introduction
This article provides information for a TKGI Operator, should the TKGI running release version reach End Of Life / End Of Support (EOS/EOL).
This article provides helpful information for a TKGI Operator to assist them in their planning and expectations.
Environment
VMware Tanzu Kubernetes Grid Integrated Edition (TKGI)
VMware NSX (Formerly referred to as VMware NSX-T Data Center)
VMware Tanzu Operations Manager
VMware Tanzu Kubernetes Integrated Edition Management Console
NOTE: If you are running NSX-T with TKGI, in earlier TKGI license contracts, NSX-T support was included under the single TKGI license.
However, it was also required that the running release version of NSX-T also complies with both the Lifecycle Policy for the NSX-T version running.
In more-recent TKGI foundations, the TKGI license contract does not include support for NSX-T instance in use by the TKGI foundation.
Therefore, an additional VMware NSX license is needed.
Refer to the details of your individual licenses to determine which applies to you.
Resolution
Any existing existing TKGI/NSX-T environments feature sets will remain to work even if a license expiration date is reached.
For example:
Existing containers will remain active and online
Existing deployments will be able to be updated
New Deployments will be able to be created.
Existing TKGI Clusters will remain active and Online
Existing TKGI clusters will be able to be upgraded
Clusters can still be created and deleted.
However, you will be unable to obtain technical support via a Tanzu technical Support Request case. If you still have a valid Support Maintenance contract, the Self Service Support portal is still available to operators.
Refer to the Product Lifecycle page for confirmation of End Or Life / End Of Support dates.
Feedback
