apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-14T19:17:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-52-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-52.ec2.internal uid: 94fefcc9-6c2a-4e5d-8310-ca26d816b1a6 resourceVersion: "30751" uid: f1e3d705-ba49-487b-ba9c-7b7db21bb71c spec: sourcePod: network-check-source-6947749cfc-rvnj6 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-14T19:24:33Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 972.997µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-14T19:31:33Z" - latency: 1.474666ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-14T19:30:33Z" - latency: 983.52µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-14T19:29:33Z" - latency: 1.290033ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-14T19:28:33Z" - latency: 839.73µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-14T19:27:33Z" - latency: 900.014µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-14T19:26:33Z" - latency: 931.928µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-14T19:25:33Z" - latency: 1.055523ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-14T19:24:33Z" - latency: 1.06447ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-14T19:23:33Z" - latency: 1.688684ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-14T19:22:33Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-14T19:17:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-52-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-52.ec2.internal uid: 94fefcc9-6c2a-4e5d-8310-ca26d816b1a6 resourceVersion: "29431" uid: 45268ea6-7166-4712-9bb3-f9ea4f5fcf37 spec: sourcePod: network-check-source-6947749cfc-rvnj6 targetEndpoint: a3373491bc3c64e3ab6f06c2e19391c5-7a49424e0c19c5da.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-14T19:23:33Z" message: 'load-balancer-api-external: tcp connection to a3373491bc3c64e3ab6f06c2e19391c5-7a49424e0c19c5da.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.148998ms message: 'load-balancer-api-external: tcp connection to a3373491bc3c64e3ab6f06c2e19391c5-7a49424e0c19c5da.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-14T19:29:33Z" - latency: 9.702709ms message: 'load-balancer-api-external: resolved host name a3373491bc3c64e3ab6f06c2e19391c5-7a49424e0c19c5da.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-14T19:29:33Z" - latency: 5.418835ms message: 'load-balancer-api-external: tcp connection to a3373491bc3c64e3ab6f06c2e19391c5-7a49424e0c19c5da.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-14T19:28:33Z" - latency: 9.102622ms message: 'load-balancer-api-external: resolved host name a3373491bc3c64e3ab6f06c2e19391c5-7a49424e0c19c5da.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-14T19:28:33Z" - latency: 5.065761ms message: 'load-balancer-api-external: tcp connection to a3373491bc3c64e3ab6f06c2e19391c5-7a49424e0c19c5da.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-14T19:27:33Z" - latency: 8.543695ms message: 'load-balancer-api-external: resolved host name a3373491bc3c64e3ab6f06c2e19391c5-7a49424e0c19c5da.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-14T19:27:33Z" - latency: 5.635502ms message: 'load-balancer-api-external: tcp connection to a3373491bc3c64e3ab6f06c2e19391c5-7a49424e0c19c5da.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-14T19:26:33Z" - latency: 8.989056ms message: 'load-balancer-api-external: resolved host name a3373491bc3c64e3ab6f06c2e19391c5-7a49424e0c19c5da.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-14T19:26:33Z" - latency: 4.5095ms message: 'load-balancer-api-external: tcp connection to a3373491bc3c64e3ab6f06c2e19391c5-7a49424e0c19c5da.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-14T19:25:33Z" - latency: 9.462643ms message: 'load-balancer-api-external: resolved host name a3373491bc3c64e3ab6f06c2e19391c5-7a49424e0c19c5da.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-14T19:25:33Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-14T19:17:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-52-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-52.ec2.internal uid: 94fefcc9-6c2a-4e5d-8310-ca26d816b1a6 resourceVersion: "29432" uid: ca05bf41-f958-45dc-be63-1d8d7d12eea5 spec: sourcePod: network-check-source-6947749cfc-rvnj6 targetEndpoint: a3373491bc3c64e3ab6f06c2e19391c5-7a49424e0c19c5da.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-14T19:23:33Z" message: 'load-balancer-api-internal: tcp connection to a3373491bc3c64e3ab6f06c2e19391c5-7a49424e0c19c5da.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.13905ms message: 'load-balancer-api-internal: tcp connection to a3373491bc3c64e3ab6f06c2e19391c5-7a49424e0c19c5da.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-14T19:29:33Z" - latency: 9.786029ms message: 'load-balancer-api-internal: resolved host name a3373491bc3c64e3ab6f06c2e19391c5-7a49424e0c19c5da.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-14T19:29:33Z" - latency: 5.396478ms message: 'load-balancer-api-internal: tcp connection to a3373491bc3c64e3ab6f06c2e19391c5-7a49424e0c19c5da.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-14T19:28:33Z" - latency: 9.175454ms message: 'load-balancer-api-internal: resolved host name a3373491bc3c64e3ab6f06c2e19391c5-7a49424e0c19c5da.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-14T19:28:33Z" - latency: 5.039412ms message: 'load-balancer-api-internal: tcp connection to a3373491bc3c64e3ab6f06c2e19391c5-7a49424e0c19c5da.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-14T19:27:33Z" - latency: 8.578011ms message: 'load-balancer-api-internal: resolved host name a3373491bc3c64e3ab6f06c2e19391c5-7a49424e0c19c5da.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-14T19:27:33Z" - latency: 5.63279ms message: 'load-balancer-api-internal: tcp connection to a3373491bc3c64e3ab6f06c2e19391c5-7a49424e0c19c5da.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-14T19:26:33Z" - latency: 9.035173ms message: 'load-balancer-api-internal: resolved host name a3373491bc3c64e3ab6f06c2e19391c5-7a49424e0c19c5da.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-14T19:26:33Z" - latency: 4.456619ms message: 'load-balancer-api-internal: tcp connection to a3373491bc3c64e3ab6f06c2e19391c5-7a49424e0c19c5da.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-14T19:25:33Z" - latency: 9.575916ms message: 'load-balancer-api-internal: resolved host name a3373491bc3c64e3ab6f06c2e19391c5-7a49424e0c19c5da.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-14T19:25:33Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-14T19:17:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-52-to-network-check-target-ip-10-0-133-27 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-52.ec2.internal uid: 94fefcc9-6c2a-4e5d-8310-ca26d816b1a6 resourceVersion: "30748" uid: 941ec71e-08d6-4c13-a5d2-4bb142aef03e spec: sourcePod: network-check-source-6947749cfc-rvnj6 targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-14T19:24:33Z" message: 'network-check-target-ip-10-0-133-27: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.213816ms message: 'network-check-target-ip-10-0-133-27: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T19:31:33Z" - latency: 2.896862ms message: 'network-check-target-ip-10-0-133-27: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T19:30:33Z" - latency: 2.032124ms message: 'network-check-target-ip-10-0-133-27: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T19:29:33Z" - latency: 2.42637ms message: 'network-check-target-ip-10-0-133-27: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T19:28:33Z" - latency: 2.648455ms message: 'network-check-target-ip-10-0-133-27: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T19:27:33Z" - latency: 2.993598ms message: 'network-check-target-ip-10-0-133-27: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T19:26:33Z" - latency: 2.350607ms message: 'network-check-target-ip-10-0-133-27: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T19:25:33Z" - latency: 2.510142ms message: 'network-check-target-ip-10-0-133-27: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T19:24:33Z" - latency: 2.416322ms message: 'network-check-target-ip-10-0-133-27: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T19:23:33Z" - latency: 2.58466ms message: 'network-check-target-ip-10-0-133-27: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T19:22:33Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-14T19:17:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-52-to-network-check-target-ip-10-0-135-103 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-52.ec2.internal uid: 94fefcc9-6c2a-4e5d-8310-ca26d816b1a6 resourceVersion: "30749" uid: dab41e48-cc52-45f1-bcc4-b736419745c4 spec: sourcePod: network-check-source-6947749cfc-rvnj6 targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-14T19:24:33Z" message: 'network-check-target-ip-10-0-135-103: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.539819ms message: 'network-check-target-ip-10-0-135-103: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T19:31:33Z" - latency: 2.359489ms message: 'network-check-target-ip-10-0-135-103: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T19:30:33Z" - latency: 2.396207ms message: 'network-check-target-ip-10-0-135-103: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T19:29:33Z" - latency: 2.381955ms message: 'network-check-target-ip-10-0-135-103: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T19:28:33Z" - latency: 2.309008ms message: 'network-check-target-ip-10-0-135-103: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T19:27:33Z" - latency: 2.255167ms message: 'network-check-target-ip-10-0-135-103: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T19:26:33Z" - latency: 3.120256ms message: 'network-check-target-ip-10-0-135-103: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T19:25:33Z" - latency: 2.353102ms message: 'network-check-target-ip-10-0-135-103: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T19:24:33Z" - latency: 3.029558ms message: 'network-check-target-ip-10-0-135-103: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T19:23:33Z" - latency: 2.306452ms message: 'network-check-target-ip-10-0-135-103: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T19:22:33Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-14T19:17:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-52-to-network-check-target-ip-10-0-142-52 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-52.ec2.internal uid: 94fefcc9-6c2a-4e5d-8310-ca26d816b1a6 resourceVersion: "30750" uid: 9ff44e1b-8ab9-4ece-8568-fdf5a60c6e48 spec: sourcePod: network-check-source-6947749cfc-rvnj6 targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-14T19:24:33Z" message: 'network-check-target-ip-10-0-142-52: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.940978ms message: 'network-check-target-ip-10-0-142-52: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T19:31:33Z" - latency: 746.216µs message: 'network-check-target-ip-10-0-142-52: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T19:30:33Z" - latency: 1.381997ms message: 'network-check-target-ip-10-0-142-52: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T19:29:33Z" - latency: 833.088µs message: 'network-check-target-ip-10-0-142-52: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T19:28:33Z" - latency: 1.256651ms message: 'network-check-target-ip-10-0-142-52: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T19:27:33Z" - latency: 814.778µs message: 'network-check-target-ip-10-0-142-52: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T19:26:33Z" - latency: 945.529µs message: 'network-check-target-ip-10-0-142-52: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T19:25:33Z" - latency: 936.669µs message: 'network-check-target-ip-10-0-142-52: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T19:24:33Z" - latency: 3.388745ms message: 'network-check-target-ip-10-0-142-52: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T19:23:33Z" - latency: 6.930563ms message: 'network-check-target-ip-10-0-142-52: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T19:22:33Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-14T19:17:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-52-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-52.ec2.internal uid: 94fefcc9-6c2a-4e5d-8310-ca26d816b1a6 resourceVersion: "29430" uid: c371d8cf-9da2-4e70-9bc9-d6ca03d1729b spec: sourcePod: network-check-source-6947749cfc-rvnj6 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-14T19:23:33Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 891.748µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-14T19:29:33Z" - latency: 2.185255ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-14T19:29:33Z" - latency: 958.519µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-14T19:28:33Z" - latency: 2.117887ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-14T19:28:33Z" - latency: 875.437µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-14T19:27:33Z" - latency: 1.835605ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-14T19:27:33Z" - latency: 1.002595ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-14T19:26:33Z" - latency: 2.027201ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-14T19:26:33Z" - latency: 1.042255ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-14T19:25:33Z" - latency: 2.495053ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-14T19:25:33Z" kind: List metadata: resourceVersion: ""