Let the apiserver reach argocd and longhorn-replica-affinity - #80
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Both gaps showed up as AUDIT verdicts in Hubble while
policyAuditModeis on, so this is traffic that flows today and would stop the moment enforcement goes on.The real bug is the longhorn webhook's 8443 rule: it never matched its own traffic. The admission call arrives SNATed to the node hosting the apiserver, so the identity is
remote-node, notkube-apiserver, and the SYN was auditing. WithfailurePolicy: Ignorethat fails silently, which is exactly what the existing comment warns about.The rest is ingress from
kube-apiserveron argocd and both longhorn-replica-affinity pods, for watch replies that arrive after the conntrack entry ages out mid-stream. Egress to the apiserver was already allowed; only the late retransmit lacks a rule.