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
Originally posted by febri4n September 6, 2024
I have a cluster that I installed with k3s using embedded PostgreSQL. I also installed Rancher on the cluster. However, about two days later, when I ran kubectl get namespace, the Rancher installation in the cattle-system namespace disappeared, leaving only the default, kube-node-lease, kube-public, and kube-system namespaces. What could be causing this to happen? I checked the database with the command pg_lsclusters, and its status is online.
The text was updated successfully, but these errors were encountered:
This repository uses a bot to automatically label issues which have not had any activity (commit/comment/label) for 45 days. This helps us manage the community issues better. If the issue is still relevant, please add a comment to the issue so the bot can remove the label and we know it is still valid. If it is no longer relevant (or possibly fixed in the latest release), the bot will automatically close the issue in 14 days. Thank you for your contributions.
Discussed in #10847
Originally posted by febri4n September 6, 2024
I have a cluster that I installed with k3s using embedded PostgreSQL. I also installed Rancher on the cluster. However, about two days later, when I ran kubectl get namespace, the Rancher installation in the cattle-system namespace disappeared, leaving only the default, kube-node-lease, kube-public, and kube-system namespaces. What could be causing this to happen? I checked the database with the command pg_lsclusters, and its status is online.
The text was updated successfully, but these errors were encountered: