GCE: WebSocket: connection is broken CloseEvent {isTrusted: true, wasClean: false, code: 1006, reason: "", type: "close", …}

[bowei]

From @unfii on August 29, 2017 13:28

Last ingress GCE.

in ingress logs.

Events:
  FirstSeen     LastSeen        Count   From                    SubObjectPath   Type            Reason  Message
  ---------     --------        -----   ----                    -------------   --------        ------  -------
  58m           58m             1       loadbalancer-controller                 Normal          ADD     default/idecisiongames
  58m           58m             1       loadbalancer-controller                 Normal          ADD     default/idecisiongames
  57m           57m             1       loadbalancer-controller                 Warning         GCE     googleapi: Error 409: The resource 'projects/dm-apps-beta/global/sslCertificates/k8s-ssl-default-idecisiongames
--be0f1d8aa9717d3c' already exists, alreadyExists
  57m           57m             1       loadbalancer-controller                 Normal          CREATE  ip: 130.211.32.230
  57m           57m             1       loadbalancer-controller                 Normal          CREATE  ip: 130.211.32.230
  57m           4m              17      loadbalancer-controller                 Warning         GCE     No node tags supplied and also failed to parse the given lists of hosts for tags. Abort creating firewall rule.

apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  name: test
  labels:
    app: idg-server
  annotations:
    kubernetes.io/ingress.class: "gce"
    kubernetes.io/ingress.global-static-ip-name: "test"
spec:
  tls:
  - secretName: test
  backend:
    serviceName: idg-server
    servicePort: 3000

And also default deployment from
https://github.com/kubernetes/ingress/tree/master/examples/deployment/gce

In console we see.

WebSocket: connection is broken CloseEvent {isTrusted: true, wasClean: false, code: 1006, reason: "", type: "close", …}

How to fix it?

Copied from original issue: kubernetes/ingress-nginx#1262

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

Prevent issues from auto-closing with an /lifecycle frozen comment.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or @fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten
/remove-lifecycle stale

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

[masus04]

Was there ever a solution to this issue? I'm running into the same problem.