-
Notifications
You must be signed in to change notification settings - Fork 135
DOCS-2798: Deploy Istio Ambient Mode on your cluster #2431
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
Conversation
✅ Deploy Preview for calico-docs-preview-next ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview succeeded!Built without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify project configuration. |
5a151d3 to
8ddc9ed
Compare
8ddc9ed to
98dbe35
Compare
98dbe35 to
6073767
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Copilot encountered an error and was unable to review this pull request. You can try again by re-requesting a review.
calico-enterprise_versioned_docs/version-3.22-2/compliance/istio/deploy-istio-ambient.mdx
Show resolved
Hide resolved
radixo
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Lovely material, just one waypoint concept to fix.
| This modification allows existing Calico and Kubernetes network policies to continue functioning exactly as they did before, without needing any rewrites, even though the traffic is now encrypted with mTLS. | ||
|
|
||
| These zTunnel enhancements are not compatible with Istio's application-layer Waypoint proxy. | ||
| If you deploy Waypoint, the reported destination ports will follow the original behavior (always port 15008), and you will need to modify existing network policies. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| If you deploy Waypoint, the reported destination ports will follow the original behavior (always port 15008), and you will need to modify existing network policies. | |
| If you deploy Waypoint, the reported destination ports will follow the original behavior (always port 15008), and you will need to allow the traffic to/from waypoint with the destination port 15008. |
probably the way I suggested here is not the best, but the idea is. The network policies needs to have to include the port 15008 for traffic coming from the waypoint (L7 filtered only).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, I've changed the language here.
| * Istio Ambient Mode does not work together with [workload-based web application firewalls](../../threat/web-application-firewall.mdx). | ||
| * The service mesh is not supported for use on clusters that are also part of a [cluster mesh](../../multicluster/index.mdx). | ||
| * Destination ports are preserved only when Istio is deployed without Waypoint. | ||
| If you deploy Waypoint, all traffic in the mesh will show port 15008 as its destination port. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| If you deploy Waypoint, all traffic in the mesh will show port 15008 as its destination port. | |
| If you deploy Waypoint, all traffic through waypoints will show port 15008 as its destination port. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done.
DOCS-2798
6073767 to
72aa35e
Compare

Product Version(s):
Issue:
Link to docs preview:
https://deploy-preview-2431--tigera.netlify.app/calico-enterprise/3.22/compliance/istio/about-istio-ambient
SME review:
DOCS review:
Additional information:
Merge checklist: