Change Details

In order for the helm chart to be deployed, the helmfile.d structure needs to be created. Deploy is then done manually on the deploy servers. That process is described [[ https://wikitech.wikimedia.org/wiki/Deployments_on_kubernetes#Code_deployment/configuration_changes | here ]]. The k8s tokens and namespaces will also need to be created by SRE ServiceOps. This ticket is waiting on https://phabricator.wikimedia.org/T269619 to move forward AC Flink is deployed to production

In order for the helm chart to be deployed, the helmfile.d structure needs to be created. Deploy is then done manually on the deploy servers. That process is described [[ https://wikitech.wikimedia.org/wiki/Deployments_on_kubernetes#Code_deployment/configuration_changes | here ]]. The k8s tokens and namespaces will also need to be created by SRE ServiceOps. We also need to ensure that all networking pieces are in places, in particular that Flink can communicate with the Swift cluster. This ticket is waiting on https://phabricator.wikimedia.org/T269619 to move forward AC Flink is deployed to production

In order for the helm chart to be deployed, the helmfile.d structure needs to be created. Deploy is then done manually on the deploy servers. That process is described [[ https://wikitech.wikimedia.org/wiki/Deployments_on_kubernetes#Code_deployment/configuration_changes | here ]]. The k8s tokens and namespaces will also need to be created by SRE ServiceOps. We also need to ensure that all networking pieces are in places, in particular that Flink can communicate with the Swift cluster. This ticket is waiting on https://phabricator.wikimedia.org/T269619 to move forward AC Flink is deployed to production