@creamy-memory-47952 has left the channel

@mammoth-forest-70320 has left the channel

Is it possible to disable the default Rancher-created projects, during the Rancher installation ? I am referring to the projects that group the namespaces

Guys, if I've created a cluster using Rancher provider in Terraform and I have a question: Can I delete the cluster in Rancher UI without delete cluster in cloud??

@astonishing-engine-86351 has left the channel

Hi, I am running cluster autoscaler with provider "rancher". Autoscaler needs rancher token to do scale up/down actions which makes sense. However, i want to limit the token privilege for cluster where autoscaler is deployed. The problem is that autoscaler rancher provider does not work with cluster scoped token. Kindly advise. Any help will be highly appreciated.

From the Rancher dashboard is it possible to know if the k8s cluster is setup on on-premises bare metal or in a virtualized Citrix Xen Server on top of bare metal?

What is the default ssh password for harvester 1.1.2?

Hi All It is about rancher local-path storage . I want to create a PVC with a different path, and I see that it is possible, but I have to mention the path for every node in the “nodePathMap” In such a situation, when we have 20+ nodes, it will be challenging to make an entry for all the nodes, and we have to keep editing the config map whenever new nodes get added. https://github.com/rancher/local-path-provisioner#storage-classes Can we override the default path used in the config map, nodePath location, via storage class?

@clean-rain-26672 has left the channel

@billowy-baker-61557 has left the channel

i am new to rancher desktop, i just use rancher desktop to build an image but i do not know where the image stored in my windows

can someone help me on this issue ..I have created multi RKE node cluster in Centos 7.9 using VirtualBox... I am getting below error in CNI

2023-05-10 20:49:25.716 [INFO][47] status-reporter/watchersyncer.go 130: Sending status update Status=in-sync

2023-05-10 20:49:42.672 [WARNING][45] felix/table.go 654: Detected out-of-sync inserts, marking for resync actualRuleIDs=[]string{"wUHhoiAYhphO9Mso", "", "", "", "", "", "", "", "", "", "", "", "", "", "", "", "", "", "", "", "", "", "", "", "", "S93hcgKJrXEqnTfs", "mp77cMpurHhyjLrM", "", ""} chainName="FORWARD" expectedRuleIDs=[]string{"wUHhoiAYhphO9Mso", "", "", "", "", "", "", "", "", "", "", "", "", "", "", "", "", "", "", "", "", "", "", "", "", "", "", "S93hcgKJrXEqnTfs", "mp77cMpurHhyjLrM"} ipVersion=0x4 table="filter"

2023-05-10 20:52:34.653 [WARNING][45] felix/table.go 654: Detected out-of-sync inserts, marking for resync actualRuleIDs=[]string{"", "O3lYWMrLQYEMJtB5", "", "", "", "", "", "", "", "", "", "", "", "", "", ""} chainName="POSTROUTING" expectedRuleIDs=[]string{"O3lYWMrLQYEMJtB5", "", "", "", "", "", "", "", "", "", "", "", "", "", "", ""} ipVersion=0x4 table="nat"

2023-05-10 22:36:35.028 [INFO][47] status-reporter/watchercache.go 125: Watch error received from Upstream ListRoot="/calico/resources/v3/projectcalico.org/caliconodestatuses" error=an error on the server ("unable to decode an event from the watch stream: http2: client connection lost") has prevented the request from succeeding

2023-05-10 22:36:35.029 [INFO][47] status-reporter/watchercache.go 181: Full resync is required ListRoot="/calico/resources/v3/projectcalico.org/caliconodestatuses"

2023-05-10 22:36:45.035 [INFO][47] status-reporter/watchercache.go 194: Failed to perform list of current data during resync ListRoot="/calico/resources/v3/projectcalico.org/caliconodestatuses" error=Get "<https://10.43.0.1:443/apis/crd.projectcalico.org/v1/caliconodestatuses?limit=500&resourceVersion=0&resourceVersionMatch=NotOlderThan>": net/http: TLS handshake timeout

2023-05-10 22:36:46.036 [INFO][47] status-reporter/watchercache.go 181: Full resync is required ListRoot="/calico/resources/v3/projectcalico.org/caliconodestatuses"

2023-05-10 22:36:56.047 [INFO][47] status-reporter/watchercache.go 194: Failed to perform list of current data during resync ListRoot="/calico/resources/v3/projectcalico.org/caliconodestatuses" error=Get "<https://10.43.0.1:443/apis/crd.projectcalico.org/v1/caliconodestatuses?limit=500&resourceVersion=0&resourceVersionMatch=NotOlderThan>": net/http: TLS handshake timeout

