-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(local): install minio object storage via helm chart #1080
Conversation
@@ -0,0 +1,19 @@ | |||
existingSecret: minio-credentials |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Slightly twisted: this create a root user off the k8s secret of the given name.
|
||
resources: | ||
requests: | ||
memory: 0.5Gi |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Same here: does this create problems for others?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
works well for me
It would also be possible to create an ingress for the service which exposes an administration UI, but I'm not sure this is currently needed? |
This can be tested in conjunction with wmde/wbaas-backup#24 and wbstack/charts#125 using diff --git a/k8s/helmfile/env/local/wbaas-backup.values.yaml.gotmpl b/k8s/helmfile/env/local/wbaas-backup.values.yaml.gotmpl
index 8d9459c..47cd659 100644
--- a/k8s/helmfile/env/local/wbaas-backup.values.yaml.gotmpl
+++ b/k8s/helmfile/env/local/wbaas-backup.values.yaml.gotmpl
@@ -6,8 +6,15 @@ job:
successfulJobsHistoryLimit: 1
cronSchedule: "* * 1 1 *"
+scratchDiskSpace: 4Gi
+
+restorePodRunning: false
+
storage:
- scratchDiskSpace: 4Gi
- gcs:
- bucketName: nacho-cheese
- uploadToBucket: false
+ bucketName: backups
+ uploadToBucket: true
+ accessKeySecretName: minio-credentials
+ accessKeySecretKey: rootUser
+ secretKeySecretName: minio-credentials
+ secretKeySecretKey: rootPassword
+ endpoint: http://minio.default.svc.cluster.local:9000
diff --git a/k8s/helmfile/helmfile.yaml b/k8s/helmfile/helmfile.yaml
index ed21617..61eb86e 100644
--- a/k8s/helmfile/helmfile.yaml
+++ b/k8s/helmfile/helmfile.yaml
@@ -210,7 +210,7 @@ releases:
- name: wbaas-backup
namespace: default
- chart: wbstack/wbaas-backup
+ chart: ./../../../charts/charts/wbaas-backup
version: 0.0.6
<<: *default_release |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
worked beautifully locally
Ticket https://phabricator.wikimedia.org/T343112
This is prep work for moving backup transfer over to an S3 client. As of this PR, there are no consumers of the MinIO service.
How to test/use this locally
minio
service to become ready