apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-10T12:21:12Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-197-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-197.ec2.internal uid: 34616ccf-f3b1-4995-b30e-f0ad84850ab9 resourceVersion: "19415" uid: 12a7fbf7-2832-4662-8be2-68d4238d342a spec: sourcePod: network-check-source-685456655f-wf2mz targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-09-10T12:28:13Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.289513ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-10T12:42:13Z" - latency: 830.147µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-10T12:41:13Z" - latency: 955.55µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-10T12:40:13Z" - latency: 1.020692ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-10T12:39:13Z" - latency: 1.252905ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-10T12:38:13Z" - latency: 935.442µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-10T12:37:13Z" - latency: 1.186695ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-10T12:36:13Z" - latency: 1.074688ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-10T12:35:13Z" - latency: 808.526µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-10T12:34:13Z" - latency: 1.31811ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-10T12:33:13Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-10T12:21:12Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-197-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-197.ec2.internal uid: 34616ccf-f3b1-4995-b30e-f0ad84850ab9 resourceVersion: "20692" uid: 81f8cbf9-9cbf-41a5-b820-a8e2aaab4b10 spec: sourcePod: network-check-source-685456655f-wf2mz targetEndpoint: a2a6eaa2e8a5245a9845b6a466e143ee-71cc61b54b23957a.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-10T12:27:13Z" message: 'load-balancer-api-external: tcp connection to a2a6eaa2e8a5245a9845b6a466e143ee-71cc61b54b23957a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.747894ms message: 'load-balancer-api-external: tcp connection to a2a6eaa2e8a5245a9845b6a466e143ee-71cc61b54b23957a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-10T12:45:13Z" - latency: 8.706857ms message: 'load-balancer-api-external: resolved host name a2a6eaa2e8a5245a9845b6a466e143ee-71cc61b54b23957a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-10T12:45:13Z" - latency: 3.34536ms message: 'load-balancer-api-external: tcp connection to a2a6eaa2e8a5245a9845b6a466e143ee-71cc61b54b23957a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-10T12:44:13Z" - latency: 8.673924ms message: 'load-balancer-api-external: resolved host name a2a6eaa2e8a5245a9845b6a466e143ee-71cc61b54b23957a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-10T12:44:13Z" - latency: 4.714006ms message: 'load-balancer-api-external: tcp connection to a2a6eaa2e8a5245a9845b6a466e143ee-71cc61b54b23957a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-10T12:43:13Z" - latency: 7.592915ms message: 'load-balancer-api-external: resolved host name a2a6eaa2e8a5245a9845b6a466e143ee-71cc61b54b23957a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-10T12:43:13Z" - latency: 5.051843ms message: 'load-balancer-api-external: tcp connection to a2a6eaa2e8a5245a9845b6a466e143ee-71cc61b54b23957a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-10T12:42:13Z" - latency: 8.985791ms message: 'load-balancer-api-external: resolved host name a2a6eaa2e8a5245a9845b6a466e143ee-71cc61b54b23957a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-10T12:42:13Z" - latency: 6.421979ms message: 'load-balancer-api-external: tcp connection to a2a6eaa2e8a5245a9845b6a466e143ee-71cc61b54b23957a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-10T12:41:13Z" - latency: 7.967249ms message: 'load-balancer-api-external: resolved host name a2a6eaa2e8a5245a9845b6a466e143ee-71cc61b54b23957a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-10T12:41:13Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-10T12:21:12Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-197-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-197.ec2.internal uid: 34616ccf-f3b1-4995-b30e-f0ad84850ab9 resourceVersion: "20691" uid: 465d31d8-6d4a-469b-b9c5-44c00b54f210 spec: sourcePod: network-check-source-685456655f-wf2mz targetEndpoint: a2a6eaa2e8a5245a9845b6a466e143ee-71cc61b54b23957a.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-10T12:27:13Z" message: 'load-balancer-api-internal: tcp connection to a2a6eaa2e8a5245a9845b6a466e143ee-71cc61b54b23957a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.028602ms message: 'load-balancer-api-internal: tcp connection to a2a6eaa2e8a5245a9845b6a466e143ee-71cc61b54b23957a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-10T12:45:13Z" - latency: 8.664344ms message: 'load-balancer-api-internal: resolved host name a2a6eaa2e8a5245a9845b6a466e143ee-71cc61b54b23957a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-10T12:45:13Z" - latency: 5.116075ms message: 'load-balancer-api-internal: tcp connection to a2a6eaa2e8a5245a9845b6a466e143ee-71cc61b54b23957a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-10T12:44:13Z" - latency: 8.64259ms message: 'load-balancer-api-internal: resolved host name a2a6eaa2e8a5245a9845b6a466e143ee-71cc61b54b23957a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-10T12:44:13Z" - latency: 4.81444ms message: 'load-balancer-api-internal: tcp connection to a2a6eaa2e8a5245a9845b6a466e143ee-71cc61b54b23957a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-10T12:43:13Z" - latency: 7.53871ms message: 'load-balancer-api-internal: resolved host name a2a6eaa2e8a5245a9845b6a466e143ee-71cc61b54b23957a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-10T12:43:13Z" - latency: 5.055208ms message: 'load-balancer-api-internal: tcp connection to a2a6eaa2e8a5245a9845b6a466e143ee-71cc61b54b23957a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-10T12:42:13Z" - latency: 8.94917ms message: 'load-balancer-api-internal: resolved host name a2a6eaa2e8a5245a9845b6a466e143ee-71cc61b54b23957a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-10T12:42:13Z" - latency: 3.696318ms message: 'load-balancer-api-internal: tcp connection to a2a6eaa2e8a5245a9845b6a466e143ee-71cc61b54b23957a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-10T12:41:13Z" - latency: 7.918224ms message: 'load-balancer-api-internal: resolved host name a2a6eaa2e8a5245a9845b6a466e143ee-71cc61b54b23957a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-10T12:41:13Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-10T12:21:13Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-197-to-network-check-target-ip-10-0-130-221 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-197.ec2.internal uid: 34616ccf-f3b1-4995-b30e-f0ad84850ab9 resourceVersion: "19414" uid: 6b1a796c-f9d1-43bf-90dd-a336d4a1fd94 spec: sourcePod: network-check-source-685456655f-wf2mz targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-09-10T12:28:13Z" message: 'network-check-target-ip-10-0-130-221: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.845977ms message: 'network-check-target-ip-10-0-130-221: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T12:42:13Z" - latency: 1.646351ms message: 'network-check-target-ip-10-0-130-221: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T12:41:13Z" - latency: 1.880017ms message: 'network-check-target-ip-10-0-130-221: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T12:40:13Z" - latency: 1.910648ms message: 'network-check-target-ip-10-0-130-221: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T12:39:13Z" - latency: 1.791642ms message: 'network-check-target-ip-10-0-130-221: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T12:38:13Z" - latency: 1.838735ms message: 'network-check-target-ip-10-0-130-221: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T12:37:13Z" - latency: 1.829108ms message: 'network-check-target-ip-10-0-130-221: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T12:36:13Z" - latency: 1.855886ms message: 'network-check-target-ip-10-0-130-221: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T12:35:13Z" - latency: 1.704739ms message: 'network-check-target-ip-10-0-130-221: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T12:34:13Z" - latency: 1.92447ms message: 'network-check-target-ip-10-0-130-221: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T12:33:13Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-10T12:21:12Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-197-to-network-check-target-ip-10-0-136-197 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-197.ec2.internal uid: 34616ccf-f3b1-4995-b30e-f0ad84850ab9 resourceVersion: "19412" uid: 8ad980d1-133e-437e-b130-9871aa317cc0 spec: sourcePod: network-check-source-685456655f-wf2mz targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-09-10T12:28:13Z" message: 'network-check-target-ip-10-0-136-197: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.270951ms message: 'network-check-target-ip-10-0-136-197: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T12:42:13Z" - latency: 753.418µs message: 'network-check-target-ip-10-0-136-197: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T12:41:13Z" - latency: 788.526µs message: 'network-check-target-ip-10-0-136-197: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T12:40:13Z" - latency: 764.67µs message: 'network-check-target-ip-10-0-136-197: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T12:39:13Z" - latency: 882.543µs message: 'network-check-target-ip-10-0-136-197: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T12:38:13Z" - latency: 1.623939ms message: 'network-check-target-ip-10-0-136-197: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T12:37:13Z" - latency: 1.379141ms message: 'network-check-target-ip-10-0-136-197: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T12:36:13Z" - latency: 942.933µs message: 'network-check-target-ip-10-0-136-197: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T12:35:13Z" - latency: 1.123776ms message: 'network-check-target-ip-10-0-136-197: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T12:34:13Z" - latency: 972.408µs message: 'network-check-target-ip-10-0-136-197: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T12:33:13Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-10T12:21:12Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-197-to-network-check-target-ip-10-0-143-110 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-197.ec2.internal uid: 34616ccf-f3b1-4995-b30e-f0ad84850ab9 resourceVersion: "19413" uid: 89b25aea-a21d-4e21-b8a0-4eec13071beb spec: sourcePod: network-check-source-685456655f-wf2mz targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-09-10T12:28:13Z" message: 'network-check-target-ip-10-0-143-110: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.396074ms message: 'network-check-target-ip-10-0-143-110: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T12:42:13Z" - latency: 2.118704ms message: 'network-check-target-ip-10-0-143-110: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T12:41:13Z" - latency: 2.039361ms message: 'network-check-target-ip-10-0-143-110: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T12:40:13Z" - latency: 2.116215ms message: 'network-check-target-ip-10-0-143-110: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T12:39:13Z" - latency: 2.027552ms message: 'network-check-target-ip-10-0-143-110: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T12:38:13Z" - latency: 2.436899ms message: 'network-check-target-ip-10-0-143-110: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T12:37:13Z" - latency: 2.175692ms message: 'network-check-target-ip-10-0-143-110: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T12:36:13Z" - latency: 2.291576ms message: 'network-check-target-ip-10-0-143-110: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T12:35:13Z" - latency: 2.190464ms message: 'network-check-target-ip-10-0-143-110: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T12:34:13Z" - latency: 1.944028ms message: 'network-check-target-ip-10-0-143-110: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T12:33:13Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-10T12:21:12Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-197-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-197.ec2.internal uid: 34616ccf-f3b1-4995-b30e-f0ad84850ab9 resourceVersion: "20690" uid: ee6c51f9-b35a-488c-b2c1-c38af7dba093 spec: sourcePod: network-check-source-685456655f-wf2mz targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-09-10T12:27:13Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 902.008µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-10T12:45:13Z" - latency: 1.702809ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-10T12:45:13Z" - latency: 829.633µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-10T12:44:13Z" - latency: 1.858926ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-10T12:44:13Z" - latency: 1.10894ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-10T12:43:13Z" - latency: 1.550659ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-10T12:43:13Z" - latency: 948.038µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-10T12:42:13Z" - latency: 2.410786ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-10T12:42:13Z" - latency: 773.377µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-10T12:41:13Z" - latency: 2.242378ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-10T12:41:13Z" kind: List metadata: resourceVersion: ""