Tiago Silva 40861809a6 Add RoleV6 resource type (#19324) ... This PR includes a new Role resource version that is compatible with V5 spec. The new resource introduces the `kubernetes_resources` definition that allows operators to limit the Kubernetes resources that each member can access. The `kubernetes_resources` entries must follow the following format: `{"kind":"<kind>", "namespace":"<namespace>","name":"<pod>"}`. Currently, it only supports objects of `kind` `pod`. Valid examples `<namespace>/<name>: - `*/*`: matches all pods in all namespaces. - `default/*`: matches all pods in the `default` namespace. - `*/nginx-*`: matches every pod prefixed with `nginx-` in every namespace. For older resource versions - V5, V4, V3 - `kubernetes_resources` is automatically populated with `{"kind":"pod","namespace":"*","name":"*"}` to keep compatibility. For the newest version, it's mandatory to define its value otherwise access to pods will be denied. Part of #18434		2023-01-05 09:58:12 +00:00
..
resources.teleport.dev_githubconnectors.yaml	Add RoleV6 resource type (#19324)	2023-01-05 09:58:12 +00:00
resources.teleport.dev_oidcconnectors.yaml	operator: Add auth_connector support (#17448)	2022-11-10 15:42:18 +00:00
resources.teleport.dev_roles.yaml	Add RoleV6 resource type (#19324)	2023-01-05 09:58:12 +00:00
resources.teleport.dev_samlconnectors.yaml	operator: Add auth_connector support (#17448)	2022-11-10 15:42:18 +00:00
resources.teleport.dev_users.yaml	operator: Add auth_connector support (#17448)	2022-11-10 15:42:18 +00:00