discuss: why set `apisix.enabled: true` to enable Control API service

I was trying to enable the control API service and noticed that while `control.enabled: true` is the default in helm values, I cannot see the Control API service (unlike Admin API, where `apisix.admin.enabled: true` will enable Admin API service https://github.com/apache/apisix-helm-chart/blob/master/charts/apisix/templates/service-admin.yaml#L16).

Found https://github.com/apache/apisix-helm-chart/blob/master/charts/apisix/templates/service-control.yaml#L16 and realized I had to set `apisix.enabled: true` in the values file in addition, then I was able to see the Control API service:


It is not exactly straightforward why `apisix.enabled: true` is necessary. The PR that added the feature is https://github.com/apache/apisix-helm-chart/pull/739

Opening this issue for a discussion. My personal take is setting `apisix.control.enabled: true` would be more straightforward to enable control API service.

Start by comparing charts/apisix/templates/service-control.yaml with service-admin.yaml and the referenced Helm values, then review pull request #739 for the intended control API design. This issue has no settled implementation; done requires an agreed enabling behavior and corresponding chart changes that make the resulting Control API service predictable.

Written by the indexing model from the issue text.