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

Explanation about the node.ws variable #48

Open
danijelTxFusion opened this issue Sep 29, 2024 · 3 comments
Open

Explanation about the node.ws variable #48

danijelTxFusion opened this issue Sep 29, 2024 · 3 comments

Comments

@danijelTxFusion
Copy link
Contributor

danijelTxFusion commented Sep 29, 2024

I am struggling to figure out what is node.ws varible is used for? I created the certificate secret using cert-manager, but can it be used for configuring TLS for rpc, rest and ws endpoints? I see the volume is attached to the node pod, but I can't figure out how to configure celestia node to use that certificate.

 node:
   ws:
      tls:
        enabled: true
        ## A secret must be available in the cluster with the following format:
        ## - name: <secret-name>
        ## - items:
        ##     - key: tls.cert
        ##     - key: tls.key
        secret:
          name: celestia-cert  # created by cert-manager
@danijelTxFusion danijelTxFusion changed the title Explanation about the node.ws. variable Explanation about the node.ws variable Sep 29, 2024
@smuu
Copy link
Member

smuu commented Sep 30, 2024

Hello @danijelTxFusion,

This tls certificate is only used for websocket and is optional. (Only needed for in-browser light nodes on iOS.)

The helm-chart sets the env variable CELESTIA_TLS_PATH to the path to which this secret is mounted, and the indication in the logs is very subtle. During the startup, it shows if it exposes the websocket with or without tls enabled.

Please let me know if you have follow-up questions.

@danijelTxFusion
Copy link
Contributor Author

So the rpc and rest ports need to be behind proxy for TLS communication?

@smuu
Copy link
Member

smuu commented Oct 15, 2024

So the rpc and rest ports need to be behind proxy for TLS communication?

Yes, exactly

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

No branches or pull requests

2 participants