Feature: Event-Driven Architecture should support "offline" mode

[metacoma]

After a kubernetes cluster reboot, if the cluster comes up without an internet connection, certain EDA (Event-Driven Architecture) workloads fail to start properly. These components should be able to recover and operate in offline mode to support air-gapped or isolated environments.

• neo4j

NAME           READY   STATUS   RESTARTS   AGE
pink-neo4j-0   0/1     Error    0          132m
$ kubectl -n context-pink logs pink-neo4j-0 install-apoc-plugin
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed

  0     0    0     0    0     0      0      0 --:--:--  0:00:04 --:--:--     0curl: (6) Could not resolve host: github.com

• redpanda

kubectl -n redpanda get pods
NAME                                 READY   STATUS             RESTARTS      AGE
neo4j-cdc-0                          0/2     Error              0             141m
neo4j-cdc-configuration-sdhhc        0/1     Completed          0             141m
neo4j-cdc-console-6d79678b56-t8f52   0/1     CrashLoopBackOff   8 (85s ago)   141m
.... redpanda logs
System check "NTP Synced" failed with non-fatal error "couldn't check NTP with timedatectl or ntpstat"

• ingressgateway (more details here Istio Ingress occasionally fails with ImagePullBackoff error #19)

kubectl -n istio-system get pods
NAME                                    READY   STATUS             RESTARTS        AGE
istio-ingressgateway-6676956bcb-lqr89   0/1     ImagePullBackOff   0               135m