Hi everyone,
Following tv-app decommission. I would like to announce that tv-lb (api.traveloka.com) decommission plan.

Decommission tv-lb a bit tricky, because we still need to support a backward compatibility to support the old Traveloka Android and iOS apps that already hardcoded api.traveloka.com on the app.

Apps version 3.19 that will release on 21 Feb 2020 is our first apps that no longer hitting the legacy api.traveloka.com.

One year after 3.19 released which is on the 21 Feb 2021 will be the end of life of the tv-lb.

Plan

Following this https://tvlk.slack.com/files/T02T3CAFM/FTTM7PLFL?origin_team=T02T3CAFM announcement, this year will be the last renewal for tv-lb cert renewal.
Reducing the number of tv-lb instance. Currently tv-lb have three instances that using c3.4xlarge. After apps v3.19 release, we will check the usage and reduce the number of instance and machine according to the system usage. Based on current data it is safe to downgrade tv-lb instances type. It can potentially save $1,701 monthly. (Downgrade of tv-lb instance will be announced separately)
After 3.19 Apps release there should be no routes and NGINX config modification on the tv-lb. however there still a needs to changes the NGINX config for Multi account migration proposes. For this case we suggesting changing the config via SSM. There will be a SOP created by BE Infra for this specific case. cc @fajrin.

Important Date

21 Feb 2021 will be the end of life of TV-LB (one year after 3.19 apps release).

Impact

api.traveloka.com is no longer accessible. The end-users app fails to connect to services that still served by tv-lb.

Thanks

:bows:

tv-lb (api.traveloka.com) Decommission Plan

Plan

Important Date

Impact