Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

support secure websocket listener feature in router chart #234

Conversation

marvkis
Copy link
Contributor

@marvkis marvkis commented Jul 3, 2024

Hi @qrkourier ,

I continued you work from you initial PR. It's rebased and in an initial 'works for me in my lab' state ;)

This is the wss server related config I use:

additionalVolumes:
  - mountPath: /etc/ziti/wss-cert/
    name: wss-cert
    secretName: nginx-default-cert
    volumeType: secret
edge:
  additionalListeners:
    - advertisedHost: wss.browzer.my.domain
      advertisedPort: 443
      containerPort: 3023
      ingress:
        annotations:
          kubernetes.io/ingress.allow-http: "false"
          nginx.ingress.kubernetes.io/secure-backends: "true"
          nginx.ingress.kubernetes.io/ssl-passthrough: "true"
        enabled: true
        ingressClassName: public
      name: edge-wss
      protocol: wss
      service:
        enabled: true
        type: ClusterIP
identity:
  altServerCerts:
    - mode: localFile
      serverCert: /etc/ziti/wss-cert/tls.crt
      serverKey: /etc/ziti/wss-cert/tls.key
websocket:
  enabled: true

Bye,
Chris

@qrkourier qrkourier self-requested a review July 4, 2024 00:27
@marvkis marvkis marked this pull request as ready for review July 7, 2024 13:50
@qrkourier qrkourier changed the base branch from main to 159-browzer-support-3rd-party-server-certs-for-controller October 2, 2024 16:07
@qrkourier qrkourier merged commit 7d7146d into openziti:159-browzer-support-3rd-party-server-certs-for-controller Oct 11, 2024
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants