apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-26T02:41:28Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-107-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-107.ec2.internal uid: b736c767-fb3b-4dae-93b4-4cf41b38d61c resourceVersion: "19686" uid: caed4d95-0b09-42c6-ae6b-33e4d81c447a spec: sourcePod: network-check-source-7f44b6dd87-c9mcn targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-05-26T02:48:29Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 822.908µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-26T03:02:29Z" - latency: 794.306µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-26T03:01:29Z" - latency: 974.553µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-26T03:00:29Z" - latency: 1.166619ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-26T02:59:29Z" - latency: 785.568µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-26T02:58:29Z" - latency: 908.3µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-26T02:57:29Z" - latency: 1.06578ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-26T02:56:29Z" - latency: 1.102112ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-26T02:55:29Z" - latency: 693.276µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-26T02:54:29Z" - latency: 919.895µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-26T02:53:29Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-26T02:41:28Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-107-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-107.ec2.internal uid: b736c767-fb3b-4dae-93b4-4cf41b38d61c resourceVersion: "20952" uid: 39985b23-084e-4234-9c03-80c02e1f8179 spec: sourcePod: network-check-source-7f44b6dd87-c9mcn targetEndpoint: a6ab0d61cc5cf4ade9bbf3f257bc7c80-6d8cc3cbc2046434.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-26T02:47:29Z" message: 'load-balancer-api-external: tcp connection to a6ab0d61cc5cf4ade9bbf3f257bc7c80-6d8cc3cbc2046434.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.675969ms message: 'load-balancer-api-external: tcp connection to a6ab0d61cc5cf4ade9bbf3f257bc7c80-6d8cc3cbc2046434.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-26T03:05:29Z" - latency: 7.56327ms message: 'load-balancer-api-external: resolved host name a6ab0d61cc5cf4ade9bbf3f257bc7c80-6d8cc3cbc2046434.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-26T03:05:29Z" - latency: 4.372529ms message: 'load-balancer-api-external: tcp connection to a6ab0d61cc5cf4ade9bbf3f257bc7c80-6d8cc3cbc2046434.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-26T03:04:29Z" - latency: 8.350973ms message: 'load-balancer-api-external: resolved host name a6ab0d61cc5cf4ade9bbf3f257bc7c80-6d8cc3cbc2046434.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-26T03:04:29Z" - latency: 5.514446ms message: 'load-balancer-api-external: tcp connection to a6ab0d61cc5cf4ade9bbf3f257bc7c80-6d8cc3cbc2046434.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-26T03:03:29Z" - latency: 9.562235ms message: 'load-balancer-api-external: resolved host name a6ab0d61cc5cf4ade9bbf3f257bc7c80-6d8cc3cbc2046434.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-26T03:03:29Z" - latency: 5.10778ms message: 'load-balancer-api-external: tcp connection to a6ab0d61cc5cf4ade9bbf3f257bc7c80-6d8cc3cbc2046434.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-26T03:02:29Z" - latency: 8.436995ms message: 'load-balancer-api-external: resolved host name a6ab0d61cc5cf4ade9bbf3f257bc7c80-6d8cc3cbc2046434.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-26T03:02:29Z" - latency: 3.374262ms message: 'load-balancer-api-external: tcp connection to a6ab0d61cc5cf4ade9bbf3f257bc7c80-6d8cc3cbc2046434.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-26T03:01:29Z" - latency: 7.583062ms message: 'load-balancer-api-external: resolved host name a6ab0d61cc5cf4ade9bbf3f257bc7c80-6d8cc3cbc2046434.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-26T03:01:29Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-26T02:41:28Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-107-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-107.ec2.internal uid: b736c767-fb3b-4dae-93b4-4cf41b38d61c resourceVersion: "20953" uid: b84bda0e-627b-40ff-b5b2-f9230364f05c spec: sourcePod: network-check-source-7f44b6dd87-c9mcn targetEndpoint: a6ab0d61cc5cf4ade9bbf3f257bc7c80-6d8cc3cbc2046434.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-26T02:47:29Z" message: 'load-balancer-api-internal: tcp connection to a6ab0d61cc5cf4ade9bbf3f257bc7c80-6d8cc3cbc2046434.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.536412ms message: 'load-balancer-api-internal: tcp connection to a6ab0d61cc5cf4ade9bbf3f257bc7c80-6d8cc3cbc2046434.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-26T03:05:29Z" - latency: 7.617733ms message: 'load-balancer-api-internal: resolved host name a6ab0d61cc5cf4ade9bbf3f257bc7c80-6d8cc3cbc2046434.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-26T03:05:29Z" - latency: 4.393902ms message: 'load-balancer-api-internal: tcp connection to a6ab0d61cc5cf4ade9bbf3f257bc7c80-6d8cc3cbc2046434.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-26T03:04:29Z" - latency: 8.431836ms message: 'load-balancer-api-internal: resolved host name a6ab0d61cc5cf4ade9bbf3f257bc7c80-6d8cc3cbc2046434.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-26T03:04:29Z" - latency: 5.244381ms message: 'load-balancer-api-internal: tcp connection to a6ab0d61cc5cf4ade9bbf3f257bc7c80-6d8cc3cbc2046434.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-26T03:03:29Z" - latency: 9.477203ms message: 'load-balancer-api-internal: resolved host name a6ab0d61cc5cf4ade9bbf3f257bc7c80-6d8cc3cbc2046434.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-26T03:03:29Z" - latency: 5.443792ms message: 'load-balancer-api-internal: tcp connection to a6ab0d61cc5cf4ade9bbf3f257bc7c80-6d8cc3cbc2046434.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-26T03:02:29Z" - latency: 8.477269ms message: 'load-balancer-api-internal: resolved host name a6ab0d61cc5cf4ade9bbf3f257bc7c80-6d8cc3cbc2046434.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-26T03:02:29Z" - latency: 3.292002ms message: 'load-balancer-api-internal: tcp connection to a6ab0d61cc5cf4ade9bbf3f257bc7c80-6d8cc3cbc2046434.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-26T03:01:29Z" - latency: 7.646353ms message: 'load-balancer-api-internal: resolved host name a6ab0d61cc5cf4ade9bbf3f257bc7c80-6d8cc3cbc2046434.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-26T03:01:29Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-26T02:41:28Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-107-to-network-check-target-ip-10-0-132-107 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-107.ec2.internal uid: b736c767-fb3b-4dae-93b4-4cf41b38d61c resourceVersion: "19683" uid: a1d1f6cc-8ec4-4970-a3d6-e43d03f97da9 spec: sourcePod: network-check-source-7f44b6dd87-c9mcn targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-05-26T02:48:29Z" message: 'network-check-target-ip-10-0-132-107: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 757.647µs message: 'network-check-target-ip-10-0-132-107: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T03:02:29Z" - latency: 754.91µs message: 'network-check-target-ip-10-0-132-107: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T03:01:29Z" - latency: 799.283µs message: 'network-check-target-ip-10-0-132-107: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T03:00:29Z" - latency: 1.298576ms message: 'network-check-target-ip-10-0-132-107: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T02:59:29Z" - latency: 776.399µs message: 'network-check-target-ip-10-0-132-107: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T02:58:29Z" - latency: 1.384785ms message: 'network-check-target-ip-10-0-132-107: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T02:57:29Z" - latency: 1.005571ms message: 'network-check-target-ip-10-0-132-107: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T02:56:29Z" - latency: 807.603µs message: 'network-check-target-ip-10-0-132-107: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T02:55:29Z" - latency: 677.292µs message: 'network-check-target-ip-10-0-132-107: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T02:54:29Z" - latency: 767.61µs message: 'network-check-target-ip-10-0-132-107: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T02:53:29Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-26T02:41:28Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-107-to-network-check-target-ip-10-0-134-241 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-107.ec2.internal uid: b736c767-fb3b-4dae-93b4-4cf41b38d61c resourceVersion: "19685" uid: e0a48e3b-ec19-4355-9bea-826367c16002 spec: sourcePod: network-check-source-7f44b6dd87-c9mcn targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-05-26T02:48:29Z" message: 'network-check-target-ip-10-0-134-241: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.98611ms message: 'network-check-target-ip-10-0-134-241: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T03:02:29Z" - latency: 1.71503ms message: 'network-check-target-ip-10-0-134-241: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T03:01:29Z" - latency: 1.95274ms message: 'network-check-target-ip-10-0-134-241: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T03:00:29Z" - latency: 2.157934ms message: 'network-check-target-ip-10-0-134-241: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T02:59:29Z" - latency: 2.130768ms message: 'network-check-target-ip-10-0-134-241: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T02:58:29Z" - latency: 2.076148ms message: 'network-check-target-ip-10-0-134-241: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T02:57:29Z" - latency: 1.779321ms message: 'network-check-target-ip-10-0-134-241: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T02:56:29Z" - latency: 1.982325ms message: 'network-check-target-ip-10-0-134-241: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T02:55:29Z" - latency: 1.887922ms message: 'network-check-target-ip-10-0-134-241: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T02:54:29Z" - latency: 2.022215ms message: 'network-check-target-ip-10-0-134-241: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T02:53:29Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-26T02:41:28Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-107-to-network-check-target-ip-10-0-139-173 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-107.ec2.internal uid: b736c767-fb3b-4dae-93b4-4cf41b38d61c resourceVersion: "19684" uid: e2d412c7-cda2-4346-ae44-765c813066e8 spec: sourcePod: network-check-source-7f44b6dd87-c9mcn targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-05-26T02:48:29Z" message: 'network-check-target-ip-10-0-139-173: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.845827ms message: 'network-check-target-ip-10-0-139-173: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T03:02:29Z" - latency: 1.724253ms message: 'network-check-target-ip-10-0-139-173: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T03:01:29Z" - latency: 2.389936ms message: 'network-check-target-ip-10-0-139-173: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T03:00:29Z" - latency: 2.124429ms message: 'network-check-target-ip-10-0-139-173: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T02:59:29Z" - latency: 2.210171ms message: 'network-check-target-ip-10-0-139-173: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T02:58:29Z" - latency: 1.812807ms message: 'network-check-target-ip-10-0-139-173: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T02:57:29Z" - latency: 2.02406ms message: 'network-check-target-ip-10-0-139-173: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T02:56:29Z" - latency: 2.154886ms message: 'network-check-target-ip-10-0-139-173: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T02:55:29Z" - latency: 1.715104ms message: 'network-check-target-ip-10-0-139-173: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T02:54:29Z" - latency: 2.212733ms message: 'network-check-target-ip-10-0-139-173: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T02:53:29Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-26T02:41:28Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-107-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-107.ec2.internal uid: b736c767-fb3b-4dae-93b4-4cf41b38d61c resourceVersion: "20951" uid: 96a19f2e-40be-4c23-8890-d651382251ad spec: sourcePod: network-check-source-7f44b6dd87-c9mcn targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-05-26T02:47:29Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.046982ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-26T03:05:29Z" - latency: 1.786614ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-26T03:05:29Z" - latency: 923.811µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-26T03:04:29Z" - latency: 1.671619ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-26T03:04:29Z" - latency: 850.533µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-26T03:03:29Z" - latency: 1.539962ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-26T03:03:29Z" - latency: 1.009584ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-26T03:02:29Z" - latency: 1.546401ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-26T03:02:29Z" - latency: 856.097µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-26T03:01:29Z" - latency: 1.418301ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-26T03:01:29Z" kind: List metadata: resourceVersion: ""