When KIC is configured to use a single workspace and does not have the permission to access GET /status, KIC fails to create the workspaced client

[randmonkey]

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

From FTI-6415.
Since KIC 2.11, The client will first run a GET /status to detect whether Kong gateway is ready to accept configuration, then create a workspaced client after the detect succeeded. So when KIC does not have the permission to access the GET /status (For example, It only have the admin permission in the configured workspace), the client can never be created.

Expected Behavior

When KIC only have permission of a single workspace, It should be OK to work with the workspace with workspace configured.

Steps To Reproduce

1. Deploy Kong gateway and create a workspace, like test
2. Create a token with super-admin permission in the single workspace created in (1)
3. Deploy KIC with workspace set to the workspace created in (1) and kong-admin-token set to the token in (2)

Kong Ingress Controller version

Since 2.11

Kubernetes version

Not relevant

Anything else?

No response