Failing to delete a managed flex gateway on RTF

SYMPTOM

Deleting a Managed Flex Gateway on Runtime Fabric (RTF) fails and does not complete. Inspecting the browser network trace (HAR file), the DELETE request for the gateway ID returns a payload similar to:

"status": 500, "message": "Unexpected error: Request failed with status code 400"

CAUSE

The RTF agent cannot finalize the deletion because the ManagedFlexGateway CRD support is not enabled (global.crds.flex.enabled).

SOLUTION

Ensure the prerequisite is met by enabling the ManagedFlexGateway resource on the RTF agent.

Once the prerequisites are done, the gateway can be deleted via the GUI. If you see any warnings/errors, refresh the page and confirm the outcome.