apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T12:12:11Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-186-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-186.ec2.internal
      uid: 596caa5d-8bc3-47c6-b056-804d91f5ebfe
    resourceVersion: "60864"
    uid: c2c20832-420c-45a2-8ac1-037fda20e24f
  spec:
    sourcePod: network-check-source-869dcfcdcd-th5wb
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T12:19:12Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.496005ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T12:54:12Z"
    - latency: 1.575026ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T12:53:12Z"
    - latency: 1.24203ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T12:52:12Z"
    - latency: 1.228511ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T12:51:12Z"
    - latency: 1.477425ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T12:50:12Z"
    - latency: 1.764272ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T12:49:12Z"
    - latency: 1.100086ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T12:48:12Z"
    - latency: 806.84µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T12:47:12Z"
    - latency: 1.834794ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T12:46:12Z"
    - latency: 1.194047ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T12:45:12Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T12:12:11Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-186-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-186.ec2.internal
      uid: 596caa5d-8bc3-47c6-b056-804d91f5ebfe
    resourceVersion: "60866"
    uid: 03fa3f74-0f4d-4ce8-909f-166bdf82ceea
  spec:
    sourcePod: network-check-source-869dcfcdcd-th5wb
    targetEndpoint: a8d39518f970e4511bf51f6b74e0c5e4-3c6f82d6115ea7e2.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T12:18:12Z"
      message: 'load-balancer-api-external: tcp connection to a8d39518f970e4511bf51f6b74e0c5e4-3c6f82d6115ea7e2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.023635ms
      message: 'load-balancer-api-external: tcp connection to a8d39518f970e4511bf51f6b74e0c5e4-3c6f82d6115ea7e2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T12:54:12Z"
    - latency: 6.779179ms
      message: 'load-balancer-api-external: resolved host name a8d39518f970e4511bf51f6b74e0c5e4-3c6f82d6115ea7e2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T12:54:12Z"
    - latency: 5.710365ms
      message: 'load-balancer-api-external: tcp connection to a8d39518f970e4511bf51f6b74e0c5e4-3c6f82d6115ea7e2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T12:53:12Z"
    - latency: 9.171484ms
      message: 'load-balancer-api-external: resolved host name a8d39518f970e4511bf51f6b74e0c5e4-3c6f82d6115ea7e2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T12:53:12Z"
    - latency: 5.46011ms
      message: 'load-balancer-api-external: tcp connection to a8d39518f970e4511bf51f6b74e0c5e4-3c6f82d6115ea7e2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T12:52:12Z"
    - latency: 7.918232ms
      message: 'load-balancer-api-external: resolved host name a8d39518f970e4511bf51f6b74e0c5e4-3c6f82d6115ea7e2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T12:52:12Z"
    - latency: 3.549708ms
      message: 'load-balancer-api-external: tcp connection to a8d39518f970e4511bf51f6b74e0c5e4-3c6f82d6115ea7e2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T12:51:12Z"
    - latency: 8.39275ms
      message: 'load-balancer-api-external: resolved host name a8d39518f970e4511bf51f6b74e0c5e4-3c6f82d6115ea7e2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T12:51:12Z"
    - latency: 3.675523ms
      message: 'load-balancer-api-external: tcp connection to a8d39518f970e4511bf51f6b74e0c5e4-3c6f82d6115ea7e2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T12:50:12Z"
    - latency: 8.846901ms
      message: 'load-balancer-api-external: resolved host name a8d39518f970e4511bf51f6b74e0c5e4-3c6f82d6115ea7e2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T12:50:12Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T12:12:11Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-186-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-186.ec2.internal
      uid: 596caa5d-8bc3-47c6-b056-804d91f5ebfe
    resourceVersion: "60865"
    uid: 9a22ffb5-8c7d-4a22-aa35-9c449b0c9f9f
  spec:
    sourcePod: network-check-source-869dcfcdcd-th5wb
    targetEndpoint: a8d39518f970e4511bf51f6b74e0c5e4-3c6f82d6115ea7e2.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T12:18:12Z"
      message: 'load-balancer-api-internal: tcp connection to a8d39518f970e4511bf51f6b74e0c5e4-3c6f82d6115ea7e2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.031528ms
      message: 'load-balancer-api-internal: tcp connection to a8d39518f970e4511bf51f6b74e0c5e4-3c6f82d6115ea7e2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T12:54:12Z"
    - latency: 6.749728ms
      message: 'load-balancer-api-internal: resolved host name a8d39518f970e4511bf51f6b74e0c5e4-3c6f82d6115ea7e2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T12:54:12Z"
    - latency: 5.720357ms
      message: 'load-balancer-api-internal: tcp connection to a8d39518f970e4511bf51f6b74e0c5e4-3c6f82d6115ea7e2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T12:53:12Z"
    - latency: 9.111153ms
      message: 'load-balancer-api-internal: resolved host name a8d39518f970e4511bf51f6b74e0c5e4-3c6f82d6115ea7e2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T12:53:12Z"
    - latency: 3.405113ms
      message: 'load-balancer-api-internal: tcp connection to a8d39518f970e4511bf51f6b74e0c5e4-3c6f82d6115ea7e2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T12:52:12Z"
    - latency: 7.994063ms
      message: 'load-balancer-api-internal: resolved host name a8d39518f970e4511bf51f6b74e0c5e4-3c6f82d6115ea7e2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T12:52:12Z"
    - latency: 4.331358ms
      message: 'load-balancer-api-internal: tcp connection to a8d39518f970e4511bf51f6b74e0c5e4-3c6f82d6115ea7e2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T12:51:12Z"
    - latency: 8.364238ms
      message: 'load-balancer-api-internal: resolved host name a8d39518f970e4511bf51f6b74e0c5e4-3c6f82d6115ea7e2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T12:51:12Z"
    - latency: 3.693631ms
      message: 'load-balancer-api-internal: tcp connection to a8d39518f970e4511bf51f6b74e0c5e4-3c6f82d6115ea7e2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T12:50:12Z"
    - latency: 8.812974ms
      message: 'load-balancer-api-internal: resolved host name a8d39518f970e4511bf51f6b74e0c5e4-3c6f82d6115ea7e2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T12:50:12Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T12:12:11Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-186-to-network-check-target-ip-10-0-128-78
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-186.ec2.internal
      uid: 596caa5d-8bc3-47c6-b056-804d91f5ebfe
    resourceVersion: "60862"
    uid: 24f30235-e640-4d2e-a7d7-523c30cc188a
  spec:
    sourcePod: network-check-source-869dcfcdcd-th5wb
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T12:19:12Z"
      message: 'network-check-target-ip-10-0-128-78: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.583577ms
      message: 'network-check-target-ip-10-0-128-78: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T12:54:12Z"
    - latency: 1.643235ms
      message: 'network-check-target-ip-10-0-128-78: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T12:53:12Z"
    - latency: 1.397446ms
      message: 'network-check-target-ip-10-0-128-78: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T12:52:12Z"
    - latency: 1.700099ms
      message: 'network-check-target-ip-10-0-128-78: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T12:51:12Z"
    - latency: 2.060818ms
      message: 'network-check-target-ip-10-0-128-78: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T12:50:12Z"
    - latency: 1.91515ms
      message: 'network-check-target-ip-10-0-128-78: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T12:49:12Z"
    - latency: 1.59988ms
      message: 'network-check-target-ip-10-0-128-78: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T12:48:12Z"
    - latency: 1.673763ms
      message: 'network-check-target-ip-10-0-128-78: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T12:47:12Z"
    - latency: 2.204986ms
      message: 'network-check-target-ip-10-0-128-78: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T12:46:12Z"
    - latency: 1.798894ms
      message: 'network-check-target-ip-10-0-128-78: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T12:45:12Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T12:12:11Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-186-to-network-check-target-ip-10-0-135-186
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-186.ec2.internal
      uid: 596caa5d-8bc3-47c6-b056-804d91f5ebfe
    resourceVersion: "60861"
    uid: 9bca3245-aef6-41fe-bb45-26ea2aa2209f
  spec:
    sourcePod: network-check-source-869dcfcdcd-th5wb
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T12:19:12Z"
      message: 'network-check-target-ip-10-0-135-186: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.482473ms
      message: 'network-check-target-ip-10-0-135-186: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T12:54:12Z"
    - latency: 854.666µs
      message: 'network-check-target-ip-10-0-135-186: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T12:53:12Z"
    - latency: 876.077µs
      message: 'network-check-target-ip-10-0-135-186: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T12:52:12Z"
    - latency: 848.437µs
      message: 'network-check-target-ip-10-0-135-186: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T12:51:12Z"
    - latency: 867.202µs
      message: 'network-check-target-ip-10-0-135-186: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T12:50:12Z"
    - latency: 1.19115ms
      message: 'network-check-target-ip-10-0-135-186: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T12:49:12Z"
    - latency: 1.533983ms
      message: 'network-check-target-ip-10-0-135-186: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T12:48:12Z"
    - latency: 825.44µs
      message: 'network-check-target-ip-10-0-135-186: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T12:47:12Z"
    - latency: 1.2759ms
      message: 'network-check-target-ip-10-0-135-186: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T12:46:12Z"
    - latency: 908.288µs
      message: 'network-check-target-ip-10-0-135-186: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T12:45:12Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T12:12:11Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-186-to-network-check-target-ip-10-0-141-123
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-186.ec2.internal
      uid: 596caa5d-8bc3-47c6-b056-804d91f5ebfe
    resourceVersion: "60860"
    uid: a0b1ce02-281f-4f08-8384-52a64c27320c
  spec:
    sourcePod: network-check-source-869dcfcdcd-th5wb
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T12:19:12Z"
      message: 'network-check-target-ip-10-0-141-123: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.309458ms
      message: 'network-check-target-ip-10-0-141-123: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T12:54:12Z"
    - latency: 2.659693ms
      message: 'network-check-target-ip-10-0-141-123: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T12:53:12Z"
    - latency: 1.997476ms
      message: 'network-check-target-ip-10-0-141-123: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T12:52:12Z"
    - latency: 2.156543ms
      message: 'network-check-target-ip-10-0-141-123: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T12:51:12Z"
    - latency: 2.094937ms
      message: 'network-check-target-ip-10-0-141-123: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T12:50:12Z"
    - latency: 2.198262ms
      message: 'network-check-target-ip-10-0-141-123: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T12:49:12Z"
    - latency: 2.495814ms
      message: 'network-check-target-ip-10-0-141-123: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T12:48:12Z"
    - latency: 1.86914ms
      message: 'network-check-target-ip-10-0-141-123: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T12:47:12Z"
    - latency: 2.31806ms
      message: 'network-check-target-ip-10-0-141-123: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T12:46:12Z"
    - latency: 2.024942ms
      message: 'network-check-target-ip-10-0-141-123: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T12:45:12Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T12:12:11Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-186-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-186.ec2.internal
      uid: 596caa5d-8bc3-47c6-b056-804d91f5ebfe
    resourceVersion: "60863"
    uid: 50d100e5-1a52-4a7b-b944-dd23b1ebc787
  spec:
    sourcePod: network-check-source-869dcfcdcd-th5wb
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T12:18:12Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 884.57µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T12:54:12Z"
    - latency: 2.024793ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T12:54:12Z"
    - latency: 846.672µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T12:53:12Z"
    - latency: 2.033531ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T12:53:12Z"
    - latency: 829.008µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T12:52:12Z"
    - latency: 2.056854ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T12:52:12Z"
    - latency: 837.47µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T12:51:12Z"
    - latency: 2.032585ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T12:51:12Z"
    - latency: 929.533µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T12:50:12Z"
    - latency: 2.158935ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T12:50:12Z"
kind: List
metadata:
  resourceVersion: ""