apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-17T17:37:13Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-96-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-96.ec2.internal uid: bbddc37f-7793-40a5-b991-6634470d1527 resourceVersion: "23182" uid: f95f15d2-bf81-4cf3-bd9c-d03797fc25e2 spec: sourcePod: network-check-source-7cbc45fddc-9jr2n targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-09-17T17:44:14Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 856.572µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T17:58:14Z" - latency: 881.258µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T17:57:14Z" - latency: 861.556µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T17:56:14Z" - latency: 958.007µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T17:55:14Z" - latency: 1.066178ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T17:54:14Z" - latency: 870.129µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T17:53:14Z" - latency: 1.212481ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T17:52:14Z" - latency: 1.005272ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T17:51:14Z" - latency: 852.272µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T17:50:14Z" - latency: 817.564µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T17:49:14Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-17T17:37:13Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-96-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-96.ec2.internal uid: bbddc37f-7793-40a5-b991-6634470d1527 resourceVersion: "21749" uid: 33f3c38b-cf28-40f1-a6e4-450dce690bc2 spec: sourcePod: network-check-source-7cbc45fddc-9jr2n targetEndpoint: a92f13632c75a4fa983519100b77a21b-739300dc29c96f17.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-17T17:43:14Z" message: 'load-balancer-api-external: tcp connection to a92f13632c75a4fa983519100b77a21b-739300dc29c96f17.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.288273ms message: 'load-balancer-api-external: tcp connection to a92f13632c75a4fa983519100b77a21b-739300dc29c96f17.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T17:55:14Z" - latency: 6.031944ms message: 'load-balancer-api-external: resolved host name a92f13632c75a4fa983519100b77a21b-739300dc29c96f17.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T17:55:14Z" - latency: 13.507278ms message: 'load-balancer-api-external: tcp connection to a92f13632c75a4fa983519100b77a21b-739300dc29c96f17.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T17:54:14Z" - latency: 6.81402ms message: 'load-balancer-api-external: resolved host name a92f13632c75a4fa983519100b77a21b-739300dc29c96f17.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T17:54:14Z" - latency: 4.634448ms message: 'load-balancer-api-external: tcp connection to a92f13632c75a4fa983519100b77a21b-739300dc29c96f17.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T17:53:14Z" - latency: 6.297872ms message: 'load-balancer-api-external: resolved host name a92f13632c75a4fa983519100b77a21b-739300dc29c96f17.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T17:53:14Z" - latency: 4.12067ms message: 'load-balancer-api-external: tcp connection to a92f13632c75a4fa983519100b77a21b-739300dc29c96f17.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T17:52:14Z" - latency: 6.581991ms message: 'load-balancer-api-external: resolved host name a92f13632c75a4fa983519100b77a21b-739300dc29c96f17.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T17:52:14Z" - latency: 6.027472ms message: 'load-balancer-api-external: tcp connection to a92f13632c75a4fa983519100b77a21b-739300dc29c96f17.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T17:51:14Z" - latency: 6.788265ms message: 'load-balancer-api-external: resolved host name a92f13632c75a4fa983519100b77a21b-739300dc29c96f17.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T17:51:14Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-17T17:37:13Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-96-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-96.ec2.internal uid: bbddc37f-7793-40a5-b991-6634470d1527 resourceVersion: "21750" uid: a5d8ffdc-b724-4616-a030-4a0c0cc5c7a1 spec: sourcePod: network-check-source-7cbc45fddc-9jr2n targetEndpoint: a92f13632c75a4fa983519100b77a21b-739300dc29c96f17.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-17T17:43:14Z" message: 'load-balancer-api-internal: tcp connection to a92f13632c75a4fa983519100b77a21b-739300dc29c96f17.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.702059ms message: 'load-balancer-api-internal: tcp connection to a92f13632c75a4fa983519100b77a21b-739300dc29c96f17.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T17:55:14Z" - latency: 6.009725ms message: 'load-balancer-api-internal: resolved host name a92f13632c75a4fa983519100b77a21b-739300dc29c96f17.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T17:55:14Z" - latency: 3.760128ms message: 'load-balancer-api-internal: tcp connection to a92f13632c75a4fa983519100b77a21b-739300dc29c96f17.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T17:54:14Z" - latency: 6.793373ms message: 'load-balancer-api-internal: resolved host name a92f13632c75a4fa983519100b77a21b-739300dc29c96f17.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T17:54:14Z" - latency: 4.657841ms message: 'load-balancer-api-internal: tcp connection to a92f13632c75a4fa983519100b77a21b-739300dc29c96f17.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T17:53:14Z" - latency: 6.263554ms message: 'load-balancer-api-internal: resolved host name a92f13632c75a4fa983519100b77a21b-739300dc29c96f17.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T17:53:14Z" - latency: 4.074904ms message: 'load-balancer-api-internal: tcp connection to a92f13632c75a4fa983519100b77a21b-739300dc29c96f17.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T17:52:14Z" - latency: 6.559444ms message: 'load-balancer-api-internal: resolved host name a92f13632c75a4fa983519100b77a21b-739300dc29c96f17.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T17:52:14Z" - latency: 6.012902ms message: 'load-balancer-api-internal: tcp connection to a92f13632c75a4fa983519100b77a21b-739300dc29c96f17.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T17:51:14Z" - latency: 6.7638ms message: 'load-balancer-api-internal: resolved host name a92f13632c75a4fa983519100b77a21b-739300dc29c96f17.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T17:51:14Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-17T17:37:13Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-96-to-network-check-target-ip-10-0-132-90 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-96.ec2.internal uid: bbddc37f-7793-40a5-b991-6634470d1527 resourceVersion: "23180" uid: 5dc3e70b-2313-41ad-a5b4-6ae096e1cd50 spec: sourcePod: network-check-source-7cbc45fddc-9jr2n targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-09-17T17:44:14Z" message: 'network-check-target-ip-10-0-132-90: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.279932ms message: 'network-check-target-ip-10-0-132-90: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T17:58:14Z" - latency: 2.118829ms message: 'network-check-target-ip-10-0-132-90: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T17:57:14Z" - latency: 1.960247ms message: 'network-check-target-ip-10-0-132-90: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T17:56:14Z" - latency: 2.205465ms message: 'network-check-target-ip-10-0-132-90: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T17:55:14Z" - latency: 2.374104ms message: 'network-check-target-ip-10-0-132-90: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T17:54:14Z" - latency: 2.377735ms message: 'network-check-target-ip-10-0-132-90: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T17:53:14Z" - latency: 2.412832ms message: 'network-check-target-ip-10-0-132-90: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T17:52:14Z" - latency: 2.244028ms message: 'network-check-target-ip-10-0-132-90: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T17:51:14Z" - latency: 2.599845ms message: 'network-check-target-ip-10-0-132-90: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T17:50:14Z" - latency: 2.009987ms message: 'network-check-target-ip-10-0-132-90: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T17:49:14Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-17T17:37:13Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-96-to-network-check-target-ip-10-0-134-52 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-96.ec2.internal uid: bbddc37f-7793-40a5-b991-6634470d1527 resourceVersion: "23181" uid: c23d6752-df81-45cb-9398-2170fd04ca47 spec: sourcePod: network-check-source-7cbc45fddc-9jr2n targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-09-17T17:44:14Z" message: 'network-check-target-ip-10-0-134-52: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.12556ms message: 'network-check-target-ip-10-0-134-52: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T17:58:14Z" - latency: 2.041536ms message: 'network-check-target-ip-10-0-134-52: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T17:57:14Z" - latency: 1.8448ms message: 'network-check-target-ip-10-0-134-52: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T17:56:14Z" - latency: 2.098971ms message: 'network-check-target-ip-10-0-134-52: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T17:55:14Z" - latency: 2.415633ms message: 'network-check-target-ip-10-0-134-52: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T17:54:14Z" - latency: 1.945127ms message: 'network-check-target-ip-10-0-134-52: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T17:53:14Z" - latency: 2.088935ms message: 'network-check-target-ip-10-0-134-52: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T17:52:14Z" - latency: 2.04916ms message: 'network-check-target-ip-10-0-134-52: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T17:51:14Z" - latency: 2.801095ms message: 'network-check-target-ip-10-0-134-52: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T17:50:14Z" - latency: 2.100914ms message: 'network-check-target-ip-10-0-134-52: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T17:49:14Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-17T17:37:13Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-96-to-network-check-target-ip-10-0-134-96 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-96.ec2.internal uid: bbddc37f-7793-40a5-b991-6634470d1527 resourceVersion: "23179" uid: 76eafdb4-a73f-4e07-acb7-500f682a5348 spec: sourcePod: network-check-source-7cbc45fddc-9jr2n targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-09-17T17:44:14Z" message: 'network-check-target-ip-10-0-134-96: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 848.569µs message: 'network-check-target-ip-10-0-134-96: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T17:58:14Z" - latency: 888.212µs message: 'network-check-target-ip-10-0-134-96: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T17:57:14Z" - latency: 845.12µs message: 'network-check-target-ip-10-0-134-96: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T17:56:14Z" - latency: 899.805µs message: 'network-check-target-ip-10-0-134-96: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T17:55:14Z" - latency: 923.283µs message: 'network-check-target-ip-10-0-134-96: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T17:54:14Z" - latency: 805.851µs message: 'network-check-target-ip-10-0-134-96: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T17:53:14Z" - latency: 907.647µs message: 'network-check-target-ip-10-0-134-96: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T17:52:14Z" - latency: 867.437µs message: 'network-check-target-ip-10-0-134-96: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T17:51:14Z" - latency: 959.218µs message: 'network-check-target-ip-10-0-134-96: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T17:50:14Z" - latency: 849.543µs message: 'network-check-target-ip-10-0-134-96: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T17:49:14Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-17T17:37:13Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-96-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-96.ec2.internal uid: bbddc37f-7793-40a5-b991-6634470d1527 resourceVersion: "21748" uid: 6703b8ab-0232-44fa-8166-655ec82e6964 spec: sourcePod: network-check-source-7cbc45fddc-9jr2n targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-09-17T17:43:14Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 760.733µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-17T17:55:14Z" - latency: 1.63748ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-17T17:55:14Z" - latency: 893.733µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-17T17:54:14Z" - latency: 1.666835ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-17T17:54:14Z" - latency: 669.047µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-17T17:53:14Z" - latency: 1.640107ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-17T17:53:14Z" - latency: 760.273µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-17T17:52:14Z" - latency: 1.56995ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-17T17:52:14Z" - latency: 933.449µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-17T17:51:14Z" - latency: 1.766057ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-17T17:51:14Z" kind: List metadata: resourceVersion: ""