Michael Bolot

As noted by others, this appears to be a UI issue at the moment. The permissions seem to be applied in the backend, but the mapping to discover which groups...

I'm not able to reproduce this on v2.8-head. I'll keep this in to-triage so we can confirm, but this might already be fixed.

@fins2 Looking into the issue, I've got a few questions/comments that I'd like to ask to help narrow down the solution a bit more. First, I was able to get...

Thanks for clarifying, your objection (needing to run several applies) is reasonable. That being said, if you are willing to use another tool (like curl) to achieve this I think...

@fins2 Your request makes sense to me. Since your PR to the terraform provider does not provide that capability (and the current workaround that you have works without that change),...

## Summary When users deploy Rancher, Rancher automatically creates the `standard-user` role, which it marks as the default for all new users. Users currently have no method of setting which...

Moving this over to the provisioning team for further work. In short, there are two issues at play here: 1. The `cloudca` driver does not provide a schema for the...

> @MbolotSuse , thank you for doing thorough research into this issue. While it makes sense that schema is required for properly processing this request, it doesn't justify getting 201...

## Basic Requirements - A new field should be added on the GlobalRole [type](https://github.com/rancher/rancher/blob/b74a73ce418ba74aec4f15d835fa64d7ca8851d9/pkg/apis/management.cattle.io/v3/authz_types.go#L143) called Status - This field should have the type `GlobalRoleStatus`, which is a complex type having...

## Basic Requirements - The webhook should prevent users from modifying the owner label on role/rolebinding objects - The webhook checks for these built-in types should use a label selector...