How to upgrade the Gitlab Package chart💣

BigBang makes modifications to the upstream helm chart. The full list of changes is at the end of this document.

Read release notes from upstream Gitlab Releases. Be aware of changes that are included in the upgrade. Take note of any manual upgrade steps that customers might need to perform, if any.
Do diff of upstream chart between old and new release tags to become aware of any significant chart changes. A graphical diff tool such as Meld is useful. You can see where the current helm chart came from by inspecting /chart/kptfile
Create a development branch and merge request from the Gitlab issue.
Merge/Sync the new helm chart with the existing Gitlab package code. A graphical diff tool like Meld is useful. Reference the “Modifications made to upstream chart” section below. Be careful not to overwrite Big Bang Package changes that need to be kept. Note that some files will have combinations of changes that you will overwrite and changes that you keep. Stay alert. The hardest file to update is the /chart/values.yaml because the changes are many and complicated.
Delete all the /chart/charts/*.tgz files and the /requirements.lock file. You will replace these files in a later step.
In /chart/requirements.yaml update the gluon library to the latest version.
Run a helm dependency command to update the chart/charts/*.tgz archives and create a new requirements.lock file. You will commit the tar archives along with the requirements.lock that was generated.
```
helm dependency update ./chart
```
In /chart/values.yaml update all the gitlab image tags to the new version. There are about 12 of them. Renovate might have arleady done this for you.
Update /CHANGELOG.md with an entry for “upgrade Gitlab to app version X.X.X chart version X.X.X-bb.X”. Or, whatever description is appropriate.
Update the /README.md following the gluon library script

Update /chart/Chart.yaml to the appropriate versions. The annotation version should match the appVersion.

version: X.X.X-bb.X
appVersion: X.X.X
annotations:
annotations:
  bigbang.dev/applicationVersions: |
    - Gitlab: X.X.X

Use a development environment to deploy and test Gitlab. See more detailed testing instructions below. Also test with gitlab-runner to make sure it still works with the new Gitlab version. Also test an upgrade by deploying the old version first and then deploying the new version.
When the Package pipeline runs expect the cypress tests to fail due to UI changes. Note that most of the cypress test files are synced to the gitlab-runner Package to avoid having two different versions of the same tests. There is one place in particular that frequently fails because the button id number button[id="__BVID__XX__BV_toggle_"] changes in /chart/tests/cypress/03-gitlab-login.spec.js. It is usually necessary to run the cypress tests locally in order to troubleshoot a failing test. The following steps are about how to set up local cypress testing. There is not good documentation anywhere else so it is included here.
Install a current version of cypress on your workstation.
Make a sibling directory named cypress next to where you have gitlab repo cloned.
```
mkdir cypress
ls -l
drwxrwxr-x cypress
drwxrwxr-x gitlab
```
Inside the cypress directory create a symbolic link named integration that points to the cypress tests inside the gitlab repo.
```
cd cypress
ln -s ../gitlab/chart/tests/cypress integration
ls -l
lrwxrwxrwx integration -> ../gitlab/chart/tests/cypress/
cd ..
```

Export the environment variables that are needed by the cypress test. Reference the bbtests: at the end of /chart/values.yaml

export cypress_baseUrl=https://gitlab.bigbang.dev
export cypress_gitlab_first_name=test
export cypress_gitlab_last_name=user
export cypress_gitlab_username=testuser
export cypress_gitlab_password=12345678
export cypress_gitlab_email=testuser@example.com
export cypress_gitlab_project=my-awesome-project
export cypress_adminpassword=put-the-gitlab-root-password-here

run cypress from the parent directory of the gitlab and cypress directories.
```
cypress
```
When Cypress launches select the same directory where you ran cypress and you should see the gitlab cypress tests listed. Run them manually, in order, one at a time.
Investigate and fix errors in the cypress tests. You can run a separate browser with developer tools to find out names of elements on each page.
Update the /README.md again if you have made any additional changes during the upgrade/testing process.

Testing new Gitlab version💣

Create a k8s dev environment. One option is to use the Big Bang k3d-dev.sh with no arguments which will give you the default configuration. The following steps assume you are using the script.
Follow the instructions at the end of the script to connect to the k8s cluster and install flux.
Deploy gitlab with these dev values overrides. Core apps are disabled for quick deployment.

domain: bigbang.dev

flux:
  interval: 1m
  rollback:
    cleanupOnFail: false

networkPolicies:
  enabled: true

clusterAuditor:
  enabled: false

gatekeeper:
  enabled: false

istiooperator:
  enabled: true

istio:
  enabled: true

jaeger:
  enabled: false

kiali:
  enabled: false

logging:
  enabled: false

eckoperator:
  enabled: false

fluentbit:
  enabled: false

monitoring:
  enabled: false

twistlock:
  enabled: false
  values:
    console:
      persistence:
        size: 5Gi

sso:
  oidc:
    host: login.dso.mil
    realm: baby-yoda
  client_secret: ""

addons:

  gitlabRunner:
    enabled: true

  gitlab:
    enabled: true
    git:
      tag: null
      branch: "your-development-branch-name"

    hostnames:
      gitlab: gitlab
      registry: registry
    sso:
      enabled: true
      label: "Platform One SSO"
      client_id: "platform1_a8604cc9-f5e9-4656-802d-d05624370245_bb8-gitlab"
      client_secret: ""

    values:
      gitlab:
        webservice:
          minReplicas: 1
          maxReplicas: 1
          helmTests:
            enabled: false
        gitlab-shell:
          minReplicas: 1
          maxReplicas: 1
        sidekiq:
          minReplicas: 1
          maxReplicas: 1
      registry:
        hpa:
          minReplicas: 1
          maxReplicas: 1
      global:
        appConfig:
          object_store:
            enabled: true
          defaultCanCreateGroup: true

Access Gitlab UI from a browser and login with SSO
Test changing your profile image.
In your profile create an access token with all privileges. Save the token for later use.
Create a group called test
Create a project called test1 with a README.md within the test group
From your workstation git clone with https the test1 project
```
git clone https://gitlab.bigbang.dev/test/test1.git
```
Make a change to README.md and commit and push. Verify that the change shows in Gitlab UI

Test pushing and pulling an image to the project container registry. Use the access token you created.

docker login registry.bigbang.dev
docker pull busybox
docker tag busybox:latest registry.bigbang.dev/test/test1:latest
docker push registry.bigbang.dev/test/test1:latest
docker image rm busybox:latest
docker image rm registry.bigbang.dev/test/test1:latest
docker pull registry.bigbang.dev/test/test1:latest

Test a pipeline with gitlab-runner. Navigate to https://gitlab.bigbang.dev/test/test1/-/settings/ci_cd and disable the Auto DevOps. Navigate to https://gitlab.bigbang.dev/test/test1/-/ci/editor?branch_name=main and configure a pipeline. Verify that it completes successfully at https://gitlab.bigbang.dev/test/test1/-/pipelines.
```
stages:
    - test
dogfood:
    stage: test
    script:
        - echo "dogfood" >> file.txt
    artifacts:
        paths:
            - file.txt
cache:
  paths:
    - file.txt
```
Perform a manual upgrade test. First deploy the current Gitlab version. Then deploy your development branch. Verify that the upgrade is successful.
Retest with monitoring and logging enabled. Verify that the logging and monitoring are working.

Modifications made to upstream chart💣

This is a high-level list of modifications that Big Bang has made to the upstream helm chart. You can use this as as cross-check to make sure that no modifications were lost during the upgrade process.

chart/bigbang/*💣

add DoD approved CA certificates (recursive copy directory from previous release)
If updating new certificates from new bundle
Check Department_of_State/ certificates for spaces in name
Check DigiCert_Federal_SSP/Trust_Chain_2/ certificates for spaces in name
Convert Entrust_Federal_SSP/Trust_Chain_2/0-Entrust_Managed_Services_Root_CA_rekey3.cer to pem format
- openssl x509 -inform der -in 0-Entrust_Managed_Services_Root_CA_rekey3.cer -out 0-Entrust_Managed_Services_Root_CA_rekey3.pem
Remove non-certificate metadata from Carillon_Federal_Services/Trust_Chain_1/1-Carillon_Federal_Services_PIVI_CA2.cer
Remove non-certificate metadata from DigiCert_NFI/Trust_Chain_2/2-Senate_PIV-I_CA_G5.cer

chart/templates/bigbang/*💣

add istio virtual service
add networkpolicies
add istio peerauthentications
add Secrets for DoD certificate authorities

chart/templates/tests/*💣

add templates for CI helm tests

chart/charts/gitlab/charts/toolbox/templates/backup-job.yaml💣

added istio shutdown to command on lines 85 and 87

{{- if and .Values.global.istio.enabled (eq .Values.global.istio.injection "enabled") }}{{ .Values.backups.cron.istioShutdown }}{{- end }}

chart/charts/minio/templates/_helper_create_buckets.sh💣

hack the MinIO sub-chart to work with newer mc version in IronBank image line 65
```
/usr/bin/mc policy set $POLICY myminio/$BUCKET
```

chart/charts/*.tgz💣

run helm dependency update ./chart and commit the downloaded archives
commit the tar archives that were downloaded from the helm dependency update command. And also commit the requirements.lock that was generated.

chart/tests/*💣

add helm test scripts for CI pipeline

chart/templates/_certificates.tpl💣

hack to support pki certificate location within the RedHat UBI image. Is different than Debian based images. Add to definition of gitlab.certificates.volumeMount the volumeMount definition is at the end of the file
```
- name: etc-ssl-certs
  mountPath: /etc/pki/tls/certs/
  readOnly: true
- name: etc-ssl-certs
  mountPath: /etc/pki/tls/cert.pem
  subPath: ca-bundle.crt
  readOnly: true
```

chart/.gitignore💣

comment the charts/*.tgz
comment the requirements.lock

chart/.helmignore💣

change scripts/ to /scripts/ so that the helm test scripts are not ignored

chart/requirements.yaml💣

Add latest gluon dependency to the end of the list

- name: gluon
  version: "x.x.x"
  repository: "oci://registry.dso.mil/platform-one/big-bang/apps/library-charts/gluon"

chart/values.yaml💣

disable all internal services other than postgres, minio, and redis
add BigBang additional values at bottom of values.yaml
add prometheus exporter: gitlab.gitlab-exporter
add default bigbang.dev hostnames for global.hosts
add IronBank hardened images
add pullSecrets for each IronBank image
add default bigbag.dev hostnames at global.hosts
add customCAs (the cert files and secrets need to be added in the next 2 steps for this to work)
Run for i in $(helm template -s templates/bigbang/secrets/DoD_CA_certs.yaml . | grep "name:" | cut -d ":" -f 2); do echo "- secret: $i"; done to get a list of the secrets
add postgresqlInitdbArgs, securityContext, postgresqlDataDir and persistence to get IB image working with postgres subchart
add upgradeCheck.annotations: sidecar.istio.io/inject: “false”
add shared-secrets.annotations: sidecar.istio.io/inject: “false”
add gitlab.migrations.annotations: sidecar.istio.io/inject: “false”
add minio.jobAnnotations: sidecar.istio.io/inject: “false”
add gitlab.toolbox.annotations: sidecar.istio.io/proxyMemory: 512Mi and sidecar.istio.io/proxyMemoryLimit: 512Mi

chart/Chart.yaml💣

change version key to Big Bang composite version
add Big Bang annotations.bigbang.dev/applicationVersions key to support release automation

Last update: 2023-01-10 by Ryan Garcia