Uploaded image for project: 'Red Hat OpenShift Dev Spaces (formerly CodeReady Workspaces) '
  1. Red Hat OpenShift Dev Spaces (formerly CodeReady Workspaces)
  2. CRW-1248

'failed getting JSON response from Kubernetes Client' warnings in Keycloak pod

XMLWordPrintable

    • False
    • False
    • Hide
      DevWorspace doesn't use keycloak.
      Make no sense to fix for current version of CRW
      Show
      DevWorspace doesn't use keycloak. Make no sense to fix for current version of CRW

      'failed getting JSON response from Kubernetes Client' warnings in Keycloak pod.

      WARN  [org.jgroups.protocols.kubernetes.KUBE_PING] (thread-138,ejb,ycloak-598b6c57b4-khhfb) failed getting JSON response from Kubernetes Client[masterUrl=https://172.30.0.1:443/api/v1 , headers={Authorization=#MASKED:883#}, connectTimeout=5000, readTimeout=30000, operationAttempts=3, operationSleep=1000, streamProvider=org.jgroups.protocols.kubernetes.stream.TokenStreamProvider@792525a5] for cluster [ejb], namespace [default], labels [null]; encountered [java.lang.Exception: 3 attempt(s) with a 1000ms sleep to execute [OpenStream] failed. Last failure was [java.io.IOException: Server returned HTTP response code: 403 for URL: https://172.30.0.1:443/api/v1/namespaces/default/pods ]]
      

      RH SSO image for CRW 2.4.0 and CRW 2.3.0 is the same: registry.redhat.io/rh-sso-7/sso74-openshift-rhel8:7.4

      The issue is probably related to upstream changes https://github.com/eclipse/che-operator/pull/371

            abazko Anatolii Bazko
            sskoryk Serhii Skoryk
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: