-
Notifications
You must be signed in to change notification settings - Fork 50
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
[PVCs]
Create public documentation for data backups and restoration
#882
Comments
Thank you for reporting us your feedback! The internal ticket has been created: https://warthogs.atlassian.net/browse/KF-5599.
|
In the first iteration of the guide, it instructs users to have a config for Our Charm though right now sets an empty value for the This urged me to change the password in MinIO (although we dropped this approach, since it's bad UX to expect users to change the password to make a backup) but then stumbled upon the issue that the KFP Profile Operator will not correctly propagate the minio The above resulted in the following errors in the UI and
|
To rewrite the instructions we have and tell users which MinIO For now we'll use the following command for getting the juju show-unit kfp-ui/0 \
| yq '.kfp-ui/0.relation-info.[] | select (.endpoint == "object-storage") | .application-data.data' \
| yq '.secret-key' Note that the above command is not targeting MinIO, which is the producer, but a consumer. This was because we couldn't find a way to get this outgoing value from MinIO. |
Then, I've created some follow-up issues so that in the future we move this backup/restore logic to the Charms |
Context
We need to create public documentation for users that want to backup their data and restore from it.
What needs to get done
Create a section in this discourse post with information about data backup and restoration for charms that use PVCs (
mlmd
andminio
).Definition of Done
A section in the discourse post that exposes information about backup and restoration for PVCs used in CKF.
The text was updated successfully, but these errors were encountered: