Overview
To ensure safe, timely delivery of features, Tulip mandates that customers who opt-in to hosting their own Connector Host (OPCH) keep that connector host updated. Starting from r336, this banner would only be visible for OPCH that has been utilized in the last 3 months.
What OPCH version is right for you?
| LTS Version | Supported OPCH Versions |
|---|---|
| LTS12.x | LTS12.x |
| LTS13.x | LTS13.x |
| LTS14.x | LTS14.x , LTS13.x - with warning banner |
The OPCH version cannot be newer than the version of the Tulip platform your instance is running. For example, if your instance is running LTS 14.5 and you are using the On-Premise Connector Host, do not install an OPCH later than LTS 14.5.
Best practice is to keep your OPCH on the same version as your instance, but you are not forced to adopt the point releases for OPCH (i.e. an LTS 14.5 instance can use the following OPCH versions: LTS 14.5, LTS 14.4, LTS 14.3, LTS 14.2, LTS 14.1, etc...)
| Standard Release Version | Supported OPCH Versions |
|---|---|
| r275-r287 | LTS12.x |
| r288-r311 | LTS13.x |
| r312-r316 (grace period) | LTS13.x - with warning banner, LTS14 |
| r317-r320 (grace period) | LTS13.x - with warning banner, LTS14.x |
| r321+ | LTS14.x |
LTS Customers
Tulip supports a single major OPCH version per LTS release. This version is supported as long as the LTS release is supported. Please refer to your LTS Terms of Service for more information on the LTS release support timeline. As part of the LTS upgrade process, customers must also upgrade their OPCH.
Customers are granted a 1 LTS version grace period to upgrade all OPCH. During this grace period warnings will be shown throughout the product, indicating that an OPCH must be updated.
Example:
| Tulip Version | Connector Host Version | State |
|---|---|---|
| LTS14 | LTS14 | Connector host fully supported |
| LTS14 | LTS13 | Grace period - warnings shown in product indicating that an update is needed. |
| LTS14 | LTS12 | Connector host will not connect to Tulip |
During a major LTS upgrade, or shortly after upgrade, customers must ensure all active OPCHs are also upgraded. This process takes just a few minutes, and more information on the upgrade process can be found here. Changes to the OPCH are included in all Tulip validation documentation for the relevant LTS version.
LTS point releases (like LTS11.2, for example) will always have an associated OPCH version, but customers are not mandated to upgrade OPCH during minor upgrades. OPCH version names will always align with the LTS version names, including point releases.
Standard Release Customers
The On-Premise Connector Host is released every 6 months. For customers on standard releases, a 4-release/week grace period will be given to upgrade each OPCH before its compatibility with the cloud is not guaranteed.
When a new version of OPCH is made available, banners will be displayed on impacted connector hosts to indicate that they should be updated.
Upgrading an OPCH takes just a few minutes, and more information on the upgrade process can be found here.
Further Reading
Did you find what you were looking for?
You can also head to community.tulip.co to post your question or see if others have faced a similar query!