logo
Alauda Build of Gitlab Docs
logo
Alauda Build of Gitlab Docs
Navigation

Overview

Introduction
Features
Lifecycle Policy
Release Notes

Install

Installing Operator
Configuring Redis, PostgreSQL, and Account Credentials
GitLab Instance Deployment

Upgrade

Managing Large Files with LFS
GitLab Official Backup and Restore
GitLab Backup and Restore Using Velero
Data migration from GitLab 14.0.12 to 17.8.z
How to Customize Rails Secrets
Troubleshooting

How to

Managing Large Files with LFS
How to Customize Deployment Templates

API Reference

Introduction

Kubernetes APIs

GitlabOfficial
📝 Edit this page on GitHub
Previous PageData migration from GitLab 14.0.12 to 17.8.z
Next PageTroubleshooting

#How to Customize Rails Secrets

Set the following environment variables first:

export NEW_GITLAB_NAMESPACE=<namespace of the new GitLab instance>
export NEW_GITLAB_NAME=<name of the new GitLab instance>

Save the Rails secrets in a local secrets.yml file.

Example:

# Create the file
cat > secrets.yml <<EOF
production:
  secret_key_base: ...
  otp_key_base: ...
  ...
EOF

Save the Rails secrets to a Kubernetes Secret:

kubectl create secret generic rails-secret -n ${NEW_GITLAB_NAMESPACE} --from-file=secrets.yml

Update the GitLab instance configuration:

kubectl edit gitlabofficial ${NEW_GITLAB_NAME} -n ${NEW_GITLAB_NAMESPACE}

Add the following spec configuration to the CR:

spec:
  helmValues:
    global:
      railsSecrets:
        secret: rails-secret

Wait for the instance to complete redeployment.