Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update troubleshooting doc for policy restriction #2420

Merged
merged 1 commit into from
Aug 20, 2024
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
19 changes: 19 additions & 0 deletions site/content/how-to/monitoring/troubleshooting.md
Original file line number Diff line number Diff line change
Expand Up @@ -436,6 +436,25 @@ To **resolve** this, you can do one of the following:

- Adjust the IPFamily of your Service to match that of the NginxProxy configuration.

##### Policy cannot be applied to target

If you `describe` your Policy and see the following error:

```text
Conditions:
Last Transition Time: 2024-08-20T14:48:53Z
Message: Policy cannot be applied to target "default/route1" since another Route "default/route2" shares a hostname:port/path combination with this target
Observed Generation: 3
Reason: TargetConflict
Status: False
Type: Accepted
```

This means you are attempting to attach a Policy to a Route that has an overlapping hostname:port/path combination with another Route. To work around this, you can do one of the following:

- Combine the Route rules for the overlapping path into a single route.
- If the Policy allows it, specify both Routes in the `targetRefs` list.

### Further reading

You can view the [Kubernetes Troubleshooting Guide](https://kubernetes.io/docs/tasks/debug/debug-application/) for more debugging guidance.
Loading