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'm having an argument with my superior
We want to upgrade to the newest version of keycloak. Currently we're still on the wildfly version
He's claiming that we should deploy keycloak on a couple of Linux vms instead of the managed k8s cluster we have, which is where our wildly keycloak is deployed, because we won't be dependent on the k8s cluster this way
I claim this is silly because then we lose all the advantage of cloud native applications and also the main point of the new kc version is the move to quarkus, which is a cloud native java framework, so moving off k8s seems counterintuitive
I would love to get some insights about this dilemma
Maybe I should add that the cluster is mainly stable and does not cause too many problems at all
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'm having an argument with my superior
We want to upgrade to the newest version of keycloak. Currently we're still on the wildfly version
He's claiming that we should deploy keycloak on a couple of Linux vms instead of the managed k8s cluster we have, which is where our wildly keycloak is deployed, because we won't be dependent on the k8s cluster this way
I claim this is silly because then we lose all the advantage of cloud native applications and also the main point of the new kc version is the move to quarkus, which is a cloud native java framework, so moving off k8s seems counterintuitive
I would love to get some insights about this dilemma
Maybe I should add that the cluster is mainly stable and does not cause too many problems at all
All reactions