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

Allow waypoint by default very hard to debug #50870

Open
linsun opened this issue May 6, 2024 · 1 comment
Open

Allow waypoint by default very hard to debug #50870

linsun opened this issue May 6, 2024 · 1 comment

Comments

@linsun
Copy link
Member

linsun commented May 6, 2024

(This is used to request new product features, please visit https://github.com/istio/istio/discussions for questions on using Istio)

Describe the feature request

Spent an hour debugging why sleep can't access productpage via its bookinfo gateway. Still not sure why but it is related to the allow waypoint by default because the productpage's ztunnel denied the req as I don't have any L4 authz policy deployed myself. The auto added policies are hard to reason about:

 istioctl x ztunnel-config policy -o yaml
- action: Allow
  name: istio_allow_waypoint_default_bookinfo-gateway
  namespace: default
  rules:
  - - - principals:
        - Exact: cluster.local/ns/default/sa/bookinfo-gateway-istio
  scope: WorkloadSelector
- action: Allow
  name: istio_allow_waypoint_default_reviews-svc-waypoint
  namespace: default
  rules:
  - - - principals:
        - Exact: cluster.local/ns/default/sa/reviews-svc-waypoint
  scope: WorkloadSelector
- action: Allow
  name: istio_allow_waypoint_default_reviews-v2-pod-waypoint
  namespace: default
  rules:
  - - - principals:
        - Exact: cluster.local/ns/default/sa/reviews-v2-pod-waypoint
  scope: WorkloadSelector
- action: Allow
  name: istio_allow_waypoint_default_waypoint
  namespace: default
  rules:
  - - - principals:
        - Exact: cluster.local/ns/default/sa/waypoint
  scope: WorkloadSelector

Disabled the feature and things start to work.

Describe alternatives you've considered

Affected product area (please put an X in all that apply)

[x ] Ambient
[ ] Docs
[ ] Dual Stack
[ ] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Extensions and Telemetry
[ ] Security
[ ] Test and Release
[x ] User Experience
[ ] Developer Infrastructure

Affected features (please put an X in all that apply)

[ ] Multi Cluster
[ ] Virtual Machine
[ ] Multi Control Plane

Additional context

@keithmattix
Copy link
Contributor

Good call out Lin! We should address this before 1.22 if at all possible

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants