As was done with other services, the Control service has now been renamed using the standard convention, which is the name of the component. The previous service is considered deprecated, still exists, but will be removed in the future. The type of the deprecated one is now ClusterIP, and the new service uses the user specified type.
Breaking change
No, but in a future release the deprecated service will be removed. This is not a breaking change either, unless users are referencing the service name somewhere else. Nothing in the default deployment uses the old service name.
Type of change
[ ] Bug fix (non-breaking change that fixes an issue)
[X] New feature (non-breaking change that adds new functionality)
[ ] Breaking change (bug fix or new feature that breaks existing functionality)
[ ] Third-party dependency update
[ ] Documentation additions or improvements
[ ] Code quality improvements to existing code or test additions/updates
Applicable issues
This change fixes an issue: CORTX-30147
How was this tested?
Deply/destroy cluster. Run status script, S3 I/O and CSM API requests.
Deleted deprecated services and status script reported success.
Deleted non-deprecated services and status script reported failure.
Additional information
Set the cortx.io/deprecated label to these services to help with the status script (to ignore these when checking).
Checklist
[X] The change is tested and works locally.
[ ] New or changed settings in the solution YAML are documented clearly in the README.md file.
Description
As was done with other services, the Control service has now been renamed using the standard convention, which is the name of the component. The previous service is considered deprecated, still exists, but will be removed in the future. The type of the deprecated one is now ClusterIP, and the new service uses the user specified type.
Breaking change
No, but in a future release the deprecated service will be removed. This is not a breaking change either, unless users are referencing the service name somewhere else. Nothing in the default deployment uses the old service name.
Type of change
Applicable issues
How was this tested?
Deply/destroy cluster. Run status script, S3 I/O and CSM API requests.
Deleted deprecated services and status script reported success.
Deleted non-deprecated services and status script reported failure.
Additional information
Set the
cortx.io/deprecatedlabel to these services to help with the status script (to ignore these when checking).Checklist
If this change requires newer CORTX or third party image versions:
imagefields in solution.example.yaml have been updated to use the required versions.appVersionfield of the Helm chart has been updated to use the new CORTX version.If this change addresses a CORTX Jira issue:
CORTX-XXXXX:)