UNCLASSIFIED - NO CUI

Skip to content

If gitlab iamprofile is set in objectstorage values, a custom s3 endpoint cannot be set

In this file https://repo1.dso.mil/big-bang/bigbang/-/blob/master/chart/templates/gitlab/secret-objectstore.yaml, the s3 endpoint for each object storage configuration is wrapped into an if block with the aws manual access credentials. Recently, Gitlab enabled overriding of the STS endpoint with an environment variable which made setting the s3 endpoint independent of the STS endpoint as they now incorrectly state in their docs. Please enable setting the s3 endpoint in the storage secret here regardless of iamprofile being set or not.