Skip to content

Have unique loadbalancer #237

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

Merged
1 commit merged into from
Apr 11, 2023
Merged

Have unique loadbalancer #237

1 commit merged into from
Apr 11, 2023

Conversation

ghost
Copy link

@ghost ghost commented Mar 23, 2023

What type of PR is this?
/kind feature

What this PR does / why we need it:
Not having two cluster with the same loadBalancer Name.
Closes #230
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #230

Special notes for your reviewer:

Please confirm that if this PR changes any image versions, then that's the sole change this PR makes.

TODOs:

  • squashed commits
  • includes documentation
  • adds unit tests

@ghost ghost requested a review from outscale-hmi March 24, 2023 08:34
@ghost
Copy link
Author

ghost commented Mar 29, 2023

@outscale-hmi
The same as #231

Copy link
Contributor

@outscale-hmi outscale-hmi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

OK

@ghost ghost merged commit 2fc36e6 into main Apr 11, 2023
@ghost ghost added the kind/feature Feature resolution label Jul 20, 2023
@jfbus jfbus deleted the get-unique-loadbalancer-name branch February 12, 2025 13:40
This pull request was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Feature resolution
Development

Successfully merging this pull request may close these issues.

Can not create two cluster with the same loadBalancer name
2 participants