apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-04T11:37:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-11-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-11.ec2.internal
      uid: dc7a548d-4170-428c-ac37-9dc7cf4f2252
    resourceVersion: "77961"
    uid: 85c239f4-7034-4880-97d3-a5d801a3b99a
  spec:
    sourcePod: network-check-source-65bdbbff45-p7bpm
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-08-04T11:44:26Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.235187ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T12:33:26Z"
    - latency: 1.640954ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T12:32:26Z"
    - latency: 945.025µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T12:31:26Z"
    - latency: 880.128µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T12:30:26Z"
    - latency: 1.35762ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T12:29:26Z"
    - latency: 1.288764ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T12:28:26Z"
    - latency: 1.113206ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T12:27:26Z"
    - latency: 1.229177ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T12:26:26Z"
    - latency: 1.164165ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T12:25:26Z"
    - latency: 986.202µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T12:24:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-04T11:37:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-11-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-11.ec2.internal
      uid: dc7a548d-4170-428c-ac37-9dc7cf4f2252
    resourceVersion: "75930"
    uid: 22f84126-61a4-49c8-9cfa-bf6d1417a771
  spec:
    sourcePod: network-check-source-65bdbbff45-p7bpm
    targetEndpoint: a6c8782cab97d437ab49e6b1bbc05d5c-7454ed0f907a711a.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-08-04T11:43:26Z"
      message: 'load-balancer-api-external: tcp connection to a6c8782cab97d437ab49e6b1bbc05d5c-7454ed0f907a711a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.991158ms
      message: 'load-balancer-api-external: tcp connection to a6c8782cab97d437ab49e6b1bbc05d5c-7454ed0f907a711a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T12:31:26Z"
    - latency: 9.010276ms
      message: 'load-balancer-api-external: resolved host name a6c8782cab97d437ab49e6b1bbc05d5c-7454ed0f907a711a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-04T12:31:26Z"
    - latency: 3.868981ms
      message: 'load-balancer-api-external: tcp connection to a6c8782cab97d437ab49e6b1bbc05d5c-7454ed0f907a711a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T12:30:26Z"
    - latency: 12.832466ms
      message: 'load-balancer-api-external: resolved host name a6c8782cab97d437ab49e6b1bbc05d5c-7454ed0f907a711a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-04T12:30:26Z"
    - latency: 5.002878ms
      message: 'load-balancer-api-external: tcp connection to a6c8782cab97d437ab49e6b1bbc05d5c-7454ed0f907a711a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T12:29:26Z"
    - latency: 8.735583ms
      message: 'load-balancer-api-external: resolved host name a6c8782cab97d437ab49e6b1bbc05d5c-7454ed0f907a711a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-04T12:29:26Z"
    - latency: 3.192672ms
      message: 'load-balancer-api-external: tcp connection to a6c8782cab97d437ab49e6b1bbc05d5c-7454ed0f907a711a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T12:28:26Z"
    - latency: 8.788398ms
      message: 'load-balancer-api-external: resolved host name a6c8782cab97d437ab49e6b1bbc05d5c-7454ed0f907a711a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-04T12:28:26Z"
    - latency: 3.871862ms
      message: 'load-balancer-api-external: tcp connection to a6c8782cab97d437ab49e6b1bbc05d5c-7454ed0f907a711a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T12:27:26Z"
    - latency: 8.54782ms
      message: 'load-balancer-api-external: resolved host name a6c8782cab97d437ab49e6b1bbc05d5c-7454ed0f907a711a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-04T12:27:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-04T11:37:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-11-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-11.ec2.internal
      uid: dc7a548d-4170-428c-ac37-9dc7cf4f2252
    resourceVersion: "75931"
    uid: e47a9bcc-ee2b-42ea-96b1-a29a6c6f5f09
  spec:
    sourcePod: network-check-source-65bdbbff45-p7bpm
    targetEndpoint: a6c8782cab97d437ab49e6b1bbc05d5c-7454ed0f907a711a.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-08-04T11:43:26Z"
      message: 'load-balancer-api-internal: tcp connection to a6c8782cab97d437ab49e6b1bbc05d5c-7454ed0f907a711a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.238663ms
      message: 'load-balancer-api-internal: tcp connection to a6c8782cab97d437ab49e6b1bbc05d5c-7454ed0f907a711a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T12:31:26Z"
    - latency: 9.043651ms
      message: 'load-balancer-api-internal: resolved host name a6c8782cab97d437ab49e6b1bbc05d5c-7454ed0f907a711a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-04T12:31:26Z"
    - latency: 5.684145ms
      message: 'load-balancer-api-internal: tcp connection to a6c8782cab97d437ab49e6b1bbc05d5c-7454ed0f907a711a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T12:30:26Z"
    - latency: 12.762512ms
      message: 'load-balancer-api-internal: resolved host name a6c8782cab97d437ab49e6b1bbc05d5c-7454ed0f907a711a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-04T12:30:26Z"
    - latency: 5.048701ms
      message: 'load-balancer-api-internal: tcp connection to a6c8782cab97d437ab49e6b1bbc05d5c-7454ed0f907a711a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T12:29:26Z"
    - latency: 8.641396ms
      message: 'load-balancer-api-internal: resolved host name a6c8782cab97d437ab49e6b1bbc05d5c-7454ed0f907a711a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-04T12:29:26Z"
    - latency: 3.20632ms
      message: 'load-balancer-api-internal: tcp connection to a6c8782cab97d437ab49e6b1bbc05d5c-7454ed0f907a711a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T12:28:26Z"
    - latency: 8.749539ms
      message: 'load-balancer-api-internal: resolved host name a6c8782cab97d437ab49e6b1bbc05d5c-7454ed0f907a711a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-04T12:28:26Z"
    - latency: 3.930468ms
      message: 'load-balancer-api-internal: tcp connection to a6c8782cab97d437ab49e6b1bbc05d5c-7454ed0f907a711a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T12:27:26Z"
    - latency: 8.514249ms
      message: 'load-balancer-api-internal: resolved host name a6c8782cab97d437ab49e6b1bbc05d5c-7454ed0f907a711a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-04T12:27:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-04T11:37:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-11-to-network-check-target-ip-10-0-128-47
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-11.ec2.internal
      uid: dc7a548d-4170-428c-ac37-9dc7cf4f2252
    resourceVersion: "77960"
    uid: 0f471b4f-fc3f-4f47-8645-c9b6c30ab76d
  spec:
    sourcePod: network-check-source-65bdbbff45-p7bpm
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-08-04T11:44:26Z"
      message: 'network-check-target-ip-10-0-128-47: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.296294ms
      message: 'network-check-target-ip-10-0-128-47: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T12:33:26Z"
    - latency: 2.053599ms
      message: 'network-check-target-ip-10-0-128-47: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T12:32:26Z"
    - latency: 2.136319ms
      message: 'network-check-target-ip-10-0-128-47: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T12:31:26Z"
    - latency: 2.087686ms
      message: 'network-check-target-ip-10-0-128-47: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T12:30:26Z"
    - latency: 2.081283ms
      message: 'network-check-target-ip-10-0-128-47: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T12:29:26Z"
    - latency: 2.063139ms
      message: 'network-check-target-ip-10-0-128-47: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T12:28:26Z"
    - latency: 1.773963ms
      message: 'network-check-target-ip-10-0-128-47: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T12:27:26Z"
    - latency: 2.071144ms
      message: 'network-check-target-ip-10-0-128-47: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T12:26:26Z"
    - latency: 2.062678ms
      message: 'network-check-target-ip-10-0-128-47: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T12:25:26Z"
    - latency: 1.968114ms
      message: 'network-check-target-ip-10-0-128-47: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T12:24:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-04T11:37:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-11-to-network-check-target-ip-10-0-129-1
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-11.ec2.internal
      uid: dc7a548d-4170-428c-ac37-9dc7cf4f2252
    resourceVersion: "77959"
    uid: b1ec941d-4965-42d5-906b-08120f972258
  spec:
    sourcePod: network-check-source-65bdbbff45-p7bpm
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-08-04T11:44:26Z"
      message: 'network-check-target-ip-10-0-129-1: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.562375ms
      message: 'network-check-target-ip-10-0-129-1: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T12:33:26Z"
    - latency: 2.245836ms
      message: 'network-check-target-ip-10-0-129-1: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T12:32:26Z"
    - latency: 2.350177ms
      message: 'network-check-target-ip-10-0-129-1: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T12:31:26Z"
    - latency: 2.047152ms
      message: 'network-check-target-ip-10-0-129-1: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T12:30:26Z"
    - latency: 2.37064ms
      message: 'network-check-target-ip-10-0-129-1: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T12:29:26Z"
    - latency: 2.329255ms
      message: 'network-check-target-ip-10-0-129-1: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T12:28:26Z"
    - latency: 2.439194ms
      message: 'network-check-target-ip-10-0-129-1: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T12:27:26Z"
    - latency: 2.334706ms
      message: 'network-check-target-ip-10-0-129-1: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T12:26:26Z"
    - latency: 2.483378ms
      message: 'network-check-target-ip-10-0-129-1: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T12:25:26Z"
    - latency: 2.493316ms
      message: 'network-check-target-ip-10-0-129-1: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T12:24:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-04T11:37:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-11-to-network-check-target-ip-10-0-129-11
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-11.ec2.internal
      uid: dc7a548d-4170-428c-ac37-9dc7cf4f2252
    resourceVersion: "77958"
    uid: a909e4e2-43b8-4938-90e0-419afb148079
  spec:
    sourcePod: network-check-source-65bdbbff45-p7bpm
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-08-04T11:44:26Z"
      message: 'network-check-target-ip-10-0-129-11: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.438964ms
      message: 'network-check-target-ip-10-0-129-11: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T12:33:26Z"
    - latency: 1.470415ms
      message: 'network-check-target-ip-10-0-129-11: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T12:32:26Z"
    - latency: 1.105499ms
      message: 'network-check-target-ip-10-0-129-11: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T12:31:26Z"
    - latency: 876.999µs
      message: 'network-check-target-ip-10-0-129-11: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T12:30:26Z"
    - latency: 1.520433ms
      message: 'network-check-target-ip-10-0-129-11: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T12:29:26Z"
    - latency: 1.441748ms
      message: 'network-check-target-ip-10-0-129-11: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T12:28:26Z"
    - latency: 1.243971ms
      message: 'network-check-target-ip-10-0-129-11: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T12:27:26Z"
    - latency: 1.324709ms
      message: 'network-check-target-ip-10-0-129-11: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T12:26:26Z"
    - latency: 1.426867ms
      message: 'network-check-target-ip-10-0-129-11: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T12:25:26Z"
    - latency: 1.556462ms
      message: 'network-check-target-ip-10-0-129-11: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T12:24:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-04T11:37:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-11-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-11.ec2.internal
      uid: dc7a548d-4170-428c-ac37-9dc7cf4f2252
    resourceVersion: "75929"
    uid: 7c6f3c85-8629-4eb2-be01-46d7bf5c933c
  spec:
    sourcePod: network-check-source-65bdbbff45-p7bpm
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-08-04T11:43:26Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 887.899µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T12:31:26Z"
    - latency: 1.875126ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-04T12:31:26Z"
    - latency: 870.973µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T12:30:26Z"
    - latency: 1.81776ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-04T12:30:26Z"
    - latency: 875.429µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T12:29:26Z"
    - latency: 1.864574ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-04T12:29:26Z"
    - latency: 1.051351ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T12:28:26Z"
    - latency: 1.985709ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-04T12:28:26Z"
    - latency: 1.341044ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T12:27:26Z"
    - latency: 1.892536ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-04T12:27:26Z"
kind: List
metadata:
  resourceVersion: ""