WHAT

We need to expose an endpoint to register customer owned clusters with the Fleet Manager.

WHY

Initially the registration will be manual. The reasons for this are:

1. The installation process itself is manual
2. The cluster needs to be registered in the KFM database before the customer can proceed to run the installation script.

HOW

Expose a new endpoint in the fleet manager. It has to be a public endpoint becaues it will be eventually called by the customer using curl or a screen in the UI.

The endpoint should accept POST requests and require the following parameters to be passed:

• Cluster ID (ocm ID, used in ocm API calls)
• External ID (ocm external ID, identifies the cluster in metrics)
• Cluster DNS

The endpoint should return the following response (as a JSON object):

• All Add-On parameters for FSO: https://github.com/bf2fc6cc711aee1a0c2a/kas-fleet-manager/blob/main/internal/kafka/internal/services/kas_fleetshard_operator_addon.go#L156
• All parameters for the Observability Stack: https://github.com/bf2fc6cc711aee1a0c2a/kas-fleet-manager/blob/main/internal/kafka/internal/workers/cluster_mgrs/clusters_mgr.go#L781, except the logging client and the auth type.

We need to know if a cluster is an enterprise cluster. For this we'll add two additional columns to the clusters table:

• cluster_type: hardcoded to enterprise
• org_id: used to ensure that a customer doesn't provision instances on a cluster they don't own

Enterprise clusters should not be terraformed, they need to be skipped in all reconcilers by checking for the enterprise cluster type.

Details about the endpoint (url) and what additional changes it needs to make are documented here: https://docs.google.com/document/d/1UNTG5QTJZPXCsekkCzLgnO1NujxmIDXeRfFEz7jiKDA

DONE

Include the following where applicable:

• Endpoint created and tested

Guidelines

The following steps should be adhered to:

• Required tests should be put in place - unit, integration, manual test cases (if necessary)
• CI and all relevant tests passing
• Changes have been verified by one additional reviewer against:
• each required environment
• each supported upgrade path
• If the changes could have an impact on the clients (either UI or CLI), a JIRA should be created for making the required changes on the client side and acknowledged by one of the client side team members. PR has been merged