- 
                Notifications
    
You must be signed in to change notification settings  - Fork 492
 
Upgrade Operator to 3.0.1 #201
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
Conversation
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.
Please fix Get Tenant Info:
--- FAIL: Test_TenantInfo (0.00s)
    --- FAIL: Test_TenantInfo/Get_tenant_Info (0.00s)
FAIL
FAIL	github.com/minio/mcs/restapi	13.231s
?   	github.com/minio/mcs/restapi/operations	[no test files]
?   	github.com/minio/mcs/restapi/operations/admin_api	[no test files]
?   	github.com/minio/mcs/restapi/operations/user_api	[no test files]
FAIL
| 
           please also update the kustomize files if needed.  | 
    
| 
           @bexsoft fixed  | 
    
| 
           please make it a single commit  | 
    
4e999db    to
    00836f8      
    Compare
  
    | 
           @cesnietor done  | 
    
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.
please update the yaml permissions accordingly:
{
    "code": 500,
    "message": "tenants.minio.min.io is forbidden: User \"system:serviceaccount:default:mcs-sa\" cannot list resource \"tenants\" in API group \"minio.min.io\" at the cluster scope"
}
| 
           @cesnietor fixed  | 
    
| 
           Socket hangup trying to gather tenant information. (http://localhost:9090/api/v1/namespaces/default/tenants/minio-tenant-4)  | 
    
| 
           Since A tenant can be created without serviceName, it now fails getting Tenant's info: on GET: caused by :  | 
    
| 
           Tenants are never created:  | 
    
| 
           Since this changes will affect UI it needs to also be addressed in this PR.  | 
    
51f7a1c    to
    31616b1      
    Compare
  
    d6cdc7f    to
    0080751      
    Compare
  
    | 
           with the following request the minio pods are never starting:  | 
    
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.
LGTM
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.
please upgrade to v3.0.1
update all other dependent packages
| 
           If I create a Tenant, then I delete it (with its secrets) and then Create it again with the same request: the tenant doesn't start: Request used: steps:  | 
    
          
 Secrets cannot be deleted, secrets are used for encrypting the config and IAM assets in MinIO so it is failing correctly. If you reuse same drives with different credentials. Looks like an operator issue.  | 
    
          
 I meant the k8s secrets that mcs create  | 
    
          
 If the same disks are used, same secrets should be used - I am explaining what is required for MinIO.  | 
    
          
 I will approve this since we can update mcs with this minor bug and update once operator has the fix.  | 
    
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.
Tested, LGTM
| 
           So it a tenant is deleted and somehow new secrets get added it is not allowed to start. https://github.com/minio/minio/tree/master/docs/config#rotating-encryption-with-new-credentials  | 
    
          
 Oh I see.  | 
    


Fixes #199