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 update the exposeServices flags to false, the services type should change to ClusterIP.
Current Behavior
During creation of a tenant that have exposed services (see tenant manifest below), it creates the services as type LoadBalancer, which is a correct and desired result.
However, when we update the flags to false, the services are not updated to type ClusterIP.
Possible Solution
Probably Operator is only recognizing the flags on creation time and ignore them on sync time, triage would find if the flag is ignored, or operator fails to execute the change for some reason.
Steps to Reproduce (for bugs)
Create a tenant on Operator UI
Set the flags exposeServices.console: true, exposeServices.minio=true
Vrify the services minio and namespace-console are of type LoadBalancer
Edit the tenant on Operator UI
Set the flags exposeServices.console: false,exposeServices.minio=false
Verify the services minio and namespace-console have not changed from LoadBalancer to ClusterIP
Context
Regression
No
Your Environment
Version used (minio-operator): 4.5.2
Environment name and version (e.g. kubernetes v1.17.2): 1.20
Server type and version:
Operating System and version (uname -a): Linux minio-tenant-1-pool-0-0 #redacted#.amzn2.x86_64 #1 SMP Wed Aug 31 00:09:52 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
Expected Behavior
When we update the exposeServices flags to false, the services type should change to ClusterIP.
Current Behavior
During creation of a tenant that have exposed services (see tenant manifest below), it creates the services as type LoadBalancer, which is a correct and desired result.
However, when we update the flags to false, the services are not updated to type ClusterIP.
Possible Solution
Probably Operator is only recognizing the flags on creation time and ignore them on sync time, triage would find if the flag is ignored, or operator fails to execute the change for some reason.
Steps to Reproduce (for bugs)
exposeServices.console: true
,exposeServices.minio=true
minio
andnamespace-console
are of type LoadBalancerexposeServices.console: false
,exposeServices.minio=false
minio
andnamespace-console
have not changed from LoadBalancer to ClusterIPContext
Regression
No
Your Environment
minio-operator
): 4.5.2uname -a
):Linux minio-tenant-1-pool-0-0 #redacted#.amzn2.x86_64 #1 SMP Wed Aug 31 00:09:52 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
The text was updated successfully, but these errors were encountered: