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
@viju2008 Looking at the code that creates the service, I don't see why NodePort wouldn't work. Have you tried it out yourself in your environment? Wondering if just a doc update is required here to mention NodePort.
Describe the feature you'd like to have.
ReplicationDestination ServiceType should have the option of NodePort
Currently only LoadBalancer or ClusterIP is supported
What is the value to the end user? (why is it a priority?)
NodePort based replication will enable projects which only use Ingress in Self Deployed Vanilla Kubernetes to utilize volsync
How will we know we have a good solution? (acceptance criteria)
NodePort based replication support gets added and tested
Additional context
It will be useful if we are deployed Open Source Kubernetes with Only Ingress and without a external Load Balancer
The text was updated successfully, but these errors were encountered: