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

istio mTLS causes issue #2851

Closed
aviramha opened this issue Oct 16, 2024 · 3 comments · Fixed by #2853
Closed

istio mTLS causes issue #2851

aviramha opened this issue Oct 16, 2024 · 3 comments · Fixed by #2853
Assignees

Comments

@aviramha
Copy link
Member

aviramha commented Oct 16, 2024

Mirantis Kubernetes Engine k8s 1.24
istio mesh with istio-cni

Health checks are received well and plain text by mirrord, but it also receives some TLS traffic that looks destined to the mTLS/istio (i.e before TLS termination)

Copy link

linear bot commented Oct 16, 2024

@aviramha aviramha closed this as not planned Won't fix, can't repro, duplicate, stale Oct 16, 2024
@aviramha aviramha reopened this Oct 16, 2024
@aviramha
Copy link
Member Author

reproduced using this istio installation config:

apiVersion: install.istio.io/v1alpha1
kind: IstioOperator
spec:
  profile: demo
  components:
    cni:
      namespace: istio-system
      enabled: true
    ingressGateways:
      - name: istio-ingressgateway
        enabled: false
    egressGateways:
      - name: istio-egressgateway
        enabled: false

and following https://istio.io/latest/docs/setup/getting-started/

@aviramha
Copy link
Member Author

So in this case, the agent doesn't see the istio iptables (since not in the same namespace) and it just initializes in a standard way. It steals traffic from PREROUTING (the mesh), but if I remove the rule there it seems to be okay.

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

Successfully merging a pull request may close this issue.

1 participant