a year ago
For services with volumes or stateful deployments, expect a brief 30–45 second downtime window during the volume re-mount into the new deployment.
I am kind of afraid of this since I had issues with railways metal. My production instances are still on the old one. Is there a way to stop this?
5 Replies
Esp when it comes to IP addressses.
My prod db is not on railways and has a filter for IP addresses. This will automatically make downtime.
I can fix all my issues in 10 days => yes. But maybe other users not!
oh wow =>
To minimize disruption, we recommend whitelisting the new outbound IP address for your region ahead of time:
Region New Outbound IP
US-West (California) 162.220.232.99
US-East (Ashburn, VA) 162.220.234.15
Singapore 208.77.246.15
EU-West (Amsterdam, NL) 208.77.244.15
this error log here only comes with metal and not with the "old" plans
SPRING_AUTOCONFIGURE_EXCLUDE="org.springframework.boot.actuate.autoconfigure.metrics.MetricsAutoConfiguration,org.springframework.boot.actuate.autoconfigure.metrics.SystemMetricsAutoConfiguration"
this is the quick and dirty fix => i migrated now my prod instance.
But Support team, pls be aware the new plans are not 100% the same