This message was deleted.
# generala
adamant-kite-43734
08/06/2025, 2:37 PMThis message was deleted.
b
bland-article-62755
08/06/2025, 3:09 PM> Any ideas how to prevent this from happening?
This might sound sarcastic, but don't take it this way: Don't run rancher on a single node.
bland-article-62755
08/06/2025, 3:10 PMnot having a single point of failure for things like webhooks is the main reason you want to run clusters in HA.
bland-article-62755
08/06/2025, 3:11 PMI'm not sure there's going to be another to do what you want and keep it stable on a single node, but adding more nodes would def help.
g
gifted-breakfast-73755
08/06/2025, 4:18 PM@bland-article-62755 I hear you, we've been told to avoid a single node especially on Docker and we do plan on migrating to a K8s cluster but haven't had time to make that leap yet.
gifted-breakfast-73755
08/06/2025, 4:21 PMDo you have any suggestions for a temporary workaround while still on Docker?
b
bland-article-62755
08/06/2025, 4:23 PMNone that are good. You can script out your fix and run it on a cron.
bland-article-62755
08/06/2025, 4:23 PM😅
g
gifted-breakfast-73755
08/06/2025, 4:23 PMIt looks like that workaround I linked to doesn't even work anymore on this version of Rancher since the
kubectlc
creamy-pencil-82913
08/06/2025, 6:17 PMThe standalone docker container is not supported and should not be used for anything except lightweight dev/proof-of-concept. I know you're planning on getting off it, but doing so asap is really the only recommendation I have.
👍 1
g
gifted-breakfast-73755
08/06/2025, 6:21 PM@creamy-pencil-82913 Ok, thanks for the suggestion. I'll try to get to that ASAP.
16 Views