-
## Describe the bug
When running all negative test cases with the following options:
```
-i \"negative\" --exclude \"cluster\" --exclude \"storage-network\" -v LOOP_COUNT:1 -v RETRY_COUNT:25920…
-
A rancher rke cluster which just installed the newest docker version
```
Failed to get version - error=400 Bad Request: client version 1.21 is too old. Minimum supported API version is 1.24, pleas…
-
## SURE-8776
### Issue description:
The kubectl shell in the Rancher UI does not work for imported AKS downstream clusters. This works fine for RKE downstream cluster, this is AKS specific issue.
…
mjura updated
1 month ago
-
Looks like when I launch an upstream cluster on AWS with RKE, it's launching Ubuntu instances. Would be nice to use SLES instead, or as an option.
See: https://github.com/rancherlabs/hosted-rancher…
-
I'm trying to deploy RKE `v1.20.6-rancher1-1` with rancher v2.5.8, which should be supported by the [release notes](https://github.com/rancher/rancher/releases/tag/v2.5.8).
I'm getting the followin…
-
## Describe the bug (🐛 if you encounter this issue)
We ran into an issue on our cluster where upon the creation of a RWX workload hundreds of share-manager instances for the created PV are started …
-
## Hello!
- Vote on this issue by adding a 👍 reaction
- If you want to implement this feature, comment to let us know (we'll work with you on design, scheduling, etc.)
## Issue details
Whe…
-
**Describe the bug**
I'm using the specific validation error that brought this matter to my attention, but seems to apply to any given cloud-init validation error to reproduce this behavior.
Whe…
-
Hi there!
First, Thank you for spending so much time and effort on your documentation. It really helps, and the love y'all put into the documentation shows.
I'd love to see a soup-to-nuts journe…
-
## Describe the bug (🐛 if you encounter this issue)
After upgrading to longhorn v1.4.3 from v1.3.3, pod remain in Init state since volume is attached to different node.
## To Reproduce
## E…