Open Brice187 opened 6 months ago
Currently you have to guess how to setup the s3 destination (e.g. add env)
@Brice187 Any chance you could post your solution? I assume we want pointers in ConfigMap and secret key in Secrets, fed in as env's.
As this project seems to be abandoned, I go with the yamls bei cloudlena:
apiVersion: apps/v1
kind: Deployment
metadata:
name: s3manager
spec:
replicas: 1
selector:
matchLabels:
app: s3manager
template:
metadata:
labels:
app: s3manager
spec:
serviceAccountName: s3manager
containers:
- name: s3manager
image: example.com/dockerhub/cloudlena/s3manager:v0.5.0"
imagePullPolicy: IfNotPresent
ports:
- name: http
containerPort: 8080
protocol: TCP
#resources:
# {}
env:
- name: "ENDPOINT"
value: "storage.example.com"
- name: "SKIP_SSL_VERIFICATION"
value: "true"
- name: ACCESS_KEY_ID
valueFrom:
secretKeyRef:
name: s3-credentials
key: accesskey
- name: SECRET_ACCESS_KEY
valueFrom:
secretKeyRef:
name: s3-credentials
key: secretkey
As this project seems to be abandoned, I go with the yamls bei cloudlena:
apiVersion: apps/v1 kind: Deployment metadata: name: s3manager spec: replicas: 1 selector: matchLabels: app: s3manager template: metadata: labels: app: s3manager spec: serviceAccountName: s3manager containers: - name: s3manager image: example.com/dockerhub/cloudlena/s3manager:v0.5.0" imagePullPolicy: IfNotPresent ports: - name: http containerPort: 8080 protocol: TCP #resources: # {} env: - name: "ENDPOINT" value: "storage.example.com" - name: "SKIP_SSL_VERIFICATION" value: "true" - name: ACCESS_KEY_ID valueFrom: secretKeyRef: name: s3-credentials key: accesskey - name: SECRET_ACCESS_KEY valueFrom: secretKeyRef: name: s3-credentials key: secretkey
Thanks, that's helpful. Unfortunately, I really want a helm method so I can use my existing CI/CD tooling & helm would make that far easier.
Currently you have to guess how to setup the s3 destination (e.g. add env)