-
Notifications
You must be signed in to change notification settings - Fork 456
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
Tenant update doesnt do anything #384
Comments
Hi @olevitt, it usually takes some time to see the rolling update, we first perform a hot update of MinIO and then we perform the rolling update. Does you kubernetes cluster has connectivity to the internet or is it restricted in any form? If we fail to download the updated MinIO image we may run into a problem, I want to confirm you are not experiencing this behavior |
Hi ! The operator logs looks more promising :
And When I uninstall and reinstall the operator, I still have no service created :
I don't know how to get the version of the kubectl minio plugin I'm using but I should be using the latest as I installed it yesterday. |
Looks like tenants cannot talk back to the operator here - perhaps your network policies? |
I don't have any network policies enforced. To me it looks like DNS resolution failure which is understandable as the service (which is linked to the |
there's a log error
I think this is the root cause, will investigate further |
Me and @zachomedia looked at this and @zachomedia wrote a patch the problem is when MinIO changed the base image from alpine to UBI and the getArtifacts call calling the largest layer no longer works to retrieve the MinIO binary files. |
@sylus feel free to send a PR |
Expected Behavior
When updating a tenant configuration (using either kubectl apply or kubectl edit), I expected minio-operator to process the new configuration and restart the pods.
Current Behavior
Modifying anything (tried with modifying env variables and minio image) does not do anything, even after killing the operator.
The text was updated successfully, but these errors were encountered: