apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-09T10:59:28Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-7-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-7.ec2.internal uid: a0b1283c-accc-4a4c-8aa3-12c42e08161f resourceVersion: "31334" uid: 216f0b1c-5cc2-4773-b8e4-9d5f6c01a809 spec: sourcePod: network-check-source-dbd9cf844-hng2g targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-09T11:06:29Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.202593ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T11:13:29Z" - latency: 768.357µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T11:12:29Z" - latency: 1.50884ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T11:11:29Z" - latency: 1.262306ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T11:10:29Z" - latency: 1.20531ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T11:09:29Z" - latency: 1.243521ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T11:08:29Z" - latency: 797.415µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T11:07:29Z" - latency: 892.426µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T11:06:29Z" - latency: 907.629µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T11:05:29Z" - latency: 830.315µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T11:04:29Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-09T10:59:28Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-7-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-7.ec2.internal uid: a0b1283c-accc-4a4c-8aa3-12c42e08161f resourceVersion: "35210" uid: 1f47f5cb-a5b4-4fdb-8ea9-dbb25ec3a31d spec: sourcePod: network-check-source-dbd9cf844-hng2g targetEndpoint: a267a27f59cdd48a3aa5803d59292d25-49424251f2fc6893.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-09T11:05:29Z" message: 'load-balancer-api-external: tcp connection to a267a27f59cdd48a3aa5803d59292d25-49424251f2fc6893.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.936336ms message: 'load-balancer-api-external: tcp connection to a267a27f59cdd48a3aa5803d59292d25-49424251f2fc6893.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T11:17:29Z" - latency: 9.980304ms message: 'load-balancer-api-external: resolved host name a267a27f59cdd48a3aa5803d59292d25-49424251f2fc6893.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T11:17:29Z" - latency: 5.034622ms message: 'load-balancer-api-external: tcp connection to a267a27f59cdd48a3aa5803d59292d25-49424251f2fc6893.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T11:16:29Z" - latency: 12.591501ms message: 'load-balancer-api-external: resolved host name a267a27f59cdd48a3aa5803d59292d25-49424251f2fc6893.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T11:16:29Z" - latency: 4.612452ms message: 'load-balancer-api-external: tcp connection to a267a27f59cdd48a3aa5803d59292d25-49424251f2fc6893.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T11:15:29Z" - latency: 8.829684ms message: 'load-balancer-api-external: resolved host name a267a27f59cdd48a3aa5803d59292d25-49424251f2fc6893.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T11:15:29Z" - latency: 5.27654ms message: 'load-balancer-api-external: tcp connection to a267a27f59cdd48a3aa5803d59292d25-49424251f2fc6893.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T11:14:29Z" - latency: 9.256234ms message: 'load-balancer-api-external: resolved host name a267a27f59cdd48a3aa5803d59292d25-49424251f2fc6893.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T11:14:29Z" - latency: 5.21949ms message: 'load-balancer-api-external: tcp connection to a267a27f59cdd48a3aa5803d59292d25-49424251f2fc6893.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T11:13:29Z" - latency: 9.317561ms message: 'load-balancer-api-external: resolved host name a267a27f59cdd48a3aa5803d59292d25-49424251f2fc6893.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T11:13:29Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-09T10:59:28Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-7-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-7.ec2.internal uid: a0b1283c-accc-4a4c-8aa3-12c42e08161f resourceVersion: "35209" uid: 105385fc-c418-4e3d-ae05-b98e7c6e130f spec: sourcePod: network-check-source-dbd9cf844-hng2g targetEndpoint: a267a27f59cdd48a3aa5803d59292d25-49424251f2fc6893.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-09T11:05:29Z" message: 'load-balancer-api-internal: tcp connection to a267a27f59cdd48a3aa5803d59292d25-49424251f2fc6893.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.997284ms message: 'load-balancer-api-internal: tcp connection to a267a27f59cdd48a3aa5803d59292d25-49424251f2fc6893.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T11:17:29Z" - latency: 9.696248ms message: 'load-balancer-api-internal: resolved host name a267a27f59cdd48a3aa5803d59292d25-49424251f2fc6893.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T11:17:29Z" - latency: 5.128813ms message: 'load-balancer-api-internal: tcp connection to a267a27f59cdd48a3aa5803d59292d25-49424251f2fc6893.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T11:16:29Z" - latency: 12.628329ms message: 'load-balancer-api-internal: resolved host name a267a27f59cdd48a3aa5803d59292d25-49424251f2fc6893.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T11:16:29Z" - latency: 4.972758ms message: 'load-balancer-api-internal: tcp connection to a267a27f59cdd48a3aa5803d59292d25-49424251f2fc6893.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T11:15:29Z" - latency: 8.763717ms message: 'load-balancer-api-internal: resolved host name a267a27f59cdd48a3aa5803d59292d25-49424251f2fc6893.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T11:15:29Z" - latency: 5.212961ms message: 'load-balancer-api-internal: tcp connection to a267a27f59cdd48a3aa5803d59292d25-49424251f2fc6893.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T11:14:29Z" - latency: 9.20472ms message: 'load-balancer-api-internal: resolved host name a267a27f59cdd48a3aa5803d59292d25-49424251f2fc6893.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T11:14:29Z" - latency: 4.508868ms message: 'load-balancer-api-internal: tcp connection to a267a27f59cdd48a3aa5803d59292d25-49424251f2fc6893.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T11:13:29Z" - latency: 9.283783ms message: 'load-balancer-api-internal: resolved host name a267a27f59cdd48a3aa5803d59292d25-49424251f2fc6893.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T11:13:29Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-09T10:59:28Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-7-to-network-check-target-ip-10-0-132-239 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-7.ec2.internal uid: a0b1283c-accc-4a4c-8aa3-12c42e08161f resourceVersion: "31332" uid: 3186ebb4-de1e-4c3d-a762-6ee556d791f9 spec: sourcePod: network-check-source-dbd9cf844-hng2g targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-09T11:06:29Z" message: 'network-check-target-ip-10-0-132-239: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.484761ms message: 'network-check-target-ip-10-0-132-239: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T11:13:29Z" - latency: 2.202411ms message: 'network-check-target-ip-10-0-132-239: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T11:12:29Z" - latency: 2.958786ms message: 'network-check-target-ip-10-0-132-239: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T11:11:29Z" - latency: 2.313297ms message: 'network-check-target-ip-10-0-132-239: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T11:10:29Z" - latency: 2.129452ms message: 'network-check-target-ip-10-0-132-239: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T11:09:29Z" - latency: 2.00883ms message: 'network-check-target-ip-10-0-132-239: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T11:08:29Z" - latency: 2.248258ms message: 'network-check-target-ip-10-0-132-239: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T11:07:29Z" - latency: 2.301477ms message: 'network-check-target-ip-10-0-132-239: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T11:06:29Z" - latency: 2.414703ms message: 'network-check-target-ip-10-0-132-239: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T11:05:29Z" - latency: 2.096528ms message: 'network-check-target-ip-10-0-132-239: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T11:04:29Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-09T10:59:28Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-7-to-network-check-target-ip-10-0-132-253 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-7.ec2.internal uid: a0b1283c-accc-4a4c-8aa3-12c42e08161f resourceVersion: "31333" uid: 12791de6-323f-4eef-9aed-96149be8239a spec: sourcePod: network-check-source-dbd9cf844-hng2g targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-09T11:06:29Z" message: 'network-check-target-ip-10-0-132-253: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.626124ms message: 'network-check-target-ip-10-0-132-253: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T11:13:29Z" - latency: 2.41043ms message: 'network-check-target-ip-10-0-132-253: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T11:12:29Z" - latency: 3.010541ms message: 'network-check-target-ip-10-0-132-253: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T11:11:29Z" - latency: 2.265289ms message: 'network-check-target-ip-10-0-132-253: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T11:10:29Z" - latency: 2.661898ms message: 'network-check-target-ip-10-0-132-253: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T11:09:29Z" - latency: 2.492112ms message: 'network-check-target-ip-10-0-132-253: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T11:08:29Z" - latency: 2.40493ms message: 'network-check-target-ip-10-0-132-253: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T11:07:29Z" - latency: 2.333388ms message: 'network-check-target-ip-10-0-132-253: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T11:06:29Z" - latency: 2.944614ms message: 'network-check-target-ip-10-0-132-253: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T11:05:29Z" - latency: 2.399192ms message: 'network-check-target-ip-10-0-132-253: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T11:04:29Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-09T10:59:28Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-7-to-network-check-target-ip-10-0-136-7 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-7.ec2.internal uid: a0b1283c-accc-4a4c-8aa3-12c42e08161f resourceVersion: "31331" uid: 81cee114-f957-4461-a83a-effb3076089f spec: sourcePod: network-check-source-dbd9cf844-hng2g targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-09T11:06:29Z" message: 'network-check-target-ip-10-0-136-7: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.044297ms message: 'network-check-target-ip-10-0-136-7: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T11:13:29Z" - latency: 1.413506ms message: 'network-check-target-ip-10-0-136-7: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T11:12:29Z" - latency: 938.859µs message: 'network-check-target-ip-10-0-136-7: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T11:11:29Z" - latency: 927.444µs message: 'network-check-target-ip-10-0-136-7: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T11:10:29Z" - latency: 1.482305ms message: 'network-check-target-ip-10-0-136-7: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T11:09:29Z" - latency: 1.702743ms message: 'network-check-target-ip-10-0-136-7: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T11:08:29Z" - latency: 1.171912ms message: 'network-check-target-ip-10-0-136-7: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T11:07:29Z" - latency: 888.257µs message: 'network-check-target-ip-10-0-136-7: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T11:06:29Z" - latency: 1.162979ms message: 'network-check-target-ip-10-0-136-7: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T11:05:29Z" - latency: 950.022µs message: 'network-check-target-ip-10-0-136-7: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T11:04:29Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-09T10:59:28Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-7-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-7.ec2.internal uid: a0b1283c-accc-4a4c-8aa3-12c42e08161f resourceVersion: "35208" uid: caf63a15-ebc8-46b5-bd98-926ad10a58fc spec: sourcePod: network-check-source-dbd9cf844-hng2g targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-09T11:05:29Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.026781ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-09T11:17:29Z" - latency: 2.648765ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-09T11:17:29Z" - latency: 1.063333ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-09T11:16:29Z" - latency: 2.022763ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-09T11:16:29Z" - latency: 1.048121ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-09T11:15:29Z" - latency: 1.637547ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-09T11:15:29Z" - latency: 1.004346ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-09T11:14:29Z" - latency: 2.29444ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-09T11:14:29Z" - latency: 951.427µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-09T11:13:29Z" - latency: 1.707705ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-09T11:13:29Z" kind: List metadata: resourceVersion: ""