apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-26T15:22:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-63-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-63.ec2.internal
      uid: 28c17bfe-82f2-45bd-8f6c-5507febd7960
    resourceVersion: "88704"
    uid: 31120368-354d-49ae-881c-b50db411acf4
  spec:
    sourcePod: network-check-source-7d88cb55d8-cbzrx
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-26T15:29:40Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.625865ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T16:11:40Z"
    - latency: 1.397099ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T16:10:40Z"
    - latency: 1.206845ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T16:09:40Z"
    - latency: 930.468µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T16:08:40Z"
    - latency: 967.475µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T16:07:40Z"
    - latency: 873.748µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T16:06:40Z"
    - latency: 973.398µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T16:05:40Z"
    - latency: 1.15546ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T16:04:40Z"
    - latency: 836.109µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T16:03:40Z"
    - latency: 962.394µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T16:02:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-26T15:22:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-63-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-63.ec2.internal
      uid: 28c17bfe-82f2-45bd-8f6c-5507febd7960
    resourceVersion: "86450"
    uid: 13f3bc9a-77c4-4d8a-8529-0537c7bb51ee
  spec:
    sourcePod: network-check-source-7d88cb55d8-cbzrx
    targetEndpoint: a6431883b1d0840aa879ae820a266f7a-e7256189f75e0564.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-26T15:28:40Z"
      message: 'load-balancer-api-external: tcp connection to a6431883b1d0840aa879ae820a266f7a-e7256189f75e0564.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.318235ms
      message: 'load-balancer-api-external: tcp connection to a6431883b1d0840aa879ae820a266f7a-e7256189f75e0564.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T16:10:40Z"
    - latency: 7.202144ms
      message: 'load-balancer-api-external: resolved host name a6431883b1d0840aa879ae820a266f7a-e7256189f75e0564.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-26T16:10:40Z"
    - latency: 4.757258ms
      message: 'load-balancer-api-external: tcp connection to a6431883b1d0840aa879ae820a266f7a-e7256189f75e0564.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T16:09:40Z"
    - latency: 6.371431ms
      message: 'load-balancer-api-external: resolved host name a6431883b1d0840aa879ae820a266f7a-e7256189f75e0564.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-26T16:09:40Z"
    - latency: 4.835216ms
      message: 'load-balancer-api-external: tcp connection to a6431883b1d0840aa879ae820a266f7a-e7256189f75e0564.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T16:08:40Z"
    - latency: 7.019034ms
      message: 'load-balancer-api-external: resolved host name a6431883b1d0840aa879ae820a266f7a-e7256189f75e0564.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-26T16:08:40Z"
    - latency: 5.235049ms
      message: 'load-balancer-api-external: tcp connection to a6431883b1d0840aa879ae820a266f7a-e7256189f75e0564.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T16:07:40Z"
    - latency: 6.927187ms
      message: 'load-balancer-api-external: resolved host name a6431883b1d0840aa879ae820a266f7a-e7256189f75e0564.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-26T16:07:40Z"
    - latency: 4.919344ms
      message: 'load-balancer-api-external: tcp connection to a6431883b1d0840aa879ae820a266f7a-e7256189f75e0564.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T16:06:40Z"
    - latency: 7.976209ms
      message: 'load-balancer-api-external: resolved host name a6431883b1d0840aa879ae820a266f7a-e7256189f75e0564.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-26T16:06:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-26T15:22:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-63-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-63.ec2.internal
      uid: 28c17bfe-82f2-45bd-8f6c-5507febd7960
    resourceVersion: "86451"
    uid: 52c66662-94b3-41d3-9a17-8507ee753912
  spec:
    sourcePod: network-check-source-7d88cb55d8-cbzrx
    targetEndpoint: a6431883b1d0840aa879ae820a266f7a-e7256189f75e0564.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-26T15:28:40Z"
      message: 'load-balancer-api-internal: tcp connection to a6431883b1d0840aa879ae820a266f7a-e7256189f75e0564.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.042137ms
      message: 'load-balancer-api-internal: tcp connection to a6431883b1d0840aa879ae820a266f7a-e7256189f75e0564.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T16:10:40Z"
    - latency: 7.124572ms
      message: 'load-balancer-api-internal: resolved host name a6431883b1d0840aa879ae820a266f7a-e7256189f75e0564.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-26T16:10:40Z"
    - latency: 5.411539ms
      message: 'load-balancer-api-internal: tcp connection to a6431883b1d0840aa879ae820a266f7a-e7256189f75e0564.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T16:09:40Z"
    - latency: 6.334075ms
      message: 'load-balancer-api-internal: resolved host name a6431883b1d0840aa879ae820a266f7a-e7256189f75e0564.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-26T16:09:40Z"
    - latency: 4.824259ms
      message: 'load-balancer-api-internal: tcp connection to a6431883b1d0840aa879ae820a266f7a-e7256189f75e0564.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T16:08:40Z"
    - latency: 6.946395ms
      message: 'load-balancer-api-internal: resolved host name a6431883b1d0840aa879ae820a266f7a-e7256189f75e0564.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-26T16:08:40Z"
    - latency: 4.755894ms
      message: 'load-balancer-api-internal: tcp connection to a6431883b1d0840aa879ae820a266f7a-e7256189f75e0564.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T16:07:40Z"
    - latency: 6.856602ms
      message: 'load-balancer-api-internal: resolved host name a6431883b1d0840aa879ae820a266f7a-e7256189f75e0564.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-26T16:07:40Z"
    - latency: 4.915861ms
      message: 'load-balancer-api-internal: tcp connection to a6431883b1d0840aa879ae820a266f7a-e7256189f75e0564.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T16:06:40Z"
    - latency: 7.890017ms
      message: 'load-balancer-api-internal: resolved host name a6431883b1d0840aa879ae820a266f7a-e7256189f75e0564.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-26T16:06:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-26T15:22:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-63-to-network-check-target-ip-10-0-137-96
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-63.ec2.internal
      uid: 28c17bfe-82f2-45bd-8f6c-5507febd7960
    resourceVersion: "88703"
    uid: 9827b285-9854-4cf3-b5e4-fadbb6c0690b
  spec:
    sourcePod: network-check-source-7d88cb55d8-cbzrx
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-26T15:29:40Z"
      message: 'network-check-target-ip-10-0-137-96: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.177467ms
      message: 'network-check-target-ip-10-0-137-96: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T16:11:40Z"
    - latency: 2.089684ms
      message: 'network-check-target-ip-10-0-137-96: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T16:10:40Z"
    - latency: 2.308558ms
      message: 'network-check-target-ip-10-0-137-96: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T16:09:40Z"
    - latency: 2.216364ms
      message: 'network-check-target-ip-10-0-137-96: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T16:08:40Z"
    - latency: 2.437854ms
      message: 'network-check-target-ip-10-0-137-96: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T16:07:40Z"
    - latency: 2.12844ms
      message: 'network-check-target-ip-10-0-137-96: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T16:06:40Z"
    - latency: 2.174084ms
      message: 'network-check-target-ip-10-0-137-96: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T16:05:40Z"
    - latency: 2.297501ms
      message: 'network-check-target-ip-10-0-137-96: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T16:04:40Z"
    - latency: 2.198912ms
      message: 'network-check-target-ip-10-0-137-96: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T16:03:40Z"
    - latency: 2.139626ms
      message: 'network-check-target-ip-10-0-137-96: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T16:02:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-26T15:22:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-63-to-network-check-target-ip-10-0-138-63
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-63.ec2.internal
      uid: 28c17bfe-82f2-45bd-8f6c-5507febd7960
    resourceVersion: "88701"
    uid: de24851f-d08a-4888-8ead-3a8ec2b9bc95
  spec:
    sourcePod: network-check-source-7d88cb55d8-cbzrx
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-26T15:29:40Z"
      message: 'network-check-target-ip-10-0-138-63: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 720.134µs
      message: 'network-check-target-ip-10-0-138-63: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T16:11:40Z"
    - latency: 811.009µs
      message: 'network-check-target-ip-10-0-138-63: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T16:10:40Z"
    - latency: 905.053µs
      message: 'network-check-target-ip-10-0-138-63: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T16:09:40Z"
    - latency: 810.16µs
      message: 'network-check-target-ip-10-0-138-63: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T16:08:40Z"
    - latency: 1.043211ms
      message: 'network-check-target-ip-10-0-138-63: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T16:07:40Z"
    - latency: 1.468326ms
      message: 'network-check-target-ip-10-0-138-63: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T16:06:40Z"
    - latency: 793.965µs
      message: 'network-check-target-ip-10-0-138-63: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T16:05:40Z"
    - latency: 912.485µs
      message: 'network-check-target-ip-10-0-138-63: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T16:04:40Z"
    - latency: 927.435µs
      message: 'network-check-target-ip-10-0-138-63: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T16:03:40Z"
    - latency: 771.639µs
      message: 'network-check-target-ip-10-0-138-63: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T16:02:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-26T15:22:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-63-to-network-check-target-ip-10-0-139-110
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-63.ec2.internal
      uid: 28c17bfe-82f2-45bd-8f6c-5507febd7960
    resourceVersion: "88702"
    uid: 625340f3-9b56-4360-bd0a-449ab39555b9
  spec:
    sourcePod: network-check-source-7d88cb55d8-cbzrx
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-26T15:29:40Z"
      message: 'network-check-target-ip-10-0-139-110: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.942752ms
      message: 'network-check-target-ip-10-0-139-110: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T16:11:40Z"
    - latency: 1.737743ms
      message: 'network-check-target-ip-10-0-139-110: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T16:10:40Z"
    - latency: 1.852021ms
      message: 'network-check-target-ip-10-0-139-110: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T16:09:40Z"
    - latency: 1.887233ms
      message: 'network-check-target-ip-10-0-139-110: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T16:08:40Z"
    - latency: 2.09735ms
      message: 'network-check-target-ip-10-0-139-110: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T16:07:40Z"
    - latency: 1.680251ms
      message: 'network-check-target-ip-10-0-139-110: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T16:06:40Z"
    - latency: 2.105468ms
      message: 'network-check-target-ip-10-0-139-110: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T16:05:40Z"
    - latency: 2.308753ms
      message: 'network-check-target-ip-10-0-139-110: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T16:04:40Z"
    - latency: 1.89226ms
      message: 'network-check-target-ip-10-0-139-110: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T16:03:40Z"
    - latency: 2.01544ms
      message: 'network-check-target-ip-10-0-139-110: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T16:02:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-26T15:22:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-63-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-63.ec2.internal
      uid: 28c17bfe-82f2-45bd-8f6c-5507febd7960
    resourceVersion: "86449"
    uid: 23c8b62a-ccd3-448c-b263-77dbe62682cd
  spec:
    sourcePod: network-check-source-7d88cb55d8-cbzrx
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-26T15:28:40Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.071072ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T16:10:40Z"
    - latency: 1.792573ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-26T16:10:40Z"
    - latency: 834.431µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T16:09:40Z"
    - latency: 1.764272ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-26T16:09:40Z"
    - latency: 1.072855ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T16:08:40Z"
    - latency: 1.787854ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-26T16:08:40Z"
    - latency: 1.463129ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T16:07:40Z"
    - latency: 2.12071ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-26T16:07:40Z"
    - latency: 887.629µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T16:06:40Z"
    - latency: 1.577947ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-26T16:06:40Z"
kind: List
metadata:
  resourceVersion: ""