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

Automate Client Failover #461

Merged
merged 2 commits into from
Aug 7, 2023
Merged

Conversation

ryanemerson
Copy link
Contributor

@ryanemerson ryanemerson commented Aug 3, 2023

Closes #446

Copy link
Contributor

@ahus1 ahus1 left a comment

Choose a reason for hiding this comment

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

Hi @ryanemerson - thank you for this nice automation!

I pushed some documentation changes in 7384622 and also added "one-image-to-explain-everything".

It doesn't allow a loadbalancer to survive the daily reaper; we can discuss in today's meeting if this is necessary and when this should be implemented.

I agree a random part of the subdomain is helpful to allow multiple test setup in the same OpenShift clusters. At the same time I found the random names a bit difficult as they didn't show me which clusters where involved. So I decided to prefix the two cluster names to the subdomain. Please let me know what you think about this, and it this needs to change.

@ahus1 ahus1 merged commit b3e07e2 into keycloak:main Aug 7, 2023
2 of 3 checks passed
@ryanemerson
Copy link
Contributor Author

Thanks for all the additions. The image and the subdomain changes are a big improvement 🙂

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.

Failover of loadbalancer for 2 DCs
2 participants