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.

Sign up for GitHub

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

Jump to bottom

If exportTo includes workload's current namespace (not '.'), other namespaces are ignored from ExportTo. #48349

Closed
3 of 17 tasks
kimmikimmi opened this issue Dec 14, 2023 · 0 comments · Fixed by #48312
Closed
3 of 17 tasks

If exportTo includes workload's current namespace (not '.'), other namespaces are ignored from ExportTo. #48349

kimmikimmi opened this issue Dec 14, 2023 · 0 comments · Fixed by #48312

Comments

@kimmikimmi
Copy link
Contributor

Is this the right place to submit this?

  • This is not a security vulnerability or a crashing bug
  • This is not a question about how to use Istio

Bug Description

If exportTo includes workload's current namespace (not '.'), other namespaces are ignored from ExportTo.

e.g.
DR1

namespace: ns1
exportTo: [a, b, ns1]

ns1 istio proxy is able to sync subsets of destination rule.
However, a,b istio proxies could not able to sync subsets of destination rule.

Version

1.20

Additional Information

No response

Affected product area

  • Ambient
  • Docs
  • Dual Stack
  • Installation
  • Networking
  • Performance and Scalability
  • Extensions and Telemetry
  • Security
  • Test and Release
  • User Experience
  • Developer Infrastructure
  • Upgrade
  • Multi Cluster
  • Virtual Machine
  • Control Plane Revisions
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fix ExportTo behavior if workload's namespace is included kimmikimmi/istio
1 participant
@kimmikimmi