-
Notifications
You must be signed in to change notification settings - Fork 17
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
Harvester cloud provider enhancement #32
Conversation
Merge after harvester/load-balancer-harvester#13 |
daef3a3
to
86256bb
Compare
85566f9
to
2d23106
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One general question is about the Primay and Secondary services
, which scenario will require it ?
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Still needs a better clarification of the scenario of the primary and secondary service
how will the user create/configure and use this feature.
The UI is working in progress and I'll add the document later. Users add annotation |
I guess, the users may want to use one VIP for all, for each PORT/each group of PORTs, it can specify a kind of service. But it should be in a further enhancement. Please Martin-Weiss confirm if the current design can meet your requirement in harvester/harvester#2772, thanks. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, thanks.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, thanks.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tested both DHCP & Pool IPAMs, LGTM! Thanks.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, Thanks
Define two service types - Primary service is the load balancer service which will be used to create the load balancer - Secondary service is the load balancer service which will share the load balancer created by the primary service. The ccm watches a secondary service, it will not create a load balancer, but get the specify primary service from annotation `cloudprovider.harvesterhci.io/primary-service`. The primary service will share its load balancer with the secondary service. Since the secondary service will have the same load balancer IP with the primary service and the service address format is IP:port, secondary service ports must not be used in the primary service to avoid service address conflict.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, thanks.
Related issue: harvester/harvester#1762 harvester/harvester#2772