editor should report unreachable host, not socket closed

[adietish]

Steps:

1. ASSERT: have 2 clusters, cluster1 set as current, cluster2 not reachable (ex. minikube stopped)
2. ASSERT: have a resource file to edit ex. job.xml

apiVersion: batch/v1
kind: Job
metadata:
  name: countdown
  labels:
    jedi: luke
spec:
  template:
    spec:
      containers:
        - name: counter
          image: centos:7
          command:
            - "bin/bash"
            - "-c"
            - "for i in 9 8 7 6 5 4 3 2 1 ; do echo $i ; done"
      restartPolicy: Never

3. EXEC: open editor with the resource file
4. ASSERT: editor notifies you that you can create a new resource (or update an existing one) on the current context cluster1
5. EXEC: switch to cluster2 as current context

Result: Editor reports "Socket closed"

Expected result: Editor should report that cluster2 is not reachable.

[adietish]

@jeffmaury referring to https://github.com/redhat-developer/intellij-kubernetes/pull/404#pullrequestreview-972380380, can you please specify what your expectation as a user would be?

[jeffmaury]

Cluster not available or something like that

[adietish]

No error is displayed in the editor when switching the context. The error is displayed when the user tries to push to the cluster Closing.