You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If your project needs some tcp or udp services exposed to the outside of your cluster (example: Redis or EMQX) that doesnt use HTTP communication. How can you expose it to the outside through a SCW loadbalancer managed by SCW K8S.
Why is it needed?
I have struggled with this. The documentation on the k8s documentaton exists, but was not sufficient for my usecase.
I can make a tutorial on how to patch it directly, or patch it using Kustomize.
Thank you for suggesting this documentation.
Feel free to write the tutorial and open a PR so we can review it. If your contribution meets our Write for community guidelines, your contribution will be rewarded with a cloud credit.
Hello @daanpersoons you mentioned that you wanted to write the doc yourself, did you manage to do so? Otherwise, we will need to find some bandwidth in the team to do it. Let us know! Thanks!
Summary
If your project needs some tcp or udp services exposed to the outside of your cluster (example: Redis or EMQX) that doesnt use HTTP communication. How can you expose it to the outside through a SCW loadbalancer managed by SCW K8S.
Why is it needed?
I have struggled with this. The documentation on the k8s documentaton exists, but was not sufficient for my usecase.
I can make a tutorial on how to patch it directly, or patch it using Kustomize.
Want to write this documentation yourself?
Yes
Related PR(s)
No response
(Optional) Scaleway Organization ID
f3bb497a-f1e6-4ed9-812c-902b2f37206b
Email address
[email protected]
The text was updated successfully, but these errors were encountered: