apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T18:07:02Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-141-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-141.ec2.internal uid: 4617c04a-5e70-489b-90c3-ef6ab2f1f0bb resourceVersion: "32044" uid: f800ab08-aea3-461f-84e9-a4c574523928 spec: sourcePod: network-check-source-869dcfcdcd-lk74k targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-09T18:14:03Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.119529ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:49:03Z" - latency: 1.011934ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:48:03Z" - latency: 731.818µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:47:03Z" - latency: 1.109468ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:46:03Z" - latency: 1.038374ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:45:03Z" - latency: 1.031205ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:44:03Z" - latency: 1.230985ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:43:03Z" - latency: 923.526µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:42:03Z" - latency: 1.079586ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:41:03Z" - latency: 949.405µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:40:03Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T18:07:02Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-141-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-141.ec2.internal uid: 4617c04a-5e70-489b-90c3-ef6ab2f1f0bb resourceVersion: "32046" uid: a247103a-9c84-4ebc-84ab-60f06542786a spec: sourcePod: network-check-source-869dcfcdcd-lk74k targetEndpoint: a47d2c8c5d4f742b083530807ba58ad5-77aaf664f1c6516c.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-09T18:13:03Z" message: 'load-balancer-api-external: tcp connection to a47d2c8c5d4f742b083530807ba58ad5-77aaf664f1c6516c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.510397ms message: 'load-balancer-api-external: tcp connection to a47d2c8c5d4f742b083530807ba58ad5-77aaf664f1c6516c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:49:03Z" - latency: 9.469852ms message: 'load-balancer-api-external: resolved host name a47d2c8c5d4f742b083530807ba58ad5-77aaf664f1c6516c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T18:49:03Z" - latency: 4.53156ms message: 'load-balancer-api-external: tcp connection to a47d2c8c5d4f742b083530807ba58ad5-77aaf664f1c6516c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:48:03Z" - latency: 10.39825ms message: 'load-balancer-api-external: resolved host name a47d2c8c5d4f742b083530807ba58ad5-77aaf664f1c6516c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T18:48:03Z" - latency: 4.353666ms message: 'load-balancer-api-external: tcp connection to a47d2c8c5d4f742b083530807ba58ad5-77aaf664f1c6516c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:47:03Z" - latency: 9.108226ms message: 'load-balancer-api-external: resolved host name a47d2c8c5d4f742b083530807ba58ad5-77aaf664f1c6516c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T18:47:03Z" - latency: 4.773012ms message: 'load-balancer-api-external: tcp connection to a47d2c8c5d4f742b083530807ba58ad5-77aaf664f1c6516c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:46:03Z" - latency: 8.783328ms message: 'load-balancer-api-external: resolved host name a47d2c8c5d4f742b083530807ba58ad5-77aaf664f1c6516c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T18:46:03Z" - latency: 4.222659ms message: 'load-balancer-api-external: tcp connection to a47d2c8c5d4f742b083530807ba58ad5-77aaf664f1c6516c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:45:03Z" - latency: 12.265121ms message: 'load-balancer-api-external: resolved host name a47d2c8c5d4f742b083530807ba58ad5-77aaf664f1c6516c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T18:45:03Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T18:07:02Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-141-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-141.ec2.internal uid: 4617c04a-5e70-489b-90c3-ef6ab2f1f0bb resourceVersion: "32045" uid: fd57d179-9890-4a0c-9906-d22dfb7264c0 spec: sourcePod: network-check-source-869dcfcdcd-lk74k targetEndpoint: a47d2c8c5d4f742b083530807ba58ad5-77aaf664f1c6516c.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-09T18:13:03Z" message: 'load-balancer-api-internal: tcp connection to a47d2c8c5d4f742b083530807ba58ad5-77aaf664f1c6516c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.539509ms message: 'load-balancer-api-internal: tcp connection to a47d2c8c5d4f742b083530807ba58ad5-77aaf664f1c6516c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:49:03Z" - latency: 9.351196ms message: 'load-balancer-api-internal: resolved host name a47d2c8c5d4f742b083530807ba58ad5-77aaf664f1c6516c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T18:49:03Z" - latency: 4.544332ms message: 'load-balancer-api-internal: tcp connection to a47d2c8c5d4f742b083530807ba58ad5-77aaf664f1c6516c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:48:03Z" - latency: 10.285262ms message: 'load-balancer-api-internal: resolved host name a47d2c8c5d4f742b083530807ba58ad5-77aaf664f1c6516c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T18:48:03Z" - latency: 4.323479ms message: 'load-balancer-api-internal: tcp connection to a47d2c8c5d4f742b083530807ba58ad5-77aaf664f1c6516c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:47:03Z" - latency: 9.177411ms message: 'load-balancer-api-internal: resolved host name a47d2c8c5d4f742b083530807ba58ad5-77aaf664f1c6516c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T18:47:03Z" - latency: 4.741147ms message: 'load-balancer-api-internal: tcp connection to a47d2c8c5d4f742b083530807ba58ad5-77aaf664f1c6516c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:46:03Z" - latency: 8.680078ms message: 'load-balancer-api-internal: resolved host name a47d2c8c5d4f742b083530807ba58ad5-77aaf664f1c6516c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T18:46:03Z" - latency: 4.279565ms message: 'load-balancer-api-internal: tcp connection to a47d2c8c5d4f742b083530807ba58ad5-77aaf664f1c6516c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:45:03Z" - latency: 12.124821ms message: 'load-balancer-api-internal: resolved host name a47d2c8c5d4f742b083530807ba58ad5-77aaf664f1c6516c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T18:45:03Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T18:07:02Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-141-to-network-check-target-ip-10-0-130-107 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-141.ec2.internal uid: 4617c04a-5e70-489b-90c3-ef6ab2f1f0bb resourceVersion: "32042" uid: 207e61a6-4b49-481a-9ef8-715f8a6432c5 spec: sourcePod: network-check-source-869dcfcdcd-lk74k targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-09T18:14:03Z" message: 'network-check-target-ip-10-0-130-107: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.766636ms message: 'network-check-target-ip-10-0-130-107: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:49:03Z" - latency: 1.747303ms message: 'network-check-target-ip-10-0-130-107: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:48:03Z" - latency: 1.755961ms message: 'network-check-target-ip-10-0-130-107: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:47:03Z" - latency: 1.932372ms message: 'network-check-target-ip-10-0-130-107: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:46:03Z" - latency: 1.785372ms message: 'network-check-target-ip-10-0-130-107: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:45:03Z" - latency: 2.237533ms message: 'network-check-target-ip-10-0-130-107: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:44:03Z" - latency: 2.411858ms message: 'network-check-target-ip-10-0-130-107: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:43:03Z" - latency: 1.884806ms message: 'network-check-target-ip-10-0-130-107: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:42:03Z" - latency: 2.553342ms message: 'network-check-target-ip-10-0-130-107: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:41:03Z" - latency: 1.896917ms message: 'network-check-target-ip-10-0-130-107: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:40:03Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T18:07:02Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-141-to-network-check-target-ip-10-0-135-87 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-141.ec2.internal uid: 4617c04a-5e70-489b-90c3-ef6ab2f1f0bb resourceVersion: "32041" uid: 8a8211b6-e843-44ef-973a-70aa85618ea0 spec: sourcePod: network-check-source-869dcfcdcd-lk74k targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-09T18:14:03Z" message: 'network-check-target-ip-10-0-135-87: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.256997ms message: 'network-check-target-ip-10-0-135-87: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:49:03Z" - latency: 1.978379ms message: 'network-check-target-ip-10-0-135-87: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:48:03Z" - latency: 2.285686ms message: 'network-check-target-ip-10-0-135-87: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:47:03Z" - latency: 1.92534ms message: 'network-check-target-ip-10-0-135-87: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:46:03Z" - latency: 1.913114ms message: 'network-check-target-ip-10-0-135-87: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:45:03Z" - latency: 2.316409ms message: 'network-check-target-ip-10-0-135-87: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:44:03Z" - latency: 2.357121ms message: 'network-check-target-ip-10-0-135-87: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:43:03Z" - latency: 2.125842ms message: 'network-check-target-ip-10-0-135-87: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:42:03Z" - latency: 1.91893ms message: 'network-check-target-ip-10-0-135-87: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:41:03Z" - latency: 2.05601ms message: 'network-check-target-ip-10-0-135-87: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:40:03Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T18:07:02Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-141-to-network-check-target-ip-10-0-141-141 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-141.ec2.internal uid: 4617c04a-5e70-489b-90c3-ef6ab2f1f0bb resourceVersion: "32040" uid: 9b4c682c-3a95-4507-845b-68759d499421 spec: sourcePod: network-check-source-869dcfcdcd-lk74k targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-09T18:14:03Z" message: 'network-check-target-ip-10-0-141-141: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 861.221µs message: 'network-check-target-ip-10-0-141-141: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:49:03Z" - latency: 838.094µs message: 'network-check-target-ip-10-0-141-141: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:48:03Z" - latency: 1.435808ms message: 'network-check-target-ip-10-0-141-141: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:47:03Z" - latency: 1.13235ms message: 'network-check-target-ip-10-0-141-141: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:46:03Z" - latency: 1.227825ms message: 'network-check-target-ip-10-0-141-141: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:45:03Z" - latency: 931.286µs message: 'network-check-target-ip-10-0-141-141: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:44:03Z" - latency: 1.532553ms message: 'network-check-target-ip-10-0-141-141: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:43:03Z" - latency: 1.359597ms message: 'network-check-target-ip-10-0-141-141: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:42:03Z" - latency: 1.478767ms message: 'network-check-target-ip-10-0-141-141: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:41:03Z" - latency: 871.433µs message: 'network-check-target-ip-10-0-141-141: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:40:03Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T18:07:02Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-141-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-141.ec2.internal uid: 4617c04a-5e70-489b-90c3-ef6ab2f1f0bb resourceVersion: "32043" uid: 58eacb0f-5c9a-4274-a121-bc05bd2d521e spec: sourcePod: network-check-source-869dcfcdcd-lk74k targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-09T18:13:03Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 884.57µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:49:03Z" - latency: 1.834965ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T18:49:03Z" - latency: 831.292µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:48:03Z" - latency: 1.758363ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T18:48:03Z" - latency: 1.349822ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:47:03Z" - latency: 1.763287ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T18:47:03Z" - latency: 942.058µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:46:03Z" - latency: 1.738891ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T18:46:03Z" - latency: 825.149µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:45:03Z" - latency: 1.739436ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T18:45:03Z" kind: List metadata: resourceVersion: ""