You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Expected behavior: create_host_user_mode can be set to keep/drop/off as described in the role documentation with the Kube operator
# Controls whether this role supports auto provisioning of SSH users.
# Options: drop (remove user on session end), keep (keep users at session end)
# and off (disable host user creation)
create_host_user_mode: drop
Current behavior:
Setting create_host_user_mode in a role definition for the kube operator fails saying the only accepted value is an integer
[root@ip-172-31-22-182 ~]# cat role.yaml
apiVersion: resources.teleport.dev/v5
kind: TeleportRole
metadata:
name: myrole
spec:
allow:
rules:
- resources: ['user', 'role']
verbs: ['list','create','read','update','delete']
options:
create_host_user_mode: keep
[root@ip-172-31-22-182 ~]# kubectl apply -f role.yaml
The TeleportRole "myrole" is invalid: spec.options.create_host_user_mode: Invalid value: "string": spec.options.create_host_user_mode in body must be of type integer: "string"
This was only resolved when I did set that value to an integer. Trying the old true/false option also failed. As a workaround the role had to be manually updated via the Web UI.
Bug details:
Teleport version: 13.3.7
Recreation steps: Deploy the Teleport Cluster chart with the operator enabled and attempt to create a role with create_host_user_mode
Expected behavior:
create_host_user_mode
can be set to keep/drop/off as described in the role documentation with the Kube operatorCurrent behavior:
Setting
create_host_user_mode
in a role definition for the kube operator fails saying the only accepted value is an integerThis was only resolved when I did set that value to an integer. Trying the old true/false option also failed. As a workaround the role had to be manually updated via the Web UI.
Bug details:
create_host_user_mode
The text was updated successfully, but these errors were encountered: