apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T19:56:31Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-177-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-177.ec2.internal
      uid: 9e218f80-3cca-4043-9e35-60d335fd318a
    resourceVersion: "54252"
    uid: 9cb8e3a0-a63e-4d8f-8811-81360d772158
  spec:
    sourcePod: network-check-source-989f8b8dc-cxzsr
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T20:03:32Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.360179ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:31:32Z"
    - latency: 1.390216ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:30:32Z"
    - latency: 1.426053ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:29:32Z"
    - latency: 931.343µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:28:32Z"
    - latency: 855.457µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:27:32Z"
    - latency: 1.109658ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:26:32Z"
    - latency: 800.029µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:25:32Z"
    - latency: 1.179519ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:24:32Z"
    - latency: 1.147644ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:23:32Z"
    - latency: 876.156µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:22:32Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T19:56:31Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-177-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-177.ec2.internal
      uid: 9e218f80-3cca-4043-9e35-60d335fd318a
    resourceVersion: "55236"
    uid: 66826116-1bc8-435c-adbc-dfcf299fac9a
  spec:
    sourcePod: network-check-source-989f8b8dc-cxzsr
    targetEndpoint: ac7bd9638b21d409cafd7a745a109297-2afbb00a853968a7.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T20:02:32Z"
      message: 'load-balancer-api-external: tcp connection to ac7bd9638b21d409cafd7a745a109297-2afbb00a853968a7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.770339ms
      message: 'load-balancer-api-external: tcp connection to ac7bd9638b21d409cafd7a745a109297-2afbb00a853968a7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:32:32Z"
    - latency: 6.615624ms
      message: 'load-balancer-api-external: resolved host name ac7bd9638b21d409cafd7a745a109297-2afbb00a853968a7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T20:32:32Z"
    - latency: 5.584043ms
      message: 'load-balancer-api-external: tcp connection to ac7bd9638b21d409cafd7a745a109297-2afbb00a853968a7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:31:32Z"
    - latency: 8.349519ms
      message: 'load-balancer-api-external: resolved host name ac7bd9638b21d409cafd7a745a109297-2afbb00a853968a7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T20:31:32Z"
    - latency: 6.498359ms
      message: 'load-balancer-api-external: tcp connection to ac7bd9638b21d409cafd7a745a109297-2afbb00a853968a7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:30:32Z"
    - latency: 7.139284ms
      message: 'load-balancer-api-external: resolved host name ac7bd9638b21d409cafd7a745a109297-2afbb00a853968a7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T20:30:32Z"
    - latency: 4.693511ms
      message: 'load-balancer-api-external: tcp connection to ac7bd9638b21d409cafd7a745a109297-2afbb00a853968a7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:29:32Z"
    - latency: 9.983812ms
      message: 'load-balancer-api-external: resolved host name ac7bd9638b21d409cafd7a745a109297-2afbb00a853968a7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T20:29:32Z"
    - latency: 5.16502ms
      message: 'load-balancer-api-external: tcp connection to ac7bd9638b21d409cafd7a745a109297-2afbb00a853968a7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:28:32Z"
    - latency: 6.425294ms
      message: 'load-balancer-api-external: resolved host name ac7bd9638b21d409cafd7a745a109297-2afbb00a853968a7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T20:28:32Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T19:56:31Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-177-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-177.ec2.internal
      uid: 9e218f80-3cca-4043-9e35-60d335fd318a
    resourceVersion: "55235"
    uid: 5fa3d63d-bae0-43cc-a352-8473d3ac515b
  spec:
    sourcePod: network-check-source-989f8b8dc-cxzsr
    targetEndpoint: ac7bd9638b21d409cafd7a745a109297-2afbb00a853968a7.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T20:02:32Z"
      message: 'load-balancer-api-internal: tcp connection to ac7bd9638b21d409cafd7a745a109297-2afbb00a853968a7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.785393ms
      message: 'load-balancer-api-internal: tcp connection to ac7bd9638b21d409cafd7a745a109297-2afbb00a853968a7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:32:32Z"
    - latency: 6.648724ms
      message: 'load-balancer-api-internal: resolved host name ac7bd9638b21d409cafd7a745a109297-2afbb00a853968a7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T20:32:32Z"
    - latency: 5.559539ms
      message: 'load-balancer-api-internal: tcp connection to ac7bd9638b21d409cafd7a745a109297-2afbb00a853968a7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:31:32Z"
    - latency: 8.381103ms
      message: 'load-balancer-api-internal: resolved host name ac7bd9638b21d409cafd7a745a109297-2afbb00a853968a7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T20:31:32Z"
    - latency: 5.757909ms
      message: 'load-balancer-api-internal: tcp connection to ac7bd9638b21d409cafd7a745a109297-2afbb00a853968a7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:30:32Z"
    - latency: 7.17553ms
      message: 'load-balancer-api-internal: resolved host name ac7bd9638b21d409cafd7a745a109297-2afbb00a853968a7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T20:30:32Z"
    - latency: 4.086512ms
      message: 'load-balancer-api-internal: tcp connection to ac7bd9638b21d409cafd7a745a109297-2afbb00a853968a7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:29:32Z"
    - latency: 10.055768ms
      message: 'load-balancer-api-internal: resolved host name ac7bd9638b21d409cafd7a745a109297-2afbb00a853968a7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T20:29:32Z"
    - latency: 5.158599ms
      message: 'load-balancer-api-internal: tcp connection to ac7bd9638b21d409cafd7a745a109297-2afbb00a853968a7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:28:32Z"
    - latency: 6.462421ms
      message: 'load-balancer-api-internal: resolved host name ac7bd9638b21d409cafd7a745a109297-2afbb00a853968a7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T20:28:32Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T19:56:31Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-177-to-network-check-target-ip-10-0-128-177
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-177.ec2.internal
      uid: 9e218f80-3cca-4043-9e35-60d335fd318a
    resourceVersion: "54249"
    uid: 3885905e-2b5c-4df0-bed3-cc3eb42e4056
  spec:
    sourcePod: network-check-source-989f8b8dc-cxzsr
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T20:03:32Z"
      message: 'network-check-target-ip-10-0-128-177: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.380475ms
      message: 'network-check-target-ip-10-0-128-177: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:31:32Z"
    - latency: 1.533515ms
      message: 'network-check-target-ip-10-0-128-177: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:30:32Z"
    - latency: 942.549µs
      message: 'network-check-target-ip-10-0-128-177: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:29:32Z"
    - latency: 1.265357ms
      message: 'network-check-target-ip-10-0-128-177: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:28:32Z"
    - latency: 1.242345ms
      message: 'network-check-target-ip-10-0-128-177: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:27:32Z"
    - latency: 1.521341ms
      message: 'network-check-target-ip-10-0-128-177: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:26:32Z"
    - latency: 797.86µs
      message: 'network-check-target-ip-10-0-128-177: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:25:32Z"
    - latency: 1.028448ms
      message: 'network-check-target-ip-10-0-128-177: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:24:32Z"
    - latency: 1.45052ms
      message: 'network-check-target-ip-10-0-128-177: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:23:32Z"
    - latency: 1.25347ms
      message: 'network-check-target-ip-10-0-128-177: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:22:32Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T19:56:31Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-177-to-network-check-target-ip-10-0-133-137
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-177.ec2.internal
      uid: 9e218f80-3cca-4043-9e35-60d335fd318a
    resourceVersion: "54251"
    uid: bcc69b93-be14-43a8-9c6f-12c25f1db161
  spec:
    sourcePod: network-check-source-989f8b8dc-cxzsr
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T20:03:32Z"
      message: 'network-check-target-ip-10-0-133-137: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.973161ms
      message: 'network-check-target-ip-10-0-133-137: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:31:32Z"
    - latency: 1.988766ms
      message: 'network-check-target-ip-10-0-133-137: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:30:32Z"
    - latency: 2.041405ms
      message: 'network-check-target-ip-10-0-133-137: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:29:32Z"
    - latency: 1.972572ms
      message: 'network-check-target-ip-10-0-133-137: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:28:32Z"
    - latency: 1.876794ms
      message: 'network-check-target-ip-10-0-133-137: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:27:32Z"
    - latency: 2.060715ms
      message: 'network-check-target-ip-10-0-133-137: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:26:32Z"
    - latency: 1.963526ms
      message: 'network-check-target-ip-10-0-133-137: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:25:32Z"
    - latency: 1.817256ms
      message: 'network-check-target-ip-10-0-133-137: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:24:32Z"
    - latency: 1.638934ms
      message: 'network-check-target-ip-10-0-133-137: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:23:32Z"
    - latency: 1.813935ms
      message: 'network-check-target-ip-10-0-133-137: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:22:32Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T19:56:31Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-177-to-network-check-target-ip-10-0-142-141
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-177.ec2.internal
      uid: 9e218f80-3cca-4043-9e35-60d335fd318a
    resourceVersion: "54250"
    uid: a0cde09d-ec29-492b-8445-c99d07ce7bf5
  spec:
    sourcePod: network-check-source-989f8b8dc-cxzsr
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T20:03:32Z"
      message: 'network-check-target-ip-10-0-142-141: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.918183ms
      message: 'network-check-target-ip-10-0-142-141: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:31:32Z"
    - latency: 2.401434ms
      message: 'network-check-target-ip-10-0-142-141: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:30:32Z"
    - latency: 2.005544ms
      message: 'network-check-target-ip-10-0-142-141: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:29:32Z"
    - latency: 2.441296ms
      message: 'network-check-target-ip-10-0-142-141: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:28:32Z"
    - latency: 2.006609ms
      message: 'network-check-target-ip-10-0-142-141: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:27:32Z"
    - latency: 2.320143ms
      message: 'network-check-target-ip-10-0-142-141: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:26:32Z"
    - latency: 1.696845ms
      message: 'network-check-target-ip-10-0-142-141: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:25:32Z"
    - latency: 2.456282ms
      message: 'network-check-target-ip-10-0-142-141: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:24:32Z"
    - latency: 2.327158ms
      message: 'network-check-target-ip-10-0-142-141: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:23:32Z"
    - latency: 2.236746ms
      message: 'network-check-target-ip-10-0-142-141: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:22:32Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T19:56:31Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-177-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-177.ec2.internal
      uid: 9e218f80-3cca-4043-9e35-60d335fd318a
    resourceVersion: "55234"
    uid: 68aa3f26-cc4b-41df-9621-279951d7b0a5
  spec:
    sourcePod: network-check-source-989f8b8dc-cxzsr
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T20:02:32Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 871.64µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:32:32Z"
    - latency: 1.776844ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T20:32:32Z"
    - latency: 908.237µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:31:32Z"
    - latency: 1.922185ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T20:31:32Z"
    - latency: 817.057µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:30:32Z"
    - latency: 2.025763ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T20:30:32Z"
    - latency: 1.106829ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:29:32Z"
    - latency: 1.811956ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T20:29:32Z"
    - latency: 898.169µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:28:32Z"
    - latency: 1.807001ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T20:28:32Z"
kind: List
metadata:
  resourceVersion: ""