apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T10:50:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-92-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-92.ec2.internal
      uid: ed5526dd-77d7-4849-962d-32a2c9a3943d
    resourceVersion: "87822"
    uid: 6819dc5d-7fdc-4685-9766-91ce689c4764
  spec:
    sourcePod: network-check-source-869dcfcdcd-gszj8
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T10:57:03Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 962.612µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T12:07:03Z"
    - latency: 985.042µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T12:06:03Z"
    - latency: 935.094µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T12:05:03Z"
    - latency: 956.788µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T12:04:03Z"
    - latency: 950.044µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T12:03:03Z"
    - latency: 1.383806ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T12:02:03Z"
    - latency: 787.275µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T12:01:03Z"
    - latency: 1.08886ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T12:00:03Z"
    - latency: 1.083888ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:59:03Z"
    - latency: 892.728µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:58:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T10:50:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-92-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-92.ec2.internal
      uid: ed5526dd-77d7-4849-962d-32a2c9a3943d
    resourceVersion: "84197"
    uid: 0de2a55a-d93e-441d-9926-48b9247adaf1
  spec:
    sourcePod: network-check-source-869dcfcdcd-gszj8
    targetEndpoint: a9f99d79a1cb948f89e2ffe9d99cac69-d281f5b9e2c38e54.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T10:56:03Z"
      message: 'load-balancer-api-external: tcp connection to a9f99d79a1cb948f89e2ffe9d99cac69-d281f5b9e2c38e54.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.374245ms
      message: 'load-balancer-api-external: tcp connection to a9f99d79a1cb948f89e2ffe9d99cac69-d281f5b9e2c38e54.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T12:02:03Z"
    - latency: 7.953273ms
      message: 'load-balancer-api-external: resolved host name a9f99d79a1cb948f89e2ffe9d99cac69-d281f5b9e2c38e54.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T12:02:03Z"
    - latency: 4.114718ms
      message: 'load-balancer-api-external: tcp connection to a9f99d79a1cb948f89e2ffe9d99cac69-d281f5b9e2c38e54.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T12:01:03Z"
    - latency: 9.174808ms
      message: 'load-balancer-api-external: resolved host name a9f99d79a1cb948f89e2ffe9d99cac69-d281f5b9e2c38e54.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T12:01:03Z"
    - latency: 4.299102ms
      message: 'load-balancer-api-external: tcp connection to a9f99d79a1cb948f89e2ffe9d99cac69-d281f5b9e2c38e54.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T12:00:03Z"
    - latency: 9.767738ms
      message: 'load-balancer-api-external: resolved host name a9f99d79a1cb948f89e2ffe9d99cac69-d281f5b9e2c38e54.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T12:00:03Z"
    - latency: 5.6526ms
      message: 'load-balancer-api-external: tcp connection to a9f99d79a1cb948f89e2ffe9d99cac69-d281f5b9e2c38e54.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:59:03Z"
    - latency: 10.003202ms
      message: 'load-balancer-api-external: resolved host name a9f99d79a1cb948f89e2ffe9d99cac69-d281f5b9e2c38e54.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T11:59:03Z"
    - latency: 3.802398ms
      message: 'load-balancer-api-external: tcp connection to a9f99d79a1cb948f89e2ffe9d99cac69-d281f5b9e2c38e54.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:58:03Z"
    - latency: 9.0816ms
      message: 'load-balancer-api-external: resolved host name a9f99d79a1cb948f89e2ffe9d99cac69-d281f5b9e2c38e54.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T11:58:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T10:50:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-92-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-92.ec2.internal
      uid: ed5526dd-77d7-4849-962d-32a2c9a3943d
    resourceVersion: "84198"
    uid: 8d7f1375-8aec-4469-bdbc-ae4961f1578c
  spec:
    sourcePod: network-check-source-869dcfcdcd-gszj8
    targetEndpoint: a9f99d79a1cb948f89e2ffe9d99cac69-d281f5b9e2c38e54.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T10:56:03Z"
      message: 'load-balancer-api-internal: tcp connection to a9f99d79a1cb948f89e2ffe9d99cac69-d281f5b9e2c38e54.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 10.125242ms
      message: 'load-balancer-api-internal: tcp connection to a9f99d79a1cb948f89e2ffe9d99cac69-d281f5b9e2c38e54.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T12:02:03Z"
    - latency: 7.974685ms
      message: 'load-balancer-api-internal: resolved host name a9f99d79a1cb948f89e2ffe9d99cac69-d281f5b9e2c38e54.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T12:02:03Z"
    - latency: 4.120507ms
      message: 'load-balancer-api-internal: tcp connection to a9f99d79a1cb948f89e2ffe9d99cac69-d281f5b9e2c38e54.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T12:01:03Z"
    - latency: 9.126994ms
      message: 'load-balancer-api-internal: resolved host name a9f99d79a1cb948f89e2ffe9d99cac69-d281f5b9e2c38e54.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T12:01:03Z"
    - latency: 5.259045ms
      message: 'load-balancer-api-internal: tcp connection to a9f99d79a1cb948f89e2ffe9d99cac69-d281f5b9e2c38e54.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T12:00:03Z"
    - latency: 9.867316ms
      message: 'load-balancer-api-internal: resolved host name a9f99d79a1cb948f89e2ffe9d99cac69-d281f5b9e2c38e54.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T12:00:03Z"
    - latency: 6.36735ms
      message: 'load-balancer-api-internal: tcp connection to a9f99d79a1cb948f89e2ffe9d99cac69-d281f5b9e2c38e54.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:59:03Z"
    - latency: 9.892113ms
      message: 'load-balancer-api-internal: resolved host name a9f99d79a1cb948f89e2ffe9d99cac69-d281f5b9e2c38e54.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T11:59:03Z"
    - latency: 4.526319ms
      message: 'load-balancer-api-internal: tcp connection to a9f99d79a1cb948f89e2ffe9d99cac69-d281f5b9e2c38e54.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:58:03Z"
    - latency: 9.175282ms
      message: 'load-balancer-api-internal: resolved host name a9f99d79a1cb948f89e2ffe9d99cac69-d281f5b9e2c38e54.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T11:58:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T10:50:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-92-to-network-check-target-ip-10-0-133-26
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-92.ec2.internal
      uid: ed5526dd-77d7-4849-962d-32a2c9a3943d
    resourceVersion: "87820"
    uid: 89b90de5-a9fa-455a-a1ba-20c7a8c7fa48
  spec:
    sourcePod: network-check-source-869dcfcdcd-gszj8
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T10:57:03Z"
      message: 'network-check-target-ip-10-0-133-26: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.122624ms
      message: 'network-check-target-ip-10-0-133-26: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T12:07:03Z"
    - latency: 1.988447ms
      message: 'network-check-target-ip-10-0-133-26: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T12:06:03Z"
    - latency: 2.306533ms
      message: 'network-check-target-ip-10-0-133-26: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T12:05:03Z"
    - latency: 2.202301ms
      message: 'network-check-target-ip-10-0-133-26: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T12:04:03Z"
    - latency: 2.597007ms
      message: 'network-check-target-ip-10-0-133-26: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T12:03:03Z"
    - latency: 2.177182ms
      message: 'network-check-target-ip-10-0-133-26: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T12:02:03Z"
    - latency: 2.104646ms
      message: 'network-check-target-ip-10-0-133-26: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T12:01:03Z"
    - latency: 2.47233ms
      message: 'network-check-target-ip-10-0-133-26: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T12:00:03Z"
    - latency: 2.112126ms
      message: 'network-check-target-ip-10-0-133-26: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:59:03Z"
    - latency: 2.208944ms
      message: 'network-check-target-ip-10-0-133-26: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:58:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T10:50:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-92-to-network-check-target-ip-10-0-134-178
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-92.ec2.internal
      uid: ed5526dd-77d7-4849-962d-32a2c9a3943d
    resourceVersion: "87821"
    uid: 3b89c841-d8a2-42f2-b315-77f577e4e20a
  spec:
    sourcePod: network-check-source-869dcfcdcd-gszj8
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T10:57:03Z"
      message: 'network-check-target-ip-10-0-134-178: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.410549ms
      message: 'network-check-target-ip-10-0-134-178: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T12:07:03Z"
    - latency: 1.955096ms
      message: 'network-check-target-ip-10-0-134-178: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T12:06:03Z"
    - latency: 2.156216ms
      message: 'network-check-target-ip-10-0-134-178: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T12:05:03Z"
    - latency: 2.243212ms
      message: 'network-check-target-ip-10-0-134-178: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T12:04:03Z"
    - latency: 2.178179ms
      message: 'network-check-target-ip-10-0-134-178: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T12:03:03Z"
    - latency: 2.071011ms
      message: 'network-check-target-ip-10-0-134-178: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T12:02:03Z"
    - latency: 2.073524ms
      message: 'network-check-target-ip-10-0-134-178: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T12:01:03Z"
    - latency: 2.339379ms
      message: 'network-check-target-ip-10-0-134-178: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T12:00:03Z"
    - latency: 2.103678ms
      message: 'network-check-target-ip-10-0-134-178: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:59:03Z"
    - latency: 2.101361ms
      message: 'network-check-target-ip-10-0-134-178: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:58:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T10:50:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-92-to-network-check-target-ip-10-0-137-92
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-92.ec2.internal
      uid: ed5526dd-77d7-4849-962d-32a2c9a3943d
    resourceVersion: "87819"
    uid: c573f542-67a0-4792-8ac0-bb011dbefdf2
  spec:
    sourcePod: network-check-source-869dcfcdcd-gszj8
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T10:57:03Z"
      message: 'network-check-target-ip-10-0-137-92: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 918.583µs
      message: 'network-check-target-ip-10-0-137-92: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T12:07:03Z"
    - latency: 791.775µs
      message: 'network-check-target-ip-10-0-137-92: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T12:06:03Z"
    - latency: 1.116684ms
      message: 'network-check-target-ip-10-0-137-92: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T12:05:03Z"
    - latency: 1.59433ms
      message: 'network-check-target-ip-10-0-137-92: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T12:04:03Z"
    - latency: 1.30228ms
      message: 'network-check-target-ip-10-0-137-92: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T12:03:03Z"
    - latency: 1.071318ms
      message: 'network-check-target-ip-10-0-137-92: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T12:02:03Z"
    - latency: 1.178454ms
      message: 'network-check-target-ip-10-0-137-92: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T12:01:03Z"
    - latency: 914.594µs
      message: 'network-check-target-ip-10-0-137-92: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T12:00:03Z"
    - latency: 1.172673ms
      message: 'network-check-target-ip-10-0-137-92: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:59:03Z"
    - latency: 948.069µs
      message: 'network-check-target-ip-10-0-137-92: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:58:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T10:50:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-92-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-92.ec2.internal
      uid: ed5526dd-77d7-4849-962d-32a2c9a3943d
    resourceVersion: "84196"
    uid: d2e9c086-1fe3-43de-966b-90666a82a159
  spec:
    sourcePod: network-check-source-869dcfcdcd-gszj8
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T10:56:03Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 948.924µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T12:02:03Z"
    - latency: 1.932779ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T12:02:03Z"
    - latency: 1.156348ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T12:01:03Z"
    - latency: 1.835123ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T12:01:03Z"
    - latency: 841.241µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T12:00:03Z"
    - latency: 2.106812ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T12:00:03Z"
    - latency: 973.077µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:59:03Z"
    - latency: 2.171283ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T11:59:03Z"
    - latency: 1.172339ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:58:03Z"
    - latency: 1.820046ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T11:58:03Z"
kind: List
metadata:
  resourceVersion: ""