lab/network/egress-test.sh runs an HAProxy on the kind network that answers with the caller's address, used as server.egress.checkUrl. It pins the mta pods to one node, whose address is what kind sends their traffic out from, and checks the event the check leaves in three cases:
the node's address expected: Normal EgressAddress;
another address: Warning EgressMismatch;
a URL that doesn't answer: Warning EgressUnknown, with the install still succeeding.
The lab's token policy now lets the egress check mount its token too (app.kubernetes.io/component: egress-check), as the upgrade Job does. I've already applied it to the kind cluster.
`lab/network/egress-test.sh` runs an HAProxy on the kind network that answers with the caller's address, used as `server.egress.checkUrl`. It pins the mta pods to one node, whose address is what kind sends their traffic out from, and checks the event the check leaves in three cases:
- the node's address expected: `Normal EgressAddress`;
- another address: `Warning EgressMismatch`;
- a URL that doesn't answer: `Warning EgressUnknown`, with the install still succeeding.
All pass with inbuxa/inbuxa-charts#25. The test puts the chart back and removes HAProxy.
The lab's token policy now lets the egress check mount its token too (`app.kubernetes.io/component: egress-check`), as the upgrade Job does. I've already applied it to the kind cluster.
An HAProxy on the kind network answers with the caller's address, as
server.egress.checkUrl. With the mta pods on one node: its address
expected gives a Normal event, another address a Warning, and a checkUrl
that doesn't answer a Warning while the install still succeeds. The lab's
token policy lets the egress check mount its token, as the upgrade Job
does.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
lab/network/egress-test.shruns an HAProxy on the kind network that answers with the caller's address, used asserver.egress.checkUrl. It pins the mta pods to one node, whose address is what kind sends their traffic out from, and checks the event the check leaves in three cases:Normal EgressAddress;Warning EgressMismatch;Warning EgressUnknown, with the install still succeeding.All pass with inbuxa/inbuxa-charts#25. The test puts the chart back and removes HAProxy.
The lab's token policy now lets the egress check mount its token too (
app.kubernetes.io/component: egress-check), as the upgrade Job does. I've already applied it to the kind cluster.