This message was deleted.
# general
a
This message was deleted.
p
Even an officially suported idp (keycloak oidc in my case) work very poorly with outdated doc... so good luck
b
I just got it working 🀯
p
Well played !!
b
i'll share my notes for anyone finding this later edit: https://hackmd.io/8iWkDLTZQdGQxN2bAoHXoQ
s
p
πŸ‘ 1
b
i didn't had any issues, just very hard to figure out wihtout docs how to add keycloak saml auth provider using zitadel instead as it works just like any saml
s
I had wondered, i don't think we have a generic saml provider yet. Slight spoiler, generic oidc is on the way
b
> Slight spoiler, generic oidc is on the way When? πŸ‘€πŸ‘€πŸ‘€ that would be much better Would it be a problem to let my users sign in with my Keycloak saml for now and then later switch to your generic oidc. (is it safe to remove an auth provider in rancher?)
p
Also Richard, are you able to re-open the pull request i linked? The guy that did it did everything correctly, except he went MIA when some questions were asked. As i sanswered the questions, I feel opening another PR for what would be the exact same content would be wasteful.
s
When?
Unfortunately we can't commit, but expected in 2.9.0 / 2.10.0
it be a problem to let my users sign in with my Keycloak saml for now
and then later switch to your generic oidc. (is it safe to remove an
auth provider in rancher?)
I'm a lowly UI guy, but would expect this to involve re-creating all bindings to matching groups in the new generic oidc provider
πŸ™Œ 1
@powerful-librarian-10572 i'll take a look
πŸ‘ 1
a
Hi @stocky-account-63046, we are looking for ARM64 support. I know it's coming with 2.9.0 release. Is there any ETA for this? Q3-2024, Q4-2024 or 2025?
βž• 2
s
2.9.0 is currently targetted for this month. I cannot commit to anything specific though, whether date or feature set
πŸ‘ 2
m
I just looked thru the 2.9.0 Release Notes, https://ranchermanager.docs.rancher.com/v2.5/getting-started/installation-and-upgrade/advanced-options/enable-experimental-features/rancher-on-arm64, and did not see any mention of official support for running Rancher on ARM.64. We were able to run Rancher on an ARM64 server and add ARM64 worker nodes in our lab, but we would like to hear if Rancher/RKE2 is officially supported on ARM64. We now have a problem joining an x86 worker node sporting 8 GPUs to the ARM64 cluster via Rancher/RKE2. We will investigate further to see if this is a user error or a true chip architecture incompatibility. Also, tthe Cluster Options page, https://ranchermanager.docs.rancher.com/v2.5/getting-started/installation-and-upgrade/advanc[…]al-features/cluster-provisioning/rke-clusters/options, is 404. Would love to hear from others their experience and workarounds, if any. Also, any pointers would be greatly appreciated, besides the links mentioned.