Tyk Cloud & Governance Portal Auto Upgrade FAQS

Q: Is this a new feature?

A: Yes - it is live within the product now though.

Q: When are these emails triggered?

A: In Tyk Cloud, customers can enable the Auto Upgrade function. When enabled:

• If a new Long-Term Support (LTS) version is released and the customer is still on an older LTS version, their deployment is automatically upgraded.

• If we release a version addressing security vulnerabilities or other urgent fixes, we can upgrade them automatically to ensure stability and safety.

   

Q: Does this include hybrid deployments? How does this impact the dashboard–control plane sync? Are the Gateway and Dashboard expected to be upgraded in sync?

A: Hybrid deployments and deployments with plugins enabled are excluded from Auto Upgrade — customers can’t have it enabled. Yes, dashboard updates first, and then the gateway gets updated.

Q: Can customers choose which deployments get Auto Upgrade? Or is it applied to all deployments/environments?

A: Yes. Auto Upgrade is opt-in, enabled on a per control plane basis. Enabling it for a control plane also upgrades its related data planes.

Q: How often do Auto Upgrades occur?

A: They occur whenever a new LTS version of the Gateway or Dashboard for Tyk Cloud is released — the timing of the actual Auto Upgrade depends on how a customer configures it

Q: Do we have a list of customers who have Auto Upgrade enabled? If yes, can we share?

A: Not readily available, but can be fetched on an ad-hoc by SRE. 

Q: How do Tyk and the customer know the upgrade was successful?

A: Alerts notify SREs about Auto Upgrade failures. Customers can check deployment status in the dashboard, similar to a manual upgrade. Failures are unlikely to impact traffic because Kubernetes usually keeps the previous version running.

Q: What happens if the upgrade fails?

A: On-call SREs are alerted.

Q: How do we ensure notifications go to the correct organisation admin?

A: Org admin details are configured in the product and can be updated by the customer at any time. It is also the responsibility of the customer to update this. 

Q: What if the org admin is not in HubSpot?

A: When a new Cloud user is created, their details are automatically added to HubSpot.

Q: Can someone be an org admin for multiple deployments?

A: Yes. An organization can have multiple deployments, and one admin may cover them. Auto Upgrade emails are sent per control plane, not per deployment.

Q: Is product data logged at the Contact or Account level in HubSpot?

A: No. We send emails using templates filled with live details.

Q: Is there a failsafe for duplicate HubSpot contacts?

A: Yes. HubSpot prevents duplicate emails from being added.

Q: Is there documentation we can link to?

A: Yes — see Auto Upgrade documentation here. 

Q: Do we want to inform customers that this feature has been added, and/or warn them when an LTS upgrade is coming?

A: Yes, this is something we are actively working on but will communicate it in the meantime. As a precaution Account Managers should actively engage with their Cloud customers notifying them of this feature.