DongHyeonkaandClaude Opus 5
2fa77a899e
Three injections failed first: kube-router keeps reinserting its chain above a hand-placed FORWARD rule, the JGroups connection direction had reversed since A-1, and only the raw table runs ahead of conntrack. Each failure looked like nothing happening. Blocking one direction never partitioned the cluster because JGroups reconnected the other way before failure detection fired. Blocking both produced a real split brain with two coordinators in JGROUPS_PING, yet only the non-coordinator node reported DOWN, so the Service kept an endpoint and the front door stayed at 200. That answers the question A-1 left open. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
19 lines
987 B
Plaintext
19 lines
987 B
Plaintext
=== keycloak-1(수신측)으로 들어가는 7800/57800 만 DROP — kc-lab-1 에 넣는다 ===
|
|
주입: 12:33:58
|
|
|
|
=== [검증] 패킷이 걸리는가 ===
|
|
Chain PREROUTING (policy ACCEPT 0 packets, 0 bytes)
|
|
pkts bytes target prot opt in out source destination
|
|
0 0 DROP 6 -- * * 0.0.0.0/0 10.42.0.42 tcp dpt:57800
|
|
19 2938 DROP 6 -- * * 0.0.0.0/0 10.42.0.42 tcp dpt:7800
|
|
|
|
=== 관찰 ===
|
|
+25초 - | keycloak-0:1/1 keycloak-1:1/1 | 외부 200
|
|
+50초 - | keycloak-0:1/1 keycloak-1:1/1 | 외부 200
|
|
+75초 - | keycloak-0:1/1 keycloak-1:0/1 | 외부 200
|
|
+100초 - | keycloak-0:1/1 keycloak-1:1/1 | 외부 200
|
|
+125초 - | keycloak-0:1/1 keycloak-1:1/1 | 외부 200
|
|
+150초 - | keycloak-0:1/1 keycloak-1:1/1 | 외부 200
|
|
+175초 - | keycloak-0:1/1 keycloak-1:1/1 | 외부 200
|
|
+200초 - | keycloak-0:1/1 keycloak-1:1/1 | 외부 200
|