2023-05-10 22:36:57.049 [INFO][47] status-reporter/watchercache.go 181: Full resync is required ListRoot="/calico/resources/v3/projectcalico.org/caliconodestatuses"

2023-05-10 22:37:07.064 [INFO][47] status-reporter/watchercache.go 194: Failed to perform list of current data during resync ListRoot="/calico/resources/v3/projectcalico.org/caliconodestatuses" error=Get "<https://10.43.0.1:443/apis/crd.projectcalico.org/v1/caliconodestatuses?limit=500&resourceVersion=0&resourceVersionMatch=NotOlderThan>": net/http: TLS handshake timeout

2023-05-10 22:37:08.065 [INFO][47] status-reporter/watchercache.go 181: Full resync is required ListRoot="/calico/resources/v3/projectcalico.org/caliconodestatuses"

[rke@kube-master rke-k8s]$

@ancient-doctor-54536 has left the channel

Hi there, Since we have changed the hostname of our Rancher server we have the following error in the logs of Rancher pods: 2023/05/12 090238 [ERROR] Failed to dial steve aggregation server: dial tcp: lookup rancher.dev.marklogic.cloud on 10.0.0.1053 no such host. steve aggregation server is still pointing to the old hostname. I've tried to change the URL in the stv-aggregation secret but obviously afterwards I'm getting : 2023/05/12 091410 [ERROR] Failed to handle tunnel request from remote address 10.4.8.7:16158 (X-Forwarded-For: 20.126.161.56:2498): response 401: failed authentication Fri, May 12 2023 111410 am 2023/05/12 091410 [ERROR] Failed to dial steve aggregation server: websocket: bad handshake Any helps would be appreciated. Thanks.

any one can help on this >> v1beta1.custom.metrics.k8s.iocattle-monitoring-system/rancher-monitoring-prometheus-adapterFalse (FailedDiscoveryCheck)

while beta metric is active

v1beta1.metrics.k8s.iokube-system/metrics-serverTrue

issue with custom metrics

pls help

Hi all, please can anyone help me? I have deployed Rancher version 2.7.1 on VM (aws ec2). I have created one cluster with one node (etcd, control plane and worker) - other VM on aws. I need to add new worker node. But when I try to run register agent on my new node (also aws ec2), they are not able to register into cluster. I see in kubelet container communication to localhost IP address 127.0.0.1 (e.g. https://127.0.0.1:6443/apis/node.k8s.io/v1/runtimeclasses?limit=500&resourceVersion=0). I think I made mistake in setup of first master node or Rancher itself, but is there any option how to change this IP address to FQDN of Rancher or public IP address of Rancher server?

Hi All, I have Rancher_V2.6.11 Deployed in AWS EKS_1.24 With managed nodes (EC2 Instances). Rancher Backups are working (to S3 Bucket with IAM Role) with EC2 Metadata IMDSv1. But when i enable EC2 Metadata IMDSv2 , rancher backup is failing with error (ERRO[2023/05/18 061036] error syncing 's3-recurring-backup': handler backups: failed to check if s3 bucket [svmx-rancher-backups] exists, error: 401 Unauthorized, requeuing). Rancher document says EC2 Metadata IMDSv2 works with rancher. Can you please help here to see if i miss anything?

anyone has solution for centralized logging solution -- rancher and Elastic search ??

I was just curious. What tooling does SUSE use for generating the Helm charts for Rancher Manager?

Does anyone have experience with Prometheus/grafana monitoring within rancher? I'd be happy to hear about your experience.

@adorable-toddler-38962 has left the channel

Guys, I'm having trouble making a decision here on how to import my cluster in rancher. I understand that we have a way to import using terraform rancher2_cluster resource, but I can also import just by running the commands directly in the cluster. What would be the most appropriate approach if I want my cluster to be completely independent of the rancher and what would be the pros and cons of using the generic import or the import of some cloud provider?

@big-parrot-28801 has left the channel

Maximizing Success with AWS Well-Architected Framework: Best Practices and Strategies In this blog post, I explored the AWS Well-Architected Framework and discussed the importance of following best practices and implementing strategies to maximize the success of your AWS Well-Architected implementations. By incorporating the recommended best practices such as designing for scalability, implementing high availability, applying security measures, optimizing costs, and embracing automation, you can build architectures that are robust, efficient, and resilient. https://dev.to/mohammad0omar/maximizing-success-with-aws-well-architected-framework-best-practices-and-strategies-3h3j

any idea how to refresh snapshot , as in UI i am not able to see snapshot, while its visible in cli