APDEX ETL Deployment ¶
Deploying new versions of Airflow is automated using Jenkins. This is the case for all of our Airflow-based clusters, which includes Production and Staging APDEX, MSQ, Scorecard, X-Alert, and others. We also use Jenkins to deploy both to our Rancher clusters as well as WebexKubed clusters.
Jenkins : http://10.241.93.117:31111/
WebexKubed ¶
The only Airflow project running in the Kubed environment is the APDEX Airflow project. More specifically we run in two OCP-based clusters in the Webex SJC and DFW DCs.
| dc | Kubed Cluster |
|---|---|
| JFK02 | wjfkgen-p-1 |
| DFW03 | wdfwgen-p-5 |
FedRAMP ¶
We DO NOT use Jenkins to deploy Airflow into the FedRAMP environment; that is done using CMC inside the boundary.
However, our CMC template for our APDEX ETL will use the docker image created using our Jenkins build pipeline.