Thanks for your response.
I am using a cloud service account (same account that was used to create the workspace) on the cluster properties in case of both the single user cluster and on the shared user cluster. This service account has all the necessary access to the cloud resources (secretsAccessor).
With a single user cluster, i am able to mention the service account and able to access the secrets. I did not have to keep the JSON file of the service key in a secret scope. This means, the cluster is with my user ownership, and i just specified the cloud service account, which enabled me to access the underlying cloud resources.
I was earlier using other type of the cluster called "No Isolation Shared", for this specifying the cloud service account was sufficient.
How does the service account property on the cluster configuration work? does it always need the service account key? or is it only for the Shared user cluster type.