Anupama Upadhyayula

Results 50 comments of Anupama Upadhyayula

Reproduced the issue on v2.6-head `c54b655` cloud provider - Linode - I ran into the same issue when I tried to create an rke2 node driver cluster on k8s `v1.23.10+rke2r1`....

I'm not able to reproduce the issue on v2.6.2: - creating an eks v2 cluster version 1.19 - Installed monitoring - Enabled okta auth provider and added a few users...

Reproduced on 2.6.2: - Enabled github auth in the rancher server - As an admin created an rke1 cluster and added a user as cluster owner - logged in as...

Seen on v2.5.9 as well: - On rancher server created 2 rke1 node driver clusters [3 worker, 1 etcd, 1 cp ] in each cluster - Installed backup charts in...

Verified on v2.6-head 79a5328 Fresh check: 1. Installed rancher server and enabled Azure AD with the `standard` end points. 2. Created 1 rke1 and 1 rke2 node driver all roles...

Re opening the issue on an upgrade use case Rancher installed on v2.6.6, v2.5.15 upgraded to v2.6-head 79a5328 1. Install rancher on either v2.5.15 or v2.6.6 2. Enable Azure AD...

Verified on v2.6-head 82bf000 - Install rancher on either v2.6.5 - Enable Azure AD auth with standard end points. - Upgrade rancher server to v2.6-head - Banner to update the...

Tried this on an upgrade from v2.6.5 >> v2.6-head `2e00266` - Install rancher on v2.6.5 - Enable Azure AD auth with standard end points. - Upgrade rancher server to v2.6-head...

Verified on an upgrade from v2.6.5 >> v2.6-head c0ba0f0 - Install rancher on v2.6.5 - Enable Azure AD auth with standard end points. - Upgrade rancher server to v2.6-head -...