Happy Business Starts Here

Zuora Staff

We will be performing a maintenance on our Connect service on November 14th from 5pm until 6pm Pacific. During this time, there may be brief service interruption. This work is to upgrade to new infrastructure and service management of the Connect environment.

4 Comments
Scholar

 

What is the nature of the maintenance that there *may* be a service disruption? This being a production service, I'd expect maintenance to occur in a way that guarantees against disruption. Do we need to plan for failing service calls?

Zuora Staff

@tisubs

 

We are moving Connect into the same Kubernetes cluster that support all apps. This is being done to ensure consistent behavior and scalability across the entire platform. We do not expect any service disruption as Connect has already been stood up (https://connect.apps.zuora.com) but we are posting a notice as customers would see a change in routing, if they were looking. You are welcome to login, there is no impact by any actions as this is essentially a mirror of existing setup. You should however see speed increases in new environment.  During this timeframe, we will be switching the DNS so that new primary takes full control.

 

For those of you with tenant IP whitelisting, you want to ensure that [52.26.252.153, 52.39.100.104, 52.37.233.34 ] are whitelisted. This should have already happened for all customers as they would otherwise have non functional apps. https://knowledgecenter.zuora.com/CE_Connect/Zuora_Connect_Apps

Scholar

Thanks for the detail!

 

For future notices, I think it would be best to indicate there is no expected interruption instead of the may be interruption. The *may* implies, at least to me, that interruption should be expected.

Zuora Staff

@tisubs

 

Thanks for feedback.