UlziiY

Ever after upgrading k3s version to 1.26.3, nothing has changed and still keep restarting.

now at least it restarts randomly after running for 5-40mins and prints out below message before it gets rebooted. I assume something is trying to apply some changes to the...

@benjaminjb do you have any idea what could be the cause?

thanks @benjaminjb for the quick response. You understood it correctly and all the bullet items you wrote above are correct. I'm still wondering why it runs on one, while doesn't...

now I've paused the pg cluster reconcilliation process by running below command and haven't received 'receiving SIGHUP' message since then. But it's not a permanent solution as the operator will...

so far below are the differences I've found between 2 clusters. - On the problematic cluster, we have fluxcd version v0.38.3 running while v2.0.0-rc.1 running on the another cluster (where...

hi, I really appreciate your help. Sounds like your approach is way more safer and reliable. Since we still have the PGO in a degraded state, I would opt for...

hi @benjaminjb, yes you're correct, that's what I tried to mean. I'm still experiencing the issue and haven't found a solution yet. To answer your question. - PGO version we're...

thanks @benjaminjb, actually it seems I was looking at the wrong log. According to your suggestion, looked at pgo log and found something interesting. ` time="2024-12-10T17:33:07Z" level=debug msg="wrote PostgreSQL users"...