Vivek Shilimkar

Validated this issue on rancher v2.6-head and v2.7-head windows cluster - 1cp, 1etcd, 1wk (Linux), 1wk (Windows) Validation steps: 1. Created a rancher v2.6-head and v2.7-head 2. Provisioned a k8s...

Also validated the same with OPA-gatekeeper 101.0.0+up3.9.0. Uninstallation was successful.

@Sahota1225 I added the reproduction steps.

Adding a "/" in path doesn't solve the issue. I still see 404 while trying to reach http://[worker-ip-address]/service2.html

@brandond Right, Adding `/` to `PathPrefix:` worked. Will close this issue. However, we need to update the jenkins automation test according to the traefik. Will create another issue to track...

Validated on rancher v2.6.7 All the validations done are checked in the issue. Public AMI - ami-02f3416038bdb17fb Private AMI - ami-07a49ad213adc30c6 Validated RKE2 node driver cluster creation on Linode as...

Blocked due to following two issues. 1. https://github.com/rancher/dashboard/issues/6773 2. https://github.com/rancher/dashboard/issues/6774

Validated docker install test scenario. 1. Installed a rancher server v2.6-head on Ubuntu 22.04. 2. Made sure rancher do not restart. 3. Provisioned a downstream cluster. Cluster comes up active...

Fresh install checks blocked by this issue. https://github.com/rancher/rancher/issues/39188

[#39188](https://github.com/rancher/rancher/issues/39188) issue is not reproducible on rancher v2.7-head(0de241c). **Fresh install checks passed.** Validations steps: 1. On rancher version v2.7-head, KDM pointing to dev-v2.7, cluster creation succeeds for `v1.24.6-rancher1-1`, `v1.23.12-rancher1-1` and...