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

Deprecate loadbalancerIP, use annotation to fetch service loadbalancerIP #528

Merged

Conversation

lubronzhan
Copy link
Contributor

@lubronzhan lubronzhan commented Mar 6, 2023

Fix ##457
PR in website: kube-vip/website#15
Related issue in kube-vip-cloud-provider kube-vip/kube-vip-cloud-provider#51

  • Add new annotation kube-vip.io/loadbalancerIPs to specify the loadbalancer ip for service
  • Now ip address fetched from loadbalancer service are first fetched from annotation, then fallback to service spec
  • Unit test

Add new annotation kube-vip.io/loadbalancerIPs to specify the loadbalancer ip for service
Now ip address fetched from loadbalancer service are first fetched from annotation, then fallback to service spec
Unit test

Signed-off-by: lubronzhan <lzhan@vmware.com>
@lubronzhan lubronzhan force-pushed the topic/lubron/deprecate_loadbalancerip branch from 9223d19 to a9932ec Compare March 6, 2023 23:53
@thebsdbox
Copy link
Collaborator

Apologies... All documentation for kube-vip.io lives in the /website repo.

@lubronzhan
Copy link
Contributor Author

Ohk, let me also create PR there

@lubronzhan lubronzhan mentioned this pull request Mar 9, 2023
@lubronzhan
Copy link
Contributor Author

Should I only update the website repo or both?

@lubronzhan
Copy link
Contributor Author

Follow up PR here kube-vip/website#15
I think I need to update the pr in website again once the release 0.5.12 is cut so they know which version they should start using the annotations

@thebsdbox thebsdbox merged commit 8af0391 into kube-vip:main Mar 16, 2023
@lubronzhan lubronzhan deleted the topic/lubron/deprecate_loadbalancerip branch February 6, 2024 01:11
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

Successfully merging this pull request may close these issues.

None yet

2 participants