You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I currently have a keycloak 26.7.x deployed in GCP behind an ingress.
I have a few other applications also deployed in gcp that use this keycloak for SSO.
One of our upcoming requirements for these apps is the use of regional(vs global) resources. Since the other apps use keycloak, I figured keycloak probably needs to be handled first. My thinking to do this without a lot of downtime was to allocate a new regionial static ip, hostname, regional managed cert, gateway and http route(s) that point to the existing Service object, Deployment etc. In theory I think this should be possible.
So what I'm thinking is
old hostname auth.somedomain via ingress
new hostname authorization.somedomain via gateway api
If I can make keycloak be accessible via both names, I can switch the the apps that use keycloak for auth to the new name and then remove the old static ip, hostname, managed certificate and ingress.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
I currently have a keycloak 26.7.x deployed in GCP behind an ingress.
I have a few other applications also deployed in gcp that use this keycloak for SSO.
One of our upcoming requirements for these apps is the use of regional(vs global) resources. Since the other apps use keycloak, I figured keycloak probably needs to be handled first. My thinking to do this without a lot of downtime was to allocate a new regionial static ip, hostname, regional managed cert, gateway and http route(s) that point to the existing Service object, Deployment etc. In theory I think this should be possible.
So what I'm thinking is
old hostname auth.somedomain via ingress
new hostname authorization.somedomain via gateway api
If I can make keycloak be accessible via both names, I can switch the the apps that use keycloak for auth to the new name and then remove the old static ip, hostname, managed certificate and ingress.
Is this possible?
All reactions