You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
I found this project when looking for a lightweight S3 gateway to use as cache for GitLab CI pipelines. As it looks like the community activities for the project hasn't picked up so I thought I'd describe my usecase which may be useful as inspiration for someone else. I see a need for this kind of simple S3 gateway for many purposes
I have gitlab runners in a k3s cluster which are managed by ArgoCD. I use the helm chart to deploy s3gw (to namespace gitlab-runner) like this
Chart.yaml:
Hence I can tell gitlab-runner to use s3gw.gitlab-runner.svc.cluster.local as address. I haven't found how to make gitlab-runner ignore self-signed certificate so I set Insecure=true to make it use http.
Since I only use S3 internally in this namespace I don't want to enable neither ingress nor ui, but that gave me a challenge that I had to create the bucket. I did that by execute a shell on the pod running s3gw and execute the below script to create runners-cache bucket:
The issues I had was that I had to set storageClass.name even though leaving it empty should have selected the default storage class and that 100 Mbyte is reserved as minimum on the storage so when I to begin with set StorageSize: 100Mi then I got quota error whenever trying to put something in the bucket. Other than that it has worked like a charm.
An improvement would be to be able to set a list of buckets in values.yaml that should be created on deploy.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi,
I found this project when looking for a lightweight S3 gateway to use as cache for GitLab CI pipelines. As it looks like the community activities for the project hasn't picked up so I thought I'd describe my usecase which may be useful as inspiration for someone else. I see a need for this kind of simple S3 gateway for many purposes
I have gitlab runners in a k3s cluster which are managed by ArgoCD. I use the helm chart to deploy s3gw (to namespace gitlab-runner) like this
Chart.yaml:
values.yaml:
Hence I can tell gitlab-runner to use s3gw.gitlab-runner.svc.cluster.local as address. I haven't found how to make gitlab-runner ignore self-signed certificate so I set Insecure=true to make it use http.
Since I only use S3 internally in this namespace I don't want to enable neither ingress nor ui, but that gave me a challenge that I had to create the bucket. I did that by execute a shell on the pod running s3gw and execute the below script to create runners-cache bucket:
The issues I had was that I had to set storageClass.name even though leaving it empty should have selected the default storage class and that 100 Mbyte is reserved as minimum on the storage so when I to begin with set StorageSize: 100Mi then I got quota error whenever trying to put something in the bucket. Other than that it has worked like a charm.
An improvement would be to be able to set a list of buckets in values.yaml that should be created on deploy.
Beta Was this translation helpful? Give feedback.
All reactions