Add a routing to check egress status for ckan apps #4407
Labels
CI/CD
component/catalog
Related to catalog component playbooks/roles
component/egress
component/inventory
Inventory playbooks/roles
Feature
O&M
Operations and maintenance tasks for the Data.gov platform
Testing
We have an egress proxy for each CKAN app to control the outgoing traffic. We noticed that occasionally the egress was disabled for some app, and it can go unnoticed for quite a while. Sometimes CKAN app failed to connect to proxy and caused down time, as described in a slack thread.
We want to run some routing checks on egress status, and get notified if the checks fail.
Sketch
We can add a GH action running CF task on each app to curl some external URL,
The text was updated successfully, but these errors were encountered: