Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -135,9 +135,10 @@ Most routing and policy issues surface in the status of the corresponding Kubern
| The controller cannot translate an `oauthTokenExchange` or `crossAppAccess` backend authentication block | The authentication block is replaced with a marker that rejects every request that uses it. Those requests fail with HTTP `500` and the message `backend authentication failed`, and the gateway does not call the token endpoint. The proxy logs name the cause, such as `oauthTokenExchange configuration is invalid` or `crossAppAccess configuration is invalid`. Requests that do not use the block are not affected. | Fix the field that the condition message names, such as an unsupported `subjectToken.tokenType` value or a missing client authentication Secret. |
| A prompt guard `webhook.backendRef` names a Service that does not exist | The webhook stays in the policy with no target to call. Guarded requests then take the webhook `failureMode`, which is `FailClosed` unless you set it. With `FailOpen`, prompt guarding is skipped instead. | Create the Service or point `backendRef` at one that exists. |
| A remote JWKS is not available yet | The authentication policy keeps an empty key set, `{"keys":[]}`, so the policy trusts no keys. JWT authentication defaults to `Strict` mode, which rejects a request that carries no token and rejects any token that does arrive because no key can verify a signature. | Check that the JWKS endpoint is reachable from the control plane. The controller retries the fetch with a backoff and installs the keys when it succeeds. |
| An inline JWKS contains a key without `kid` or a symmetric `oct` key | The controller still sends the JWT provider to the proxy, but the proxy discards the whole provider. The valid keys in the same JWKS are discarded too. The proxy logs a `failed to create JWT provider` warning, and tokens from that issuer fail validation. The policy status reports the invalid key. | Replace the inline JWKS with keys that include `kid` and use a supported asymmetric key type, such as RSA, EC, or Ed25519. Then reapply the policy. For production, use a remote JWKS endpoint so the identity provider rotates the keys. |
| A CEL expression does not compile | The rest of the policy is kept and the expression is replaced with one that always fails. An `authorization` rule that depends on that replacement therefore allows nothing. | Fix the expression. The condition message names the field, then the expression that did not compile. |

6. Check the condition again. The controller recomputes it on its own when the missing Secret, Service, or key set appears, so you do not need to reapply the resource.
6. Check the condition again. The controller recomputes the condition on its own when the missing Secret, Service, or remote key set appears, so you do not need to reapply the resource. An inline JWKS is different, because the JWKS is part of the policy. Fix the inline JWKS and reapply the policy.

## Inspect the loaded configuration

Expand Down
Loading