Now that the webserver is running in Kubernetes, we'll migrate the kerberos and scheduler components to Kubernetes, to see whether everything still works as expected.
- Create the s3 user for the airflow logs
- Create the s3 bucket for the airflow logs
- Store the S3 keys in the private repo
- Stop the kerberos and scheduler systemd services on an-test-client1002
- Copy all airflow logs to the s3 log bucket
- Deploy airflow-analytics-test with kerberos, scheduler and remote logging enabled
- Disable the airflow systemd services on the airflow host