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
When we change the MinIO secret-key config option, the KFP Profiles Operator will not
Update the mlpipeline-minio-artifact K8s Secret, in the user namespace
Restart the ml-pipeline-ui-artifact Deployment's pod, to get the new value for the secret
The above results in seeing the following error in the KFP UI, when trying to download the artifacts of an already finished Pipeline (that live in S3)
Failed to get object in bucket: S3Error: The request signature we calculated does not match the signature you provided. Check your key and signing method.
These logs are coming from the ml-pipeline-ui-artifact pod in the user's namespace, which is responsible for fetching the minio artifacts. But because now MinIO has different credentials and that pod has still the outdated once it then fails to get the artifacts
To Reproduce
Deploy CKF 1.8
Run the data-passing pipeline, which creates some artifacts in MinIO
juju config minio secret-key=minio123
Go to the KFP UI and click on the step that produced a Dataset or Model artifact and try to download them from the minio link in the UI
To confirm the user namespaced MinIO credentials are incorrect you can do:
kubectl get secret -n admin mlpipeline-minio-artifact -o yaml
Decode the hash, and it'll be a radom value (which is the initial secret-key since the config option is initially empty)
Environment
CKF 1.8
Relevant Log Output
# From the `ml-pipeline-ui-artifact` pod in the user namespace:
Failed to get object in bucket: S3Error: The request signature we calculated does not match the signature you provided. Check your key and signing method.
### Additional Context
_No response_
The text was updated successfully, but these errors were encountered:
kimwnasptd
changed the title
KFP Profiles Operator doesn't update MinIO's credentials if we update them
KFP Profiles Operator doesn't update MinIO's credentials if updated in MinIO's config
May 2, 2024
Bug Description
When we change the MinIO
secret-key
config option, the KFP Profiles Operator will notmlpipeline-minio-artifact
K8s Secret, in the user namespaceml-pipeline-ui-artifact
Deployment's pod, to get the new value for the secretThe above results in seeing the following error in the KFP UI, when trying to download the artifacts of an already finished Pipeline (that live in S3)
These logs are coming from the
ml-pipeline-ui-artifact
pod in the user's namespace, which is responsible for fetching the minio artifacts. But because now MinIO has different credentials and that pod has still the outdated once it then fails to get the artifactsTo Reproduce
data-passing
pipeline, which creates some artifacts in MinIOjuju config minio secret-key=minio123
Dataset
orModel
artifact and try to download them from the minio link in the UITo confirm the user namespaced MinIO credentials are incorrect you can do:
kubectl get secret -n admin mlpipeline-minio-artifact -o yaml
secret-key
since the config option is initially empty)Environment
CKF 1.8
Relevant Log Output
The text was updated successfully, but these errors were encountered: