DOCS: Gitlab Runner AWS S3 Govt Cloud configuration
Summary
When trying to configure a gitlab-runner helm chart to use a S3 Govt Cloud Bucket as cache it fails with Bad Request 400. The instructions don't mention that gov cloud require a special / different setup in regards to the s3ServerAddress and s3BucketName being the same and on the following format:
cache:
cacheType: s3
s3CachePath: "gitlab-cache/"
cacheShared: true
## S3 settings
s3ServerAddress: my-gitlab-cache-bucket.s3.us-gov-east-1.amazonaws.com
s3BucketName: "my-gitlab-cache-bucket"
s3BucketLocation: "us-gov-east-1"
s3CacheInsecure: false
Important Note: The Bucket must have a folder in it's root with the same name as the bucket otherwise it will fail.
Steps to reproduce
Try configuring Govt cloud S3 Bucket by just specifiying as s3ServerAddress: "s3.amazonaws.com" and regio us-gov-east-1
Configuration used
(Please provide a sanitized version of the configuration used wrapped in a code block (```yaml))
cache:
cacheType: s3
s3CachePath: "gitlab-cache/"
cacheShared: true
## S3 settings
s3ServerAddress: s3.amazonaws.com
s3BucketName: "my-gitlab-cache-bucket"
s3BucketLocation: "us-gov-east-1"
s3CacheInsecure: false
Current behavior
During Gitlab Build Runner executing a build cache download returns Bad request 400 error. Access key is shown as never been used (since Access Keys are different on Govt Cloud vs Regular cloud)
Expected behavior
It should download the artifacts correctly from the AWS S3 Bucket on Govt Cloud
Versions
- Chart: ( 0.12.0)
- Platform:
- Cloud: (AWS Govt)
- Self-hosted: ( Rancher RKE )
- Kubernetes: (
kubectl version
)- Client: v1.16.1
- Server: v1.16.3
- Helm: (
helm version
)- Client: n/a
- Server: n/a
Relevant logs
(Please provide any relevate log snippets you have collected, using code blocks (```) to format)
Providing the fix logs where provided to zendesk ticket 142750