Manually Setting Up the User Secret

You can also manually create a MapR user secret for accessing secure and unsecure storage clusters.

There is a sample mapr-user-secrets-secure.yaml file for secure clusters and a mapr-user-secrets-unsecure.yaml file for unsecure clusters in the examples/secrettemplates directory. To manually create a user secret, you can either modify the sample file or create your own custom file and set the values for the properties shown in the following table. If you create your own custom file, you must set the value of the CONTAINER_TICKET property to the Base64 encoded value of a MapR ticket (generated using the maprlogin utility).
Important: User secret information must use Base64 encoding. Base64 is not designed to encrypt fields. Secrets only use Base64 to obfuscate secret values from casual viewing. Secrets are actually encrypted during transport by standard SSL encryption. Secrets are encrypted at rest via built-in encryption of the Kubernetes secret store (remember to enable this option in Kubernetes if you choose to use the built-in store) or via an external secret store.
Parameter Description
MAPR_SPARK_USER Specifies the user that runs the Spark job. The value must be Base64 encoded.
MAPR_SPARK_PASSWORD Specifies the password of the user that runs the Spark job. The value must be Base64 encoded. Note: This field is required for logging in to the Spark driver UI.
MAPR_SPARK_GROUP Specifies the group of the user that runs the Spark job. The value must be Base64 encoded.
MAPR_SPARK_UID Specifies the ID of the user that runs the Spark job. The value must be Base64 encoded.
MAPR_SPARK_GID Specifies the ID of the group of the user that runs the Spark job. The value must be Base64 encoded.
CONTAINER_TICKET The user's ticket generated on a system with maprlogin. The value must be Base64 encoded.
SECURE_CLUSTER true or false depending on whether the cluster is secure or unsecure. The value must be Base64 encoded.

After setting up the secret files, deploy the secrets in the Compute Space. For more information, see Applying the Credentials.