apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-27T21:42:24Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-70-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-70.ec2.internal uid: 1efb300c-a5b4-478c-a009-500b1a1a6bc9 resourceVersion: "23659" uid: 36da37ed-fe6a-4734-9b45-e33dbba8ebc8 spec: sourcePod: network-check-source-7f44b6dd87-vxhjb targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-05-27T21:49:25Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.059926ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-27T21:49:25Z" - latency: 1.206474ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-27T21:48:25Z" - latency: 1.195915ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-27T21:47:25Z" - latency: 1.330091ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-27T21:46:25Z" - latency: 1.383486ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-27T21:45:25Z" - latency: 1.054753ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-27T21:44:25Z" - latency: 1.198985ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-27T21:43:25Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-27T21:42:24Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-70-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-70.ec2.internal uid: 1efb300c-a5b4-478c-a009-500b1a1a6bc9 resourceVersion: "22494" uid: ac278fc3-1041-4a95-84aa-eacbd9948b6a spec: sourcePod: network-check-source-7f44b6dd87-vxhjb targetEndpoint: afe18e7a42bde4f2ea254bae19260ada-df0ba984ccf2358c.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-27T21:48:25Z" message: 'load-balancer-api-external: tcp connection to afe18e7a42bde4f2ea254bae19260ada-df0ba984ccf2358c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.355292ms message: 'load-balancer-api-external: tcp connection to afe18e7a42bde4f2ea254bae19260ada-df0ba984ccf2358c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-27T21:48:25Z" - latency: 10.773212ms message: 'load-balancer-api-external: resolved host name afe18e7a42bde4f2ea254bae19260ada-df0ba984ccf2358c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-27T21:48:25Z" - latency: 3.906093ms message: 'load-balancer-api-external: tcp connection to afe18e7a42bde4f2ea254bae19260ada-df0ba984ccf2358c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-27T21:47:25Z" - latency: 9.580991ms message: 'load-balancer-api-external: resolved host name afe18e7a42bde4f2ea254bae19260ada-df0ba984ccf2358c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-27T21:47:25Z" - latency: 4.55645ms message: 'load-balancer-api-external: tcp connection to afe18e7a42bde4f2ea254bae19260ada-df0ba984ccf2358c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-27T21:46:25Z" - latency: 10.22002ms message: 'load-balancer-api-external: resolved host name afe18e7a42bde4f2ea254bae19260ada-df0ba984ccf2358c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-27T21:46:25Z" - latency: 4.809962ms message: 'load-balancer-api-external: tcp connection to afe18e7a42bde4f2ea254bae19260ada-df0ba984ccf2358c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-27T21:45:25Z" - latency: 14.346728ms message: 'load-balancer-api-external: resolved host name afe18e7a42bde4f2ea254bae19260ada-df0ba984ccf2358c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-27T21:45:25Z" - latency: 5.815687ms message: 'load-balancer-api-external: tcp connection to afe18e7a42bde4f2ea254bae19260ada-df0ba984ccf2358c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-27T21:44:25Z" - latency: 9.882997ms message: 'load-balancer-api-external: resolved host name afe18e7a42bde4f2ea254bae19260ada-df0ba984ccf2358c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-27T21:44:25Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-27T21:42:24Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-70-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-70.ec2.internal uid: 1efb300c-a5b4-478c-a009-500b1a1a6bc9 resourceVersion: "22495" uid: 5f121553-0cda-417e-9b93-179556bc72b2 spec: sourcePod: network-check-source-7f44b6dd87-vxhjb targetEndpoint: afe18e7a42bde4f2ea254bae19260ada-df0ba984ccf2358c.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-27T21:48:25Z" message: 'load-balancer-api-internal: tcp connection to afe18e7a42bde4f2ea254bae19260ada-df0ba984ccf2358c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.33323ms message: 'load-balancer-api-internal: tcp connection to afe18e7a42bde4f2ea254bae19260ada-df0ba984ccf2358c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-27T21:48:25Z" - latency: 10.804535ms message: 'load-balancer-api-internal: resolved host name afe18e7a42bde4f2ea254bae19260ada-df0ba984ccf2358c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-27T21:48:25Z" - latency: 3.85896ms message: 'load-balancer-api-internal: tcp connection to afe18e7a42bde4f2ea254bae19260ada-df0ba984ccf2358c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-27T21:47:25Z" - latency: 9.590639ms message: 'load-balancer-api-internal: resolved host name afe18e7a42bde4f2ea254bae19260ada-df0ba984ccf2358c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-27T21:47:25Z" - latency: 3.992203ms message: 'load-balancer-api-internal: tcp connection to afe18e7a42bde4f2ea254bae19260ada-df0ba984ccf2358c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-27T21:46:25Z" - latency: 10.154107ms message: 'load-balancer-api-internal: resolved host name afe18e7a42bde4f2ea254bae19260ada-df0ba984ccf2358c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-27T21:46:25Z" - latency: 4.849358ms message: 'load-balancer-api-internal: tcp connection to afe18e7a42bde4f2ea254bae19260ada-df0ba984ccf2358c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-27T21:45:25Z" - latency: 14.277504ms message: 'load-balancer-api-internal: resolved host name afe18e7a42bde4f2ea254bae19260ada-df0ba984ccf2358c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-27T21:45:25Z" - latency: 5.870844ms message: 'load-balancer-api-internal: tcp connection to afe18e7a42bde4f2ea254bae19260ada-df0ba984ccf2358c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-27T21:44:25Z" - latency: 9.816678ms message: 'load-balancer-api-internal: resolved host name afe18e7a42bde4f2ea254bae19260ada-df0ba984ccf2358c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-27T21:44:25Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-27T21:42:24Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-70-to-network-check-target-ip-10-0-130-139 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-70.ec2.internal uid: 1efb300c-a5b4-478c-a009-500b1a1a6bc9 resourceVersion: "23657" uid: 2b92bd68-5bea-469a-b5f2-be1b79100729 spec: sourcePod: network-check-source-7f44b6dd87-vxhjb targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-05-27T21:49:25Z" message: 'network-check-target-ip-10-0-130-139: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.366451ms message: 'network-check-target-ip-10-0-130-139: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T21:49:25Z" - latency: 1.90748ms message: 'network-check-target-ip-10-0-130-139: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T21:48:25Z" - latency: 2.172525ms message: 'network-check-target-ip-10-0-130-139: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T21:47:25Z" - latency: 1.729807ms message: 'network-check-target-ip-10-0-130-139: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T21:46:25Z" - latency: 2.401887ms message: 'network-check-target-ip-10-0-130-139: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T21:45:25Z" - latency: 2.029624ms message: 'network-check-target-ip-10-0-130-139: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T21:44:25Z" - latency: 2.142811ms message: 'network-check-target-ip-10-0-130-139: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T21:43:25Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-27T21:42:24Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-70-to-network-check-target-ip-10-0-131-147 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-70.ec2.internal uid: 1efb300c-a5b4-478c-a009-500b1a1a6bc9 resourceVersion: "23658" uid: 87db840c-1318-486c-809c-f2cb4efda801 spec: sourcePod: network-check-source-7f44b6dd87-vxhjb targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-05-27T21:49:25Z" message: 'network-check-target-ip-10-0-131-147: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.296104ms message: 'network-check-target-ip-10-0-131-147: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T21:49:25Z" - latency: 2.119196ms message: 'network-check-target-ip-10-0-131-147: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T21:48:25Z" - latency: 2.135491ms message: 'network-check-target-ip-10-0-131-147: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T21:47:25Z" - latency: 2.229715ms message: 'network-check-target-ip-10-0-131-147: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T21:46:25Z" - latency: 2.092319ms message: 'network-check-target-ip-10-0-131-147: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T21:45:25Z" - latency: 2.139537ms message: 'network-check-target-ip-10-0-131-147: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T21:44:25Z" - latency: 2.641267ms message: 'network-check-target-ip-10-0-131-147: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T21:43:25Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-27T21:42:24Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-70-to-network-check-target-ip-10-0-140-70 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-70.ec2.internal uid: 1efb300c-a5b4-478c-a009-500b1a1a6bc9 resourceVersion: "23656" uid: 1acfe4b7-6810-4e14-abd3-18fef703496f spec: sourcePod: network-check-source-7f44b6dd87-vxhjb targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-05-27T21:49:25Z" message: 'network-check-target-ip-10-0-140-70: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 929.351µs message: 'network-check-target-ip-10-0-140-70: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T21:49:25Z" - latency: 919.464µs message: 'network-check-target-ip-10-0-140-70: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T21:48:25Z" - latency: 809.961µs message: 'network-check-target-ip-10-0-140-70: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T21:47:25Z" - latency: 1.197401ms message: 'network-check-target-ip-10-0-140-70: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T21:46:25Z" - latency: 740.169µs message: 'network-check-target-ip-10-0-140-70: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T21:45:25Z" - latency: 780.07µs message: 'network-check-target-ip-10-0-140-70: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T21:44:25Z" - latency: 1.815389ms message: 'network-check-target-ip-10-0-140-70: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T21:43:25Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-27T21:42:24Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-70-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-70.ec2.internal uid: 1efb300c-a5b4-478c-a009-500b1a1a6bc9 resourceVersion: "22493" uid: d00224f3-a8f2-42c1-8641-2353a1fc9973 spec: sourcePod: network-check-source-7f44b6dd87-vxhjb targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-05-27T21:48:25Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 893.997µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-27T21:48:25Z" - latency: 1.937268ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-27T21:48:25Z" - latency: 840.995µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-27T21:47:25Z" - latency: 1.802495ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-27T21:47:25Z" - latency: 713.255µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-27T21:46:25Z" - latency: 1.554505ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-27T21:46:25Z" - latency: 1.072316ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-27T21:45:25Z" - latency: 2.136997ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-27T21:45:25Z" - latency: 901.958µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-27T21:44:25Z" - latency: 1.667717ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-27T21:44:25Z" kind: List metadata: resourceVersion: ""