apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T18:38:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-52-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-52.ec2.internal
      uid: f4372310-947c-4ba0-84b2-43fee60885d2
    resourceVersion: "41527"
    uid: b089759a-01a3-4f11-a512-23867ef6d1e6
  spec:
    sourcePod: network-check-source-7d88cb55d8-7bqvr
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T18:45:48Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.146837ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T19:13:48Z"
    - latency: 1.539674ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T19:12:48Z"
    - latency: 913.654µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T19:11:48Z"
    - latency: 3.622176ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T19:10:48Z"
    - latency: 1.076704ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T19:09:48Z"
    - latency: 776.409µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T19:08:48Z"
    - latency: 1.061044ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T19:07:48Z"
    - latency: 1.248604ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T19:06:48Z"
    - latency: 1.287029ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T19:05:48Z"
    - latency: 1.052249ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T19:04:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T18:38:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-52-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-52.ec2.internal
      uid: f4372310-947c-4ba0-84b2-43fee60885d2
    resourceVersion: "42478"
    uid: b5823b64-d57c-4d23-98f3-e9dc16f1cd88
  spec:
    sourcePod: network-check-source-7d88cb55d8-7bqvr
    targetEndpoint: ad8dcae205265450284ac109fa72502f-f5730cffa4de77d9.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T18:44:48Z"
      message: 'load-balancer-api-external: tcp connection to ad8dcae205265450284ac109fa72502f-f5730cffa4de77d9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.547371ms
      message: 'load-balancer-api-external: tcp connection to ad8dcae205265450284ac109fa72502f-f5730cffa4de77d9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T19:14:48Z"
    - latency: 8.978404ms
      message: 'load-balancer-api-external: resolved host name ad8dcae205265450284ac109fa72502f-f5730cffa4de77d9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T19:14:48Z"
    - latency: 6.079116ms
      message: 'load-balancer-api-external: tcp connection to ad8dcae205265450284ac109fa72502f-f5730cffa4de77d9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T19:13:48Z"
    - latency: 9.865248ms
      message: 'load-balancer-api-external: resolved host name ad8dcae205265450284ac109fa72502f-f5730cffa4de77d9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T19:13:48Z"
    - latency: 5.576551ms
      message: 'load-balancer-api-external: tcp connection to ad8dcae205265450284ac109fa72502f-f5730cffa4de77d9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T19:12:48Z"
    - latency: 9.900068ms
      message: 'load-balancer-api-external: resolved host name ad8dcae205265450284ac109fa72502f-f5730cffa4de77d9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T19:12:48Z"
    - latency: 4.907139ms
      message: 'load-balancer-api-external: tcp connection to ad8dcae205265450284ac109fa72502f-f5730cffa4de77d9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T19:11:48Z"
    - latency: 7.365369ms
      message: 'load-balancer-api-external: resolved host name ad8dcae205265450284ac109fa72502f-f5730cffa4de77d9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T19:11:48Z"
    - latency: 6.840744ms
      message: 'load-balancer-api-external: tcp connection to ad8dcae205265450284ac109fa72502f-f5730cffa4de77d9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T19:10:48Z"
    - latency: 28.64466ms
      message: 'load-balancer-api-external: resolved host name ad8dcae205265450284ac109fa72502f-f5730cffa4de77d9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T19:10:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T18:38:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-52-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-52.ec2.internal
      uid: f4372310-947c-4ba0-84b2-43fee60885d2
    resourceVersion: "42477"
    uid: 4d5f2271-020c-4293-ba55-a17a54123298
  spec:
    sourcePod: network-check-source-7d88cb55d8-7bqvr
    targetEndpoint: ad8dcae205265450284ac109fa72502f-f5730cffa4de77d9.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T18:44:48Z"
      message: 'load-balancer-api-internal: tcp connection to ad8dcae205265450284ac109fa72502f-f5730cffa4de77d9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.537407ms
      message: 'load-balancer-api-internal: tcp connection to ad8dcae205265450284ac109fa72502f-f5730cffa4de77d9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T19:14:48Z"
    - latency: 8.156385ms
      message: 'load-balancer-api-internal: resolved host name ad8dcae205265450284ac109fa72502f-f5730cffa4de77d9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T19:14:48Z"
    - latency: 6.512145ms
      message: 'load-balancer-api-internal: tcp connection to ad8dcae205265450284ac109fa72502f-f5730cffa4de77d9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T19:13:48Z"
    - latency: 9.768075ms
      message: 'load-balancer-api-internal: resolved host name ad8dcae205265450284ac109fa72502f-f5730cffa4de77d9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T19:13:48Z"
    - latency: 5.505756ms
      message: 'load-balancer-api-internal: tcp connection to ad8dcae205265450284ac109fa72502f-f5730cffa4de77d9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T19:12:48Z"
    - latency: 9.818238ms
      message: 'load-balancer-api-internal: resolved host name ad8dcae205265450284ac109fa72502f-f5730cffa4de77d9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T19:12:48Z"
    - latency: 4.855205ms
      message: 'load-balancer-api-internal: tcp connection to ad8dcae205265450284ac109fa72502f-f5730cffa4de77d9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T19:11:48Z"
    - latency: 7.402087ms
      message: 'load-balancer-api-internal: resolved host name ad8dcae205265450284ac109fa72502f-f5730cffa4de77d9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T19:11:48Z"
    - latency: 7.569845ms
      message: 'load-balancer-api-internal: tcp connection to ad8dcae205265450284ac109fa72502f-f5730cffa4de77d9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T19:10:48Z"
    - latency: 24.343839ms
      message: 'load-balancer-api-internal: resolved host name ad8dcae205265450284ac109fa72502f-f5730cffa4de77d9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T19:10:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T18:38:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-52-to-network-check-target-ip-10-0-129-174
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-52.ec2.internal
      uid: f4372310-947c-4ba0-84b2-43fee60885d2
    resourceVersion: "41526"
    uid: bfd54af7-bb49-4bf4-ad04-d9f8a7a4623f
  spec:
    sourcePod: network-check-source-7d88cb55d8-7bqvr
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T18:45:48Z"
      message: 'network-check-target-ip-10-0-129-174: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.294153ms
      message: 'network-check-target-ip-10-0-129-174: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T19:13:48Z"
    - latency: 2.040563ms
      message: 'network-check-target-ip-10-0-129-174: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T19:12:48Z"
    - latency: 2.050998ms
      message: 'network-check-target-ip-10-0-129-174: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T19:11:48Z"
    - latency: 8.013822ms
      message: 'network-check-target-ip-10-0-129-174: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T19:10:48Z"
    - latency: 2.184396ms
      message: 'network-check-target-ip-10-0-129-174: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T19:09:48Z"
    - latency: 1.76797ms
      message: 'network-check-target-ip-10-0-129-174: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T19:08:48Z"
    - latency: 2.057604ms
      message: 'network-check-target-ip-10-0-129-174: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T19:07:48Z"
    - latency: 2.137012ms
      message: 'network-check-target-ip-10-0-129-174: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T19:06:48Z"
    - latency: 2.188407ms
      message: 'network-check-target-ip-10-0-129-174: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T19:05:48Z"
    - latency: 2.069637ms
      message: 'network-check-target-ip-10-0-129-174: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T19:04:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T18:38:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-52-to-network-check-target-ip-10-0-137-187
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-52.ec2.internal
      uid: f4372310-947c-4ba0-84b2-43fee60885d2
    resourceVersion: "41524"
    uid: 103265fb-f39c-4f80-951c-9d47ea11f341
  spec:
    sourcePod: network-check-source-7d88cb55d8-7bqvr
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T18:45:48Z"
      message: 'network-check-target-ip-10-0-137-187: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.571976ms
      message: 'network-check-target-ip-10-0-137-187: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T19:13:48Z"
    - latency: 2.396977ms
      message: 'network-check-target-ip-10-0-137-187: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T19:12:48Z"
    - latency: 2.381722ms
      message: 'network-check-target-ip-10-0-137-187: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T19:11:48Z"
    - latency: 2.811508ms
      message: 'network-check-target-ip-10-0-137-187: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T19:10:48Z"
    - latency: 2.30686ms
      message: 'network-check-target-ip-10-0-137-187: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T19:09:48Z"
    - latency: 2.099072ms
      message: 'network-check-target-ip-10-0-137-187: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T19:08:48Z"
    - latency: 2.352023ms
      message: 'network-check-target-ip-10-0-137-187: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T19:07:48Z"
    - latency: 2.426693ms
      message: 'network-check-target-ip-10-0-137-187: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T19:06:48Z"
    - latency: 2.559727ms
      message: 'network-check-target-ip-10-0-137-187: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T19:05:48Z"
    - latency: 2.386368ms
      message: 'network-check-target-ip-10-0-137-187: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T19:04:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T18:38:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-52-to-network-check-target-ip-10-0-137-52
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-52.ec2.internal
      uid: f4372310-947c-4ba0-84b2-43fee60885d2
    resourceVersion: "41525"
    uid: 1af466a2-6e46-4e25-91b1-4b7dd50a0a4c
  spec:
    sourcePod: network-check-source-7d88cb55d8-7bqvr
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T18:45:48Z"
      message: 'network-check-target-ip-10-0-137-52: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.539192ms
      message: 'network-check-target-ip-10-0-137-52: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T19:13:48Z"
    - latency: 1.210517ms
      message: 'network-check-target-ip-10-0-137-52: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T19:12:48Z"
    - latency: 1.169307ms
      message: 'network-check-target-ip-10-0-137-52: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T19:11:48Z"
    - latency: 1.782061ms
      message: 'network-check-target-ip-10-0-137-52: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T19:10:48Z"
    - latency: 1.204268ms
      message: 'network-check-target-ip-10-0-137-52: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T19:09:48Z"
    - latency: 1.337064ms
      message: 'network-check-target-ip-10-0-137-52: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T19:08:48Z"
    - latency: 976.091µs
      message: 'network-check-target-ip-10-0-137-52: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T19:07:48Z"
    - latency: 970.986µs
      message: 'network-check-target-ip-10-0-137-52: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T19:06:48Z"
    - latency: 938.489µs
      message: 'network-check-target-ip-10-0-137-52: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T19:05:48Z"
    - latency: 918.595µs
      message: 'network-check-target-ip-10-0-137-52: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T19:04:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T18:38:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-52-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-52.ec2.internal
      uid: f4372310-947c-4ba0-84b2-43fee60885d2
    resourceVersion: "42476"
    uid: 0f374f98-c419-4e2c-bcaa-bbd9460c490f
  spec:
    sourcePod: network-check-source-7d88cb55d8-7bqvr
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T18:44:48Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.067097ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T19:14:48Z"
    - latency: 1.318987ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T19:14:48Z"
    - latency: 957.218µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T19:13:48Z"
    - latency: 2.055432ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T19:13:48Z"
    - latency: 999.83µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T19:12:48Z"
    - latency: 2.439335ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T19:12:48Z"
    - latency: 868.155µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T19:11:48Z"
    - latency: 2.059937ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T19:11:48Z"
    - latency: 11.217304ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T19:10:48Z"
    - latency: 3.179486ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T19:10:48Z"
kind: List
metadata:
  resourceVersion: ""