Installing RKE with a Specified UID
Last updated: June 10, 2026
| Tier | Deployment |
|
|
When installing Sisense, the default installation user ID is 1000. Sometimes, due to security restrictions, it is not possible to use UID 1000. In this case, you need to specify a different UID and use it to install Sisense.
Note:
-
When using a non-default UID, monitoring is not natively supported.
-
The user must have a name other than sisense.
Before installing Sisense, on each node:
-
Create the user that you want to use, and generate a password for it. Make sure that the user is on each node with the same UID.
sudo adduser CustomUsername -
Add the user to the sudoers file: /etc/sudoers.d/custom-user-permission.
CustomUsername ALL=(ALL:ALL) NOPASSWD: ALL -
Add the user to the docker group.
sudo usermod -aG docker CustomUsername -
Connect to the node as the user you created.
sudo su - CustomUsername -
Configure the SSH key to all the nodes. For details, see https://www.cyberciti.biz/faq/how-to-set-up-ssh-keys-on-linux-unix/.
-
Run the following command on each of the instances:
ssh-copy-id CustomUsername@instance_node_IP
Set the following parameters:
-
UID
-
GID
-
fsGroup (a Kubernetes setting) If you do not have something specific you want to use, you can use the user's GID.
-
internal_monitoring
Example:
internal_monitoring: false
linux_user: CustomUsername
run_as_user: 1003
run_as_group: 1003
fs_group: 1003
Set the following parameters:
-
securityContext:
-
UID
-
GID
-
fsGroup (a Kubernetes setting) If you do not have something specific you want to use, you can use the user's GID.
-
-
monitoring (must be set to false)
-
internal
-
Example:
securityContext:
runAsUser: 5050
runAsGroup: 5050
fsGroup: 5050
monitoring:
internal: false
Set the following parameters:
-
UID
-
GID
-
fsGroup (a Kubernetes setting) If you do not have something specific you want to use, you can use the user's GID.
-
internal_monitoring
Example:
internal_monitoring: false
linux_user: CustomUsername
run_as_user: 1003
run_as_group: 1003
fs_group: 1003