apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-30T19:42:07Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-254-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-254.ec2.internal
      uid: f06ca528-8e8b-499a-be1b-5a7a8e095a71
    resourceVersion: "76779"
    uid: a402e4e5-8a33-48c8-ac9c-bfe578d68307
  spec:
    sourcePod: network-check-source-65bdbbff45-c65pq
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-30T19:49:09Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.194071ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T20:38:09Z"
    - latency: 1.022355ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T20:37:09Z"
    - latency: 1.145374ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T20:36:09Z"
    - latency: 1.349114ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T20:35:09Z"
    - latency: 1.060308ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T20:34:09Z"
    - latency: 1.119499ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T20:33:09Z"
    - latency: 1.071255ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T20:32:09Z"
    - latency: 1.90501ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T20:31:09Z"
    - latency: 1.120786ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T20:30:09Z"
    - latency: 1.109263ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T20:29:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-30T19:42:07Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-254-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-254.ec2.internal
      uid: f06ca528-8e8b-499a-be1b-5a7a8e095a71
    resourceVersion: "74786"
    uid: 9554cb53-c7ea-4b17-b4bc-91265f2c7971
  spec:
    sourcePod: network-check-source-65bdbbff45-c65pq
    targetEndpoint: ae539cda2c678442880c280c0d388d39-1dcec5d578e51986.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-30T19:48:09Z"
      message: 'load-balancer-api-external: tcp connection to ae539cda2c678442880c280c0d388d39-1dcec5d578e51986.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.347909ms
      message: 'load-balancer-api-external: tcp connection to ae539cda2c678442880c280c0d388d39-1dcec5d578e51986.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T20:36:09Z"
    - latency: 7.665916ms
      message: 'load-balancer-api-external: resolved host name ae539cda2c678442880c280c0d388d39-1dcec5d578e51986.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T20:36:09Z"
    - latency: 5.467542ms
      message: 'load-balancer-api-external: tcp connection to ae539cda2c678442880c280c0d388d39-1dcec5d578e51986.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T20:35:09Z"
    - latency: 8.77028ms
      message: 'load-balancer-api-external: resolved host name ae539cda2c678442880c280c0d388d39-1dcec5d578e51986.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T20:35:09Z"
    - latency: 4.834685ms
      message: 'load-balancer-api-external: tcp connection to ae539cda2c678442880c280c0d388d39-1dcec5d578e51986.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T20:34:09Z"
    - latency: 7.343554ms
      message: 'load-balancer-api-external: resolved host name ae539cda2c678442880c280c0d388d39-1dcec5d578e51986.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T20:34:09Z"
    - latency: 5.092012ms
      message: 'load-balancer-api-external: tcp connection to ae539cda2c678442880c280c0d388d39-1dcec5d578e51986.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T20:33:09Z"
    - latency: 8.03182ms
      message: 'load-balancer-api-external: resolved host name ae539cda2c678442880c280c0d388d39-1dcec5d578e51986.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T20:33:09Z"
    - latency: 5.050382ms
      message: 'load-balancer-api-external: tcp connection to ae539cda2c678442880c280c0d388d39-1dcec5d578e51986.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T20:32:09Z"
    - latency: 9.194197ms
      message: 'load-balancer-api-external: resolved host name ae539cda2c678442880c280c0d388d39-1dcec5d578e51986.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T20:32:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-30T19:42:07Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-254-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-254.ec2.internal
      uid: f06ca528-8e8b-499a-be1b-5a7a8e095a71
    resourceVersion: "74787"
    uid: 13100659-3041-445a-99fb-8abcc4db0746
  spec:
    sourcePod: network-check-source-65bdbbff45-c65pq
    targetEndpoint: ae539cda2c678442880c280c0d388d39-1dcec5d578e51986.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-30T19:48:09Z"
      message: 'load-balancer-api-internal: tcp connection to ae539cda2c678442880c280c0d388d39-1dcec5d578e51986.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.296879ms
      message: 'load-balancer-api-internal: tcp connection to ae539cda2c678442880c280c0d388d39-1dcec5d578e51986.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T20:36:09Z"
    - latency: 7.820027ms
      message: 'load-balancer-api-internal: resolved host name ae539cda2c678442880c280c0d388d39-1dcec5d578e51986.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T20:36:09Z"
    - latency: 5.229631ms
      message: 'load-balancer-api-internal: tcp connection to ae539cda2c678442880c280c0d388d39-1dcec5d578e51986.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T20:35:09Z"
    - latency: 8.830869ms
      message: 'load-balancer-api-internal: resolved host name ae539cda2c678442880c280c0d388d39-1dcec5d578e51986.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T20:35:09Z"
    - latency: 4.741057ms
      message: 'load-balancer-api-internal: tcp connection to ae539cda2c678442880c280c0d388d39-1dcec5d578e51986.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T20:34:09Z"
    - latency: 7.403264ms
      message: 'load-balancer-api-internal: resolved host name ae539cda2c678442880c280c0d388d39-1dcec5d578e51986.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T20:34:09Z"
    - latency: 5.062858ms
      message: 'load-balancer-api-internal: tcp connection to ae539cda2c678442880c280c0d388d39-1dcec5d578e51986.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T20:33:09Z"
    - latency: 8.121016ms
      message: 'load-balancer-api-internal: resolved host name ae539cda2c678442880c280c0d388d39-1dcec5d578e51986.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T20:33:09Z"
    - latency: 5.718822ms
      message: 'load-balancer-api-internal: tcp connection to ae539cda2c678442880c280c0d388d39-1dcec5d578e51986.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T20:32:09Z"
    - latency: 9.245826ms
      message: 'load-balancer-api-internal: resolved host name ae539cda2c678442880c280c0d388d39-1dcec5d578e51986.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T20:32:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-30T19:42:07Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-254-to-network-check-target-ip-10-0-134-200
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-254.ec2.internal
      uid: f06ca528-8e8b-499a-be1b-5a7a8e095a71
    resourceVersion: "76778"
    uid: ad9a8fba-58c9-4c6f-b6ac-9adcf62109b2
  spec:
    sourcePod: network-check-source-65bdbbff45-c65pq
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-30T19:49:09Z"
      message: 'network-check-target-ip-10-0-134-200: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.506222ms
      message: 'network-check-target-ip-10-0-134-200: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T20:38:09Z"
    - latency: 2.659554ms
      message: 'network-check-target-ip-10-0-134-200: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T20:37:09Z"
    - latency: 2.55255ms
      message: 'network-check-target-ip-10-0-134-200: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T20:36:09Z"
    - latency: 2.504157ms
      message: 'network-check-target-ip-10-0-134-200: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T20:35:09Z"
    - latency: 2.202296ms
      message: 'network-check-target-ip-10-0-134-200: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T20:34:09Z"
    - latency: 2.491709ms
      message: 'network-check-target-ip-10-0-134-200: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T20:33:09Z"
    - latency: 2.51587ms
      message: 'network-check-target-ip-10-0-134-200: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T20:32:09Z"
    - latency: 2.379066ms
      message: 'network-check-target-ip-10-0-134-200: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T20:31:09Z"
    - latency: 2.456641ms
      message: 'network-check-target-ip-10-0-134-200: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T20:30:09Z"
    - latency: 2.237229ms
      message: 'network-check-target-ip-10-0-134-200: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T20:29:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-30T19:42:07Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-254-to-network-check-target-ip-10-0-135-254
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-254.ec2.internal
      uid: f06ca528-8e8b-499a-be1b-5a7a8e095a71
    resourceVersion: "76776"
    uid: fd73c1be-c20d-4868-bf5a-3c9adbe17b84
  spec:
    sourcePod: network-check-source-65bdbbff45-c65pq
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-30T19:49:09Z"
      message: 'network-check-target-ip-10-0-135-254: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.534593ms
      message: 'network-check-target-ip-10-0-135-254: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T20:38:09Z"
    - latency: 980.641µs
      message: 'network-check-target-ip-10-0-135-254: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T20:37:09Z"
    - latency: 1.225385ms
      message: 'network-check-target-ip-10-0-135-254: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T20:36:09Z"
    - latency: 1.343064ms
      message: 'network-check-target-ip-10-0-135-254: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T20:35:09Z"
    - latency: 1.049124ms
      message: 'network-check-target-ip-10-0-135-254: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T20:34:09Z"
    - latency: 1.360238ms
      message: 'network-check-target-ip-10-0-135-254: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T20:33:09Z"
    - latency: 981.317µs
      message: 'network-check-target-ip-10-0-135-254: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T20:32:09Z"
    - latency: 986.596µs
      message: 'network-check-target-ip-10-0-135-254: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T20:31:09Z"
    - latency: 1.454353ms
      message: 'network-check-target-ip-10-0-135-254: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T20:30:09Z"
    - latency: 1.014178ms
      message: 'network-check-target-ip-10-0-135-254: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T20:29:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-30T19:42:07Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-254-to-network-check-target-ip-10-0-136-46
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-254.ec2.internal
      uid: f06ca528-8e8b-499a-be1b-5a7a8e095a71
    resourceVersion: "76777"
    uid: 7fc784c5-8879-4a40-aca3-e4166085e46e
  spec:
    sourcePod: network-check-source-65bdbbff45-c65pq
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-30T19:49:09Z"
      message: 'network-check-target-ip-10-0-136-46: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.452281ms
      message: 'network-check-target-ip-10-0-136-46: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T20:38:09Z"
    - latency: 2.280267ms
      message: 'network-check-target-ip-10-0-136-46: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T20:37:09Z"
    - latency: 2.12306ms
      message: 'network-check-target-ip-10-0-136-46: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T20:36:09Z"
    - latency: 2.619854ms
      message: 'network-check-target-ip-10-0-136-46: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T20:35:09Z"
    - latency: 2.230249ms
      message: 'network-check-target-ip-10-0-136-46: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T20:34:09Z"
    - latency: 2.467565ms
      message: 'network-check-target-ip-10-0-136-46: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T20:33:09Z"
    - latency: 2.443385ms
      message: 'network-check-target-ip-10-0-136-46: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T20:32:09Z"
    - latency: 2.589587ms
      message: 'network-check-target-ip-10-0-136-46: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T20:31:09Z"
    - latency: 2.368953ms
      message: 'network-check-target-ip-10-0-136-46: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T20:30:09Z"
    - latency: 3.071393ms
      message: 'network-check-target-ip-10-0-136-46: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T20:29:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-30T19:42:07Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-254-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-254.ec2.internal
      uid: f06ca528-8e8b-499a-be1b-5a7a8e095a71
    resourceVersion: "74785"
    uid: b0e8760d-b8d4-4c32-8103-a4230ae18ed7
  spec:
    sourcePod: network-check-source-65bdbbff45-c65pq
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-30T19:48:09Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.250989ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T20:36:09Z"
    - latency: 1.894094ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T20:36:09Z"
    - latency: 1.273665ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T20:35:09Z"
    - latency: 2.02587ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T20:35:09Z"
    - latency: 963.238µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T20:34:09Z"
    - latency: 1.883767ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T20:34:09Z"
    - latency: 1.005666ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T20:33:09Z"
    - latency: 1.907611ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T20:33:09Z"
    - latency: 1.180077ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T20:32:09Z"
    - latency: 2.596049ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T20:32:09Z"
kind: List
metadata:
  resourceVersion: ""