Reaching orcakey.sh
Unreachable, Unauthorised, Forbidden, NotFound, Incompatible.
These reasons are about the conversation between the operator and orcakey.sh: the path, the token, and what that token is entitled to.
Unreachable
The operator could not reach orcakey.sh at all — DNS, network, TLS, or orcakey.sh being down.
Check spec.host in the resource (or the chart's orcakey.apiBaseUrl), and
whether anything in your cluster restricts outbound traffic. The operator tries
again every resyncSeconds, so this clears on its own once the path is back.
Unauthorised
orcakey.sh refused the service token. It has been revoked, has expired, or was
mistyped when the token Secret was created. The operator does not renew
tokens, so an expired one stays expired.
Mint a replacement and update that Secret. The next sync picks it up; there is
nothing to restart. See Service tokens.
For a resource that sets identity, orcakey.sh refused the cluster's
exchange: the cluster is not registered under this issuer, audience and
service account, or identity.environmentId is not assigned to it. The message
says which checks to make; see
Authenticating as the cluster.
Forbidden
The token is valid and is not entitled to read what it asked for.
It usually appears when the environment holds a value built from a key in another environment. References resolve with the reader’s permission, and a token scoped to one environment is not entitled to another — so the whole reveal is refused rather than the Secret landing with one key missing. The message names the environment it needed. Either widen the token, or keep composed values within the environment a connector reads.
NotFound
The environment does not exist, or this token is not permitted to know that it does. orcakey.sh answers the same way for both, so that a caller cannot discover what exists by asking.
Usually the token's environment has been deleted. Mint a token for an environment that exists.
Incompatible
The operator does not understand the version of the orcakey.sh API it was pointed at. It refuses to start rather than syncing incorrectly, and the log names both versions.
Upgrade the operator, or point it at the right API.