Add workaround for services added to existing cluster post-upgrade not working (#964)

* add workaround for broken services after upgrade

* linting

Author: wtripp180901

playbooks/deploy.yml

@@ -51,14 +51,22 @@
       when: azimuth_apps_enabled
     - role: azimuth_cloud.azimuth_ops.azimuth
 
-  # Ensure that Consul is uninstalled
   post_tasks:
+    # Ensure that Consul is uninstalled
     - name: Ensure Consul is uninstalled
       ansible.builtin.include_role:
         name: azimuth_cloud.azimuth_ops.consul
         tasks_from: uninstall.yml
       when:
         - consul_server_host is defined
         - consul_server_port is defined
+    # Workaround for new services on existing Clusters not getting added
+    # to Platforms after upgrades
+    - name: Restart CAPI Operator
+      ansible.builtin.include_role:
+        name: azimuth_cloud.azimuth_ops.azimuth_capi_operator
+        tasks_from: restart.yml
+      when: azimuth_kubernetes_enabled
+
   environment:
     KUBECONFIG: "{{ kubeconfig_path | default('') }}"

roles/azimuth_capi_operator/tasks/restart.yml

@@ -0,0 +1,4 @@
+---
+- name: Restart deployment
+  ansible.builtin.command: "kubectl rollout restart deployment {{ azimuth_capi_operator_release_name }} -n {{ azimuth_capi_operator_release_namespace }}"
+  changed_when: true