833-gitlab-object-storage-use_iam_role

Summary

With the current way the Big Bang chart is set up, the users are unable to use an iam profile for their aws object storage in the gitlab chart. The chart will include the accesskey and secretkey with empty values and no use_iam_profile key.

Resolution

Following these docs

Added a new key and logic into the gitlab template to handle use of an iam profile for gitlab.

Closes #833 (closed)

changed milestone to %1.20.0

added BB Customer Issues gitlab priority5 statusdoing teamXForce labels

added statusreview label and removed statusdoing label

added statusdoing label and removed statusreview label

changed the description

resolved all threads

It does look like the task-runner pod will also need the iam role annotation as well.

added 57 commits

• d1bf54fd...256d554d - 54 commits from branch master
• 9c063275 - helmy and rebase
• 4fdeb7fc - merge
• b057fe39 - Add annotation for task runner

Compare with previous version

resolved all threads

added Affinity/AntiAffinity label

removed Affinity/AntiAffinity label

removed statusdoing label

added statusreview label

resolved all threads

added 1 commit

• fbf41fbe - Update comments in values.yaml

Compare with previous version

resolved all threads