apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T10:31:53Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-34-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-34.ec2.internal
      uid: 769ee7c0-a719-4396-a3a1-6e4a10381610
    resourceVersion: "55004"
    uid: 65081306-3bbd-4554-bac3-9906578042ea
  spec:
    sourcePod: network-check-source-989f8b8dc-2fvvk
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T10:38:55Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 939.347µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T11:06:55Z"
    - latency: 1.130266ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T11:05:55Z"
    - latency: 1.119284ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T11:04:55Z"
    - latency: 1.127652ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T11:03:55Z"
    - latency: 847.703µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T11:02:55Z"
    - latency: 849.657µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T11:01:55Z"
    - latency: 1.319877ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T11:00:55Z"
    - latency: 846.212µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T10:59:55Z"
    - latency: 875.794µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T10:58:55Z"
    - latency: 893.825µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T10:57:55Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T10:31:53Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-34-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-34.ec2.internal
      uid: 769ee7c0-a719-4396-a3a1-6e4a10381610
    resourceVersion: "56003"
    uid: 484abe49-ebbf-405c-ad88-30ea108149c6
  spec:
    sourcePod: network-check-source-989f8b8dc-2fvvk
    targetEndpoint: a29d4c3db15794cefa8a5d3ad55db52a-bde0e8c2d305ce6f.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T10:37:55Z"
      message: 'load-balancer-api-external: tcp connection to a29d4c3db15794cefa8a5d3ad55db52a-bde0e8c2d305ce6f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 13.070357ms
      message: 'load-balancer-api-external: tcp connection to a29d4c3db15794cefa8a5d3ad55db52a-bde0e8c2d305ce6f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T11:07:55Z"
    - latency: 10.773199ms
      message: 'load-balancer-api-external: resolved host name a29d4c3db15794cefa8a5d3ad55db52a-bde0e8c2d305ce6f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T11:07:55Z"
    - latency: 4.923961ms
      message: 'load-balancer-api-external: tcp connection to a29d4c3db15794cefa8a5d3ad55db52a-bde0e8c2d305ce6f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T11:06:55Z"
    - latency: 10.23255ms
      message: 'load-balancer-api-external: resolved host name a29d4c3db15794cefa8a5d3ad55db52a-bde0e8c2d305ce6f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T11:06:55Z"
    - latency: 3.897928ms
      message: 'load-balancer-api-external: tcp connection to a29d4c3db15794cefa8a5d3ad55db52a-bde0e8c2d305ce6f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T11:05:55Z"
    - latency: 6.872477ms
      message: 'load-balancer-api-external: resolved host name a29d4c3db15794cefa8a5d3ad55db52a-bde0e8c2d305ce6f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T11:05:55Z"
    - latency: 6.262386ms
      message: 'load-balancer-api-external: tcp connection to a29d4c3db15794cefa8a5d3ad55db52a-bde0e8c2d305ce6f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T11:04:55Z"
    - latency: 15.584047ms
      message: 'load-balancer-api-external: resolved host name a29d4c3db15794cefa8a5d3ad55db52a-bde0e8c2d305ce6f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T11:04:55Z"
    - latency: 4.645166ms
      message: 'load-balancer-api-external: tcp connection to a29d4c3db15794cefa8a5d3ad55db52a-bde0e8c2d305ce6f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T11:03:55Z"
    - latency: 8.067463ms
      message: 'load-balancer-api-external: resolved host name a29d4c3db15794cefa8a5d3ad55db52a-bde0e8c2d305ce6f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T11:03:55Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T10:31:53Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-34-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-34.ec2.internal
      uid: 769ee7c0-a719-4396-a3a1-6e4a10381610
    resourceVersion: "56002"
    uid: cf5d55d1-e2d3-4499-9114-681b09d23165
  spec:
    sourcePod: network-check-source-989f8b8dc-2fvvk
    targetEndpoint: a29d4c3db15794cefa8a5d3ad55db52a-bde0e8c2d305ce6f.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T10:37:55Z"
      message: 'load-balancer-api-internal: tcp connection to a29d4c3db15794cefa8a5d3ad55db52a-bde0e8c2d305ce6f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.330497ms
      message: 'load-balancer-api-internal: tcp connection to a29d4c3db15794cefa8a5d3ad55db52a-bde0e8c2d305ce6f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T11:07:55Z"
    - latency: 10.721133ms
      message: 'load-balancer-api-internal: resolved host name a29d4c3db15794cefa8a5d3ad55db52a-bde0e8c2d305ce6f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T11:07:55Z"
    - latency: 5.095316ms
      message: 'load-balancer-api-internal: tcp connection to a29d4c3db15794cefa8a5d3ad55db52a-bde0e8c2d305ce6f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T11:06:55Z"
    - latency: 10.062193ms
      message: 'load-balancer-api-internal: resolved host name a29d4c3db15794cefa8a5d3ad55db52a-bde0e8c2d305ce6f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T11:06:55Z"
    - latency: 3.888707ms
      message: 'load-balancer-api-internal: tcp connection to a29d4c3db15794cefa8a5d3ad55db52a-bde0e8c2d305ce6f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T11:05:55Z"
    - latency: 6.918094ms
      message: 'load-balancer-api-internal: resolved host name a29d4c3db15794cefa8a5d3ad55db52a-bde0e8c2d305ce6f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T11:05:55Z"
    - latency: 6.283139ms
      message: 'load-balancer-api-internal: tcp connection to a29d4c3db15794cefa8a5d3ad55db52a-bde0e8c2d305ce6f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T11:04:55Z"
    - latency: 15.437431ms
      message: 'load-balancer-api-internal: resolved host name a29d4c3db15794cefa8a5d3ad55db52a-bde0e8c2d305ce6f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T11:04:55Z"
    - latency: 4.467113ms
      message: 'load-balancer-api-internal: tcp connection to a29d4c3db15794cefa8a5d3ad55db52a-bde0e8c2d305ce6f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T11:03:55Z"
    - latency: 8.11858ms
      message: 'load-balancer-api-internal: resolved host name a29d4c3db15794cefa8a5d3ad55db52a-bde0e8c2d305ce6f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T11:03:55Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T10:31:53Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-34-to-network-check-target-ip-10-0-135-34
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-34.ec2.internal
      uid: 769ee7c0-a719-4396-a3a1-6e4a10381610
    resourceVersion: "55001"
    uid: f6fd26be-a03c-4848-b477-3e96ad0e9424
  spec:
    sourcePod: network-check-source-989f8b8dc-2fvvk
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T10:38:55Z"
      message: 'network-check-target-ip-10-0-135-34: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 822.408µs
      message: 'network-check-target-ip-10-0-135-34: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T11:06:55Z"
    - latency: 979.794µs
      message: 'network-check-target-ip-10-0-135-34: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T11:05:55Z"
    - latency: 827.817µs
      message: 'network-check-target-ip-10-0-135-34: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T11:04:55Z"
    - latency: 1.1435ms
      message: 'network-check-target-ip-10-0-135-34: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T11:03:55Z"
    - latency: 954.141µs
      message: 'network-check-target-ip-10-0-135-34: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T11:02:55Z"
    - latency: 1.232772ms
      message: 'network-check-target-ip-10-0-135-34: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T11:01:55Z"
    - latency: 1.034478ms
      message: 'network-check-target-ip-10-0-135-34: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T11:00:55Z"
    - latency: 1.00946ms
      message: 'network-check-target-ip-10-0-135-34: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T10:59:55Z"
    - latency: 992.547µs
      message: 'network-check-target-ip-10-0-135-34: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T10:58:55Z"
    - latency: 1.254538ms
      message: 'network-check-target-ip-10-0-135-34: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T10:57:55Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T10:31:53Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-34-to-network-check-target-ip-10-0-135-59
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-34.ec2.internal
      uid: 769ee7c0-a719-4396-a3a1-6e4a10381610
    resourceVersion: "55002"
    uid: cf57745b-7cf0-4f13-a3a9-6066a06c086d
  spec:
    sourcePod: network-check-source-989f8b8dc-2fvvk
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T10:38:55Z"
      message: 'network-check-target-ip-10-0-135-59: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.790708ms
      message: 'network-check-target-ip-10-0-135-59: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T11:06:55Z"
    - latency: 2.013764ms
      message: 'network-check-target-ip-10-0-135-59: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T11:05:55Z"
    - latency: 2.774478ms
      message: 'network-check-target-ip-10-0-135-59: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T11:04:55Z"
    - latency: 1.823193ms
      message: 'network-check-target-ip-10-0-135-59: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T11:03:55Z"
    - latency: 1.774279ms
      message: 'network-check-target-ip-10-0-135-59: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T11:02:55Z"
    - latency: 1.581025ms
      message: 'network-check-target-ip-10-0-135-59: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T11:01:55Z"
    - latency: 1.710369ms
      message: 'network-check-target-ip-10-0-135-59: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T11:00:55Z"
    - latency: 1.902144ms
      message: 'network-check-target-ip-10-0-135-59: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T10:59:55Z"
    - latency: 1.836289ms
      message: 'network-check-target-ip-10-0-135-59: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T10:58:55Z"
    - latency: 2.011116ms
      message: 'network-check-target-ip-10-0-135-59: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T10:57:55Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T10:31:53Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-34-to-network-check-target-ip-10-0-139-204
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-34.ec2.internal
      uid: 769ee7c0-a719-4396-a3a1-6e4a10381610
    resourceVersion: "55003"
    uid: 04d3cb27-2d1d-4dbf-a8e6-fe3f04510c99
  spec:
    sourcePod: network-check-source-989f8b8dc-2fvvk
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T10:38:55Z"
      message: 'network-check-target-ip-10-0-139-204: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.247573ms
      message: 'network-check-target-ip-10-0-139-204: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T11:06:55Z"
    - latency: 2.28274ms
      message: 'network-check-target-ip-10-0-139-204: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T11:05:55Z"
    - latency: 2.874621ms
      message: 'network-check-target-ip-10-0-139-204: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T11:04:55Z"
    - latency: 2.022841ms
      message: 'network-check-target-ip-10-0-139-204: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T11:03:55Z"
    - latency: 1.941614ms
      message: 'network-check-target-ip-10-0-139-204: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T11:02:55Z"
    - latency: 1.846168ms
      message: 'network-check-target-ip-10-0-139-204: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T11:01:55Z"
    - latency: 2.250689ms
      message: 'network-check-target-ip-10-0-139-204: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T11:00:55Z"
    - latency: 2.221209ms
      message: 'network-check-target-ip-10-0-139-204: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T10:59:55Z"
    - latency: 2.125086ms
      message: 'network-check-target-ip-10-0-139-204: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T10:58:55Z"
    - latency: 2.394713ms
      message: 'network-check-target-ip-10-0-139-204: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T10:57:55Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T10:31:53Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-34-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-34.ec2.internal
      uid: 769ee7c0-a719-4396-a3a1-6e4a10381610
    resourceVersion: "56000"
    uid: 85949c11-2ebc-430d-bc1a-1a39f2cd4309
  spec:
    sourcePod: network-check-source-989f8b8dc-2fvvk
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T10:37:55Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 750.73µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T11:07:55Z"
    - latency: 1.671157ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T11:07:55Z"
    - latency: 891.854µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T11:06:55Z"
    - latency: 1.895191ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T11:06:55Z"
    - latency: 883.23µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T11:05:55Z"
    - latency: 1.75049ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T11:05:55Z"
    - latency: 737.786µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T11:04:55Z"
    - latency: 3.498023ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T11:04:55Z"
    - latency: 714.405µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T11:03:55Z"
    - latency: 1.875227ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T11:03:55Z"
kind: List
metadata:
  resourceVersion: ""