apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-25T13:11:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-184-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-184.ec2.internal uid: 0ba98818-36e9-45db-a485-6a8b1b6dd51b resourceVersion: "21523" uid: 53919d3f-d995-4274-b762-c545801a41da spec: sourcePod: network-check-source-7f44b6dd87-q4zcf targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-05-25T13:18:44Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 945.568µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:32:44Z" - latency: 818.26µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:31:44Z" - latency: 720.252µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:30:44Z" - latency: 899.265µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:29:44Z" - latency: 1.042797ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:28:44Z" - latency: 906.642µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:27:44Z" - latency: 952.35µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:26:44Z" - latency: 1.055281ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:25:44Z" - latency: 1.175678ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:24:44Z" - latency: 916.3µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:23:44Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-25T13:11:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-184-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-184.ec2.internal uid: 0ba98818-36e9-45db-a485-6a8b1b6dd51b resourceVersion: "19885" uid: da4cda8d-21dc-4c8a-8fe5-d4867209ae32 spec: sourcePod: network-check-source-7f44b6dd87-q4zcf targetEndpoint: ac0337ff72d2b40b09d9548f4a0d0d0c-112719f2556e485e.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-25T13:17:44Z" message: 'load-balancer-api-external: tcp connection to ac0337ff72d2b40b09d9548f4a0d0d0c-112719f2556e485e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.851949ms message: 'load-balancer-api-external: tcp connection to ac0337ff72d2b40b09d9548f4a0d0d0c-112719f2556e485e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:29:44Z" - latency: 7.743036ms message: 'load-balancer-api-external: resolved host name ac0337ff72d2b40b09d9548f4a0d0d0c-112719f2556e485e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-25T13:29:44Z" - latency: 4.700406ms message: 'load-balancer-api-external: tcp connection to ac0337ff72d2b40b09d9548f4a0d0d0c-112719f2556e485e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:28:44Z" - latency: 8.392571ms message: 'load-balancer-api-external: resolved host name ac0337ff72d2b40b09d9548f4a0d0d0c-112719f2556e485e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-25T13:28:44Z" - latency: 5.146875ms message: 'load-balancer-api-external: tcp connection to ac0337ff72d2b40b09d9548f4a0d0d0c-112719f2556e485e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:27:44Z" - latency: 7.401435ms message: 'load-balancer-api-external: resolved host name ac0337ff72d2b40b09d9548f4a0d0d0c-112719f2556e485e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-25T13:27:44Z" - latency: 4.314004ms message: 'load-balancer-api-external: tcp connection to ac0337ff72d2b40b09d9548f4a0d0d0c-112719f2556e485e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:26:44Z" - latency: 8.521592ms message: 'load-balancer-api-external: resolved host name ac0337ff72d2b40b09d9548f4a0d0d0c-112719f2556e485e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-25T13:26:44Z" - latency: 4.928843ms message: 'load-balancer-api-external: tcp connection to ac0337ff72d2b40b09d9548f4a0d0d0c-112719f2556e485e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:25:44Z" - latency: 8.998581ms message: 'load-balancer-api-external: resolved host name ac0337ff72d2b40b09d9548f4a0d0d0c-112719f2556e485e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-25T13:25:44Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-25T13:11:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-184-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-184.ec2.internal uid: 0ba98818-36e9-45db-a485-6a8b1b6dd51b resourceVersion: "19884" uid: c5d344a5-440a-408d-9172-e29055758de9 spec: sourcePod: network-check-source-7f44b6dd87-q4zcf targetEndpoint: ac0337ff72d2b40b09d9548f4a0d0d0c-112719f2556e485e.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-25T13:17:44Z" message: 'load-balancer-api-internal: tcp connection to ac0337ff72d2b40b09d9548f4a0d0d0c-112719f2556e485e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.024173ms message: 'load-balancer-api-internal: tcp connection to ac0337ff72d2b40b09d9548f4a0d0d0c-112719f2556e485e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:29:44Z" - latency: 7.686023ms message: 'load-balancer-api-internal: resolved host name ac0337ff72d2b40b09d9548f4a0d0d0c-112719f2556e485e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-25T13:29:44Z" - latency: 4.597922ms message: 'load-balancer-api-internal: tcp connection to ac0337ff72d2b40b09d9548f4a0d0d0c-112719f2556e485e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:28:44Z" - latency: 8.432703ms message: 'load-balancer-api-internal: resolved host name ac0337ff72d2b40b09d9548f4a0d0d0c-112719f2556e485e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-25T13:28:44Z" - latency: 4.289678ms message: 'load-balancer-api-internal: tcp connection to ac0337ff72d2b40b09d9548f4a0d0d0c-112719f2556e485e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:27:44Z" - latency: 7.320332ms message: 'load-balancer-api-internal: resolved host name ac0337ff72d2b40b09d9548f4a0d0d0c-112719f2556e485e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-25T13:27:44Z" - latency: 4.323543ms message: 'load-balancer-api-internal: tcp connection to ac0337ff72d2b40b09d9548f4a0d0d0c-112719f2556e485e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:26:44Z" - latency: 8.554532ms message: 'load-balancer-api-internal: resolved host name ac0337ff72d2b40b09d9548f4a0d0d0c-112719f2556e485e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-25T13:26:44Z" - latency: 4.789161ms message: 'load-balancer-api-internal: tcp connection to ac0337ff72d2b40b09d9548f4a0d0d0c-112719f2556e485e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:25:44Z" - latency: 9.04886ms message: 'load-balancer-api-internal: resolved host name ac0337ff72d2b40b09d9548f4a0d0d0c-112719f2556e485e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-25T13:25:44Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-25T13:11:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-184-to-network-check-target-ip-10-0-132-184 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-184.ec2.internal uid: 0ba98818-36e9-45db-a485-6a8b1b6dd51b resourceVersion: "21520" uid: 81fea9cf-abcc-4fe3-88cc-f1ec196a8da1 spec: sourcePod: network-check-source-7f44b6dd87-q4zcf targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-05-25T13:18:44Z" message: 'network-check-target-ip-10-0-132-184: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.336877ms message: 'network-check-target-ip-10-0-132-184: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:32:44Z" - latency: 1.044033ms message: 'network-check-target-ip-10-0-132-184: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:31:44Z" - latency: 839.006µs message: 'network-check-target-ip-10-0-132-184: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:30:44Z" - latency: 1.054676ms message: 'network-check-target-ip-10-0-132-184: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:29:44Z" - latency: 1.129565ms message: 'network-check-target-ip-10-0-132-184: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:28:44Z" - latency: 819.027µs message: 'network-check-target-ip-10-0-132-184: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:27:44Z" - latency: 977.612µs message: 'network-check-target-ip-10-0-132-184: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:26:44Z" - latency: 719.019µs message: 'network-check-target-ip-10-0-132-184: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:25:44Z" - latency: 939.233µs message: 'network-check-target-ip-10-0-132-184: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:24:44Z" - latency: 882.008µs message: 'network-check-target-ip-10-0-132-184: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:23:44Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-25T13:11:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-184-to-network-check-target-ip-10-0-135-64 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-184.ec2.internal uid: 0ba98818-36e9-45db-a485-6a8b1b6dd51b resourceVersion: "21522" uid: f23f1a19-fbf8-4b2e-924e-556c01fffc29 spec: sourcePod: network-check-source-7f44b6dd87-q4zcf targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-05-25T13:18:44Z" message: 'network-check-target-ip-10-0-135-64: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.220779ms message: 'network-check-target-ip-10-0-135-64: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:32:44Z" - latency: 1.673462ms message: 'network-check-target-ip-10-0-135-64: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:31:44Z" - latency: 1.758388ms message: 'network-check-target-ip-10-0-135-64: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:30:44Z" - latency: 2.163539ms message: 'network-check-target-ip-10-0-135-64: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:29:44Z" - latency: 1.98364ms message: 'network-check-target-ip-10-0-135-64: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:28:44Z" - latency: 2.071689ms message: 'network-check-target-ip-10-0-135-64: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:27:44Z" - latency: 1.844537ms message: 'network-check-target-ip-10-0-135-64: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:26:44Z" - latency: 2.200242ms message: 'network-check-target-ip-10-0-135-64: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:25:44Z" - latency: 2.059239ms message: 'network-check-target-ip-10-0-135-64: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:24:44Z" - latency: 1.940839ms message: 'network-check-target-ip-10-0-135-64: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:23:44Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-25T13:11:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-184-to-network-check-target-ip-10-0-142-251 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-184.ec2.internal uid: 0ba98818-36e9-45db-a485-6a8b1b6dd51b resourceVersion: "21521" uid: d2f28b95-f7b6-4ba6-b8ab-d27d7a87e935 spec: sourcePod: network-check-source-7f44b6dd87-q4zcf targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-05-25T13:18:44Z" message: 'network-check-target-ip-10-0-142-251: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.181765ms message: 'network-check-target-ip-10-0-142-251: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:32:44Z" - latency: 1.967851ms message: 'network-check-target-ip-10-0-142-251: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:31:44Z" - latency: 1.607628ms message: 'network-check-target-ip-10-0-142-251: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:30:44Z" - latency: 2.008582ms message: 'network-check-target-ip-10-0-142-251: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:29:44Z" - latency: 2.027371ms message: 'network-check-target-ip-10-0-142-251: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:28:44Z" - latency: 2.001769ms message: 'network-check-target-ip-10-0-142-251: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:27:44Z" - latency: 2.233144ms message: 'network-check-target-ip-10-0-142-251: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:26:44Z" - latency: 2.259453ms message: 'network-check-target-ip-10-0-142-251: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:25:44Z" - latency: 2.232372ms message: 'network-check-target-ip-10-0-142-251: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:24:44Z" - latency: 2.150278ms message: 'network-check-target-ip-10-0-142-251: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:23:44Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-25T13:11:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-184-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-184.ec2.internal uid: 0ba98818-36e9-45db-a485-6a8b1b6dd51b resourceVersion: "19887" uid: ae62c333-ed52-4a60-b1dc-488535b37c43 spec: sourcePod: network-check-source-7f44b6dd87-q4zcf targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-05-25T13:17:44Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 661.565µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:29:44Z" - latency: 596.135µs message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-25T13:29:44Z" - latency: 727.113µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:28:44Z" - latency: 574.862µs message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-25T13:28:44Z" - latency: 704.745µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:27:44Z" - latency: 590.119µs message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-25T13:27:44Z" - latency: 878.859µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:26:44Z" - latency: 582.888µs message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-25T13:26:44Z" - latency: 818.82µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-25T13:25:44Z" - latency: 492.299µs message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-25T13:25:44Z" kind: List metadata: resourceVersion: ""