-
Notifications
You must be signed in to change notification settings - Fork 66
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
ReplicationDestination ServiceType NodePort support #814
Comments
@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. |
The documentation dosent mention nodeport anywhere request to please update the document so that it will help kubernetes users to easily adopt volsync Does the kind kind: ReplicationDestination support servicType : NodePort It only mentions Ingress or LB in Doc |
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: