apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T19:34:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-97-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-97.ec2.internal
      uid: a0299f3c-a54f-46a9-9aa9-50f830a75356
    resourceVersion: "68796"
    uid: dd64bf1b-af12-4d38-a416-ae0a9ef30d10
  spec:
    sourcePod: network-check-source-6f8b768455-lf4dn
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T19:41:02Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.094181ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T20:09:02Z"
    - latency: 966.124µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T20:08:02Z"
    - latency: 990.851µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T20:07:02Z"
    - latency: 1.682286ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T20:06:02Z"
    - latency: 1.149159ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T20:05:02Z"
    - latency: 1.148219ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T20:04:02Z"
    - latency: 995.33µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T20:03:02Z"
    - latency: 1.332664ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T20:02:02Z"
    - latency: 1.797626ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T20:01:02Z"
    - latency: 1.217412ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T20:00:02Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T19:34:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-97-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-97.ec2.internal
      uid: a0299f3c-a54f-46a9-9aa9-50f830a75356
    resourceVersion: "69628"
    uid: 3b4ce3fd-d95d-489e-9fd0-1e8975d778fb
  spec:
    sourcePod: network-check-source-6f8b768455-lf4dn
    targetEndpoint: a967f5d11ae1742838df16b28457a97d-ce4c780847635e77.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T19:40:02Z"
      message: 'load-balancer-api-external: tcp connection to a967f5d11ae1742838df16b28457a97d-ce4c780847635e77.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.235454ms
      message: 'load-balancer-api-external: tcp connection to a967f5d11ae1742838df16b28457a97d-ce4c780847635e77.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T20:10:02Z"
    - latency: 8.652304ms
      message: 'load-balancer-api-external: resolved host name a967f5d11ae1742838df16b28457a97d-ce4c780847635e77.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T20:10:02Z"
    - latency: 4.010251ms
      message: 'load-balancer-api-external: tcp connection to a967f5d11ae1742838df16b28457a97d-ce4c780847635e77.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T20:09:02Z"
    - latency: 9.204912ms
      message: 'load-balancer-api-external: resolved host name a967f5d11ae1742838df16b28457a97d-ce4c780847635e77.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T20:09:02Z"
    - latency: 5.416114ms
      message: 'load-balancer-api-external: tcp connection to a967f5d11ae1742838df16b28457a97d-ce4c780847635e77.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T20:08:02Z"
    - latency: 8.402444ms
      message: 'load-balancer-api-external: resolved host name a967f5d11ae1742838df16b28457a97d-ce4c780847635e77.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T20:08:02Z"
    - latency: 4.787467ms
      message: 'load-balancer-api-external: tcp connection to a967f5d11ae1742838df16b28457a97d-ce4c780847635e77.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T20:07:02Z"
    - latency: 9.141613ms
      message: 'load-balancer-api-external: resolved host name a967f5d11ae1742838df16b28457a97d-ce4c780847635e77.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T20:07:02Z"
    - latency: 5.582058ms
      message: 'load-balancer-api-external: tcp connection to a967f5d11ae1742838df16b28457a97d-ce4c780847635e77.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T20:06:02Z"
    - latency: 7.409432ms
      message: 'load-balancer-api-external: resolved host name a967f5d11ae1742838df16b28457a97d-ce4c780847635e77.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T20:06:02Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T19:34:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-97-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-97.ec2.internal
      uid: a0299f3c-a54f-46a9-9aa9-50f830a75356
    resourceVersion: "69627"
    uid: b063ab60-eb89-449e-b088-33254f458156
  spec:
    sourcePod: network-check-source-6f8b768455-lf4dn
    targetEndpoint: a967f5d11ae1742838df16b28457a97d-ce4c780847635e77.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T19:40:02Z"
      message: 'load-balancer-api-internal: tcp connection to a967f5d11ae1742838df16b28457a97d-ce4c780847635e77.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.320014ms
      message: 'load-balancer-api-internal: tcp connection to a967f5d11ae1742838df16b28457a97d-ce4c780847635e77.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T20:10:02Z"
    - latency: 8.770988ms
      message: 'load-balancer-api-internal: resolved host name a967f5d11ae1742838df16b28457a97d-ce4c780847635e77.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T20:10:02Z"
    - latency: 4.070249ms
      message: 'load-balancer-api-internal: tcp connection to a967f5d11ae1742838df16b28457a97d-ce4c780847635e77.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T20:09:02Z"
    - latency: 9.140914ms
      message: 'load-balancer-api-internal: resolved host name a967f5d11ae1742838df16b28457a97d-ce4c780847635e77.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T20:09:02Z"
    - latency: 5.485781ms
      message: 'load-balancer-api-internal: tcp connection to a967f5d11ae1742838df16b28457a97d-ce4c780847635e77.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T20:08:02Z"
    - latency: 8.452921ms
      message: 'load-balancer-api-internal: resolved host name a967f5d11ae1742838df16b28457a97d-ce4c780847635e77.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T20:08:02Z"
    - latency: 5.477178ms
      message: 'load-balancer-api-internal: tcp connection to a967f5d11ae1742838df16b28457a97d-ce4c780847635e77.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T20:07:02Z"
    - latency: 9.237312ms
      message: 'load-balancer-api-internal: resolved host name a967f5d11ae1742838df16b28457a97d-ce4c780847635e77.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T20:07:02Z"
    - latency: 5.714155ms
      message: 'load-balancer-api-internal: tcp connection to a967f5d11ae1742838df16b28457a97d-ce4c780847635e77.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T20:06:02Z"
    - latency: 7.498967ms
      message: 'load-balancer-api-internal: resolved host name a967f5d11ae1742838df16b28457a97d-ce4c780847635e77.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T20:06:02Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T19:34:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-97-to-network-check-target-ip-10-0-130-171
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-97.ec2.internal
      uid: a0299f3c-a54f-46a9-9aa9-50f830a75356
    resourceVersion: "68795"
    uid: 1e6eb91b-9200-4f6c-a913-ad005da595e6
  spec:
    sourcePod: network-check-source-6f8b768455-lf4dn
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T19:41:02Z"
      message: 'network-check-target-ip-10-0-130-171: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.124632ms
      message: 'network-check-target-ip-10-0-130-171: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T20:09:02Z"
    - latency: 2.320905ms
      message: 'network-check-target-ip-10-0-130-171: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T20:08:02Z"
    - latency: 2.339075ms
      message: 'network-check-target-ip-10-0-130-171: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T20:07:02Z"
    - latency: 2.384887ms
      message: 'network-check-target-ip-10-0-130-171: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T20:06:02Z"
    - latency: 2.736938ms
      message: 'network-check-target-ip-10-0-130-171: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T20:05:02Z"
    - latency: 2.399583ms
      message: 'network-check-target-ip-10-0-130-171: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T20:04:02Z"
    - latency: 2.573804ms
      message: 'network-check-target-ip-10-0-130-171: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T20:03:02Z"
    - latency: 2.124068ms
      message: 'network-check-target-ip-10-0-130-171: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T20:02:02Z"
    - latency: 2.608156ms
      message: 'network-check-target-ip-10-0-130-171: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T20:01:02Z"
    - latency: 2.363696ms
      message: 'network-check-target-ip-10-0-130-171: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T20:00:02Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T19:34:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-97-to-network-check-target-ip-10-0-137-97
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-97.ec2.internal
      uid: a0299f3c-a54f-46a9-9aa9-50f830a75356
    resourceVersion: "68793"
    uid: 41725602-056a-4c94-9871-cbc669b2bdaf
  spec:
    sourcePod: network-check-source-6f8b768455-lf4dn
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T19:41:02Z"
      message: 'network-check-target-ip-10-0-137-97: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 951.056µs
      message: 'network-check-target-ip-10-0-137-97: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T20:09:02Z"
    - latency: 1.745103ms
      message: 'network-check-target-ip-10-0-137-97: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T20:08:02Z"
    - latency: 1.078199ms
      message: 'network-check-target-ip-10-0-137-97: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T20:07:02Z"
    - latency: 1.28892ms
      message: 'network-check-target-ip-10-0-137-97: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T20:06:02Z"
    - latency: 1.37443ms
      message: 'network-check-target-ip-10-0-137-97: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T20:05:02Z"
    - latency: 1.081259ms
      message: 'network-check-target-ip-10-0-137-97: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T20:04:02Z"
    - latency: 1.028695ms
      message: 'network-check-target-ip-10-0-137-97: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T20:03:02Z"
    - latency: 1.037361ms
      message: 'network-check-target-ip-10-0-137-97: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T20:02:02Z"
    - latency: 1.836015ms
      message: 'network-check-target-ip-10-0-137-97: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T20:01:02Z"
    - latency: 1.019511ms
      message: 'network-check-target-ip-10-0-137-97: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T20:00:02Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T19:34:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-97-to-network-check-target-ip-10-0-138-43
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-97.ec2.internal
      uid: a0299f3c-a54f-46a9-9aa9-50f830a75356
    resourceVersion: "68794"
    uid: d7043ec7-db6c-495d-891c-abaef9d909a7
  spec:
    sourcePod: network-check-source-6f8b768455-lf4dn
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T19:41:02Z"
      message: 'network-check-target-ip-10-0-138-43: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.856012ms
      message: 'network-check-target-ip-10-0-138-43: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T20:09:02Z"
    - latency: 1.894128ms
      message: 'network-check-target-ip-10-0-138-43: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T20:08:02Z"
    - latency: 2.55645ms
      message: 'network-check-target-ip-10-0-138-43: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T20:07:02Z"
    - latency: 2.396525ms
      message: 'network-check-target-ip-10-0-138-43: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T20:06:02Z"
    - latency: 2.486027ms
      message: 'network-check-target-ip-10-0-138-43: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T20:05:02Z"
    - latency: 2.296327ms
      message: 'network-check-target-ip-10-0-138-43: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T20:04:02Z"
    - latency: 2.341703ms
      message: 'network-check-target-ip-10-0-138-43: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T20:03:02Z"
    - latency: 2.549499ms
      message: 'network-check-target-ip-10-0-138-43: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T20:02:02Z"
    - latency: 2.596804ms
      message: 'network-check-target-ip-10-0-138-43: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T20:01:02Z"
    - latency: 2.496537ms
      message: 'network-check-target-ip-10-0-138-43: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T20:00:02Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T19:34:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-97-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-97.ec2.internal
      uid: a0299f3c-a54f-46a9-9aa9-50f830a75356
    resourceVersion: "69626"
    uid: 6839b655-c118-4e1e-a035-f64a8b615a9b
  spec:
    sourcePod: network-check-source-6f8b768455-lf4dn
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T19:40:02Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.025137ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T20:10:02Z"
    - latency: 2.014264ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T20:10:02Z"
    - latency: 888.572µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T20:09:02Z"
    - latency: 1.637818ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T20:09:02Z"
    - latency: 970.319µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T20:08:02Z"
    - latency: 2.248403ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T20:08:02Z"
    - latency: 932.55µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T20:07:02Z"
    - latency: 1.937216ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T20:07:02Z"
    - latency: 1.237279ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T20:06:02Z"
    - latency: 2.044149ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T20:06:02Z"
kind: List
metadata:
  resourceVersion: ""