Business Problem:

Customers installing Secured Cluster Services on a remote Kube cluster (i.e., not the cluster where Central is installed) often make mistakes in specifying the endpoint for Central. The Operator UI and Helm should prevent simple errors and the Sensor should be more tolerant of slight errors.

When this value is not correct, the error can only be discovered after deploying Secured Cluster and it is difficult to pinpoint the source of the error.

Use Cases:

1. Customer leaves the Central endpoint unspecified in a cluster where Central is not installed. Since this configuration can never work, Operator should detect that this cluster does not have Central and make the entry required. Help text for the field should tell the user where to find this information for both self-managed and cloud service)
2. Customer fails to specify a port in endpoint field. Operator UI should detect and prevent this, or automatically append :443. Operator, Helm, Sensor and any other components that use this value, should append :443 if the port is not specified.
3. Customer enters the endpoint with a protocol, e.g., "https://central.example.com" - Operator UI should detect and prevent, or remove the protocol. Any component that consumes the endpoint value should tolerate this and remove the protocol if necessary. (Note that specifying protocol wss:// is expected)
4. Operator or other UIs should strive to detect and
5. roxctl should have similar resilience to minor errors in specifying the Central endpoint (extraneous protocol, missing port, etc)
6. If the error cannot be automatically corrected, it should be as easy as possible to pinpoint the reason for the failure. For Sensor, this used to be very clear from the logs and from the Pod crashing; recent versions don't crash and the log message for inability to contact the endpoint gets lost.

1. [Attach any relevant documents, research, or supporting materials that provide additional context or information]