The cluster and the resource
NamespaceNotAllowed, TokenMissing, Misconfigured, KubernetesError.
These reasons are about where the resource is allowed to reach and what it asked for. The fix is in your cluster or in the file, not in orcakey.sh.
NamespaceNotAllowed
The resource is outside orcakey-operator and names another namespace in
tokenSecret.namespace or managedSecret.namespace. Only a resource in
orcakey-operator may do that; see
What it may do.
Nothing is read or written. Move the resource to orcakey-operator, or create
it in the namespace it names.
A resource that sets identity reports the same reason anywhere outside
orcakey-operator, whatever it names: only the operator's namespace may
authenticate as the cluster. Move it there, or use a tokenSecret. See
Authenticating as the cluster.
TokenMissing
The Secret named in tokenSecret does not exist, or has no non-empty value
under its key. The key defaults to serviceToken; a token Secret made for a
0.x OrcaKeySync used token. The message names the Secret and the key.
Create the Secret or fix the key. The next resync picks it up.
Misconfigured
The operator does not know which orcakey.sh API to call: the resource has no
spec.host and the chart has no orcakey.apiBaseUrl. Set one of them.
For a resource that sets identity, it also means no service-account token is
mounted at /var/run/secrets/orcakey.sh/identity/token. Chart 1.0.1 always
mounts one; an operator deployed some other way has to mount it too.
KubernetesError
The Kubernetes API refused a call, usually reading the token Secret or
writing the managed one. The message carries the HTTP status. A 403 means the
operator's ClusterRole is missing or was changed.