Kubernetes helm chart: trying to automate 100% #678
Labels
No labels
action
check-aws
action
discussion-needed
action
for-external-contributors
action
for-newcomers
action
more-info-needed
action
need-funding
action
triage-required
kind
correctness
kind
ideas
kind
improvement
kind
performance
kind
testing
kind
usability
kind
wrong-behavior
prio
critical
prio
low
scope
admin-api
scope
background-healing
scope
build
scope
documentation
scope
k8s
scope
layout
scope
metadata
scope
ops
scope
rpc
scope
s3-api
scope
security
scope
telemetry
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: Deuxfleurs/garage#678
Loading…
Add table
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Hello
Im trying to automate the garage installation with helm chart 100%
What that means that I writting a python/bash script that run after the helm installation and with predefined secrets+passwords+and endpoints, he will create new layout, buckets, users, etc
The problem I encountering that the instances is generating keys
What should I do then ? How can I know beforehand the keys(ids) ?
Thanks !
Why can't you use the admin API to retrieve the keys when they are generated, and then inject that in your kubernetes configuration database?
Otherwise, there is the
garage key import
/ ImportAccessKey functionnality to add an existing access key/secret key pair to Garage. They have to be formatted properly, i.e. be generated by another Garage instance.@lx
I mean the nodes id's , in order to create new layout:
how do i get the ids?
e0341ceea1f3f2dd4b37b079db96a19de37b94d4351d3de4990e543fb3974590
9e1b3f63e1da2b721d61d0d4dbd907b765b0f2be495543315c993de36c049e32
b36f6a694f6740cdf5a48f8c4cbc71582616792730241b0f51d1506c74e9a6b9
currently im getting those ID's manually from the logs
found what needed:
thanks!