apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-19T11:37:13Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-209-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-209.ec2.internal
      uid: aebe7c7c-521b-4e75-a48f-7fa98ce7aa46
    resourceVersion: "71131"
    uid: b9943f7a-ef37-4a1a-b0b7-d098d8c99c19
  spec:
    sourcePod: network-check-source-7cbc45fddc-hlvdj
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-19T11:44:15Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.027413ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T12:12:15Z"
    - latency: 1.302781ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T12:11:15Z"
    - latency: 1.142037ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T12:10:15Z"
    - latency: 1.030885ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T12:09:15Z"
    - latency: 1.028713ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T12:08:15Z"
    - latency: 1.281753ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T12:07:15Z"
    - latency: 1.317371ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T12:06:15Z"
    - latency: 1.122242ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T12:05:15Z"
    - latency: 1.20744ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T12:04:15Z"
    - latency: 1.021046ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T12:03:15Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-19T11:37:13Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-209-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-209.ec2.internal
      uid: aebe7c7c-521b-4e75-a48f-7fa98ce7aa46
    resourceVersion: "66165"
    uid: 168ab95a-b7e6-4cff-b235-027c50cc4868
  spec:
    sourcePod: network-check-source-7cbc45fddc-hlvdj
    targetEndpoint: ab4a055a7177e4c5fbec6f77b12a63ff-a496afafa63b7825.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-19T11:43:15Z"
      message: 'load-balancer-api-external: tcp connection to ab4a055a7177e4c5fbec6f77b12a63ff-a496afafa63b7825.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.433892ms
      message: 'load-balancer-api-external: tcp connection to ab4a055a7177e4c5fbec6f77b12a63ff-a496afafa63b7825.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T12:07:15Z"
    - latency: 8.856903ms
      message: 'load-balancer-api-external: resolved host name ab4a055a7177e4c5fbec6f77b12a63ff-a496afafa63b7825.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T12:07:15Z"
    - latency: 4.94102ms
      message: 'load-balancer-api-external: tcp connection to ab4a055a7177e4c5fbec6f77b12a63ff-a496afafa63b7825.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T12:06:15Z"
    - latency: 8.889226ms
      message: 'load-balancer-api-external: resolved host name ab4a055a7177e4c5fbec6f77b12a63ff-a496afafa63b7825.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T12:06:15Z"
    - latency: 4.85351ms
      message: 'load-balancer-api-external: tcp connection to ab4a055a7177e4c5fbec6f77b12a63ff-a496afafa63b7825.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T12:05:15Z"
    - latency: 9.060876ms
      message: 'load-balancer-api-external: resolved host name ab4a055a7177e4c5fbec6f77b12a63ff-a496afafa63b7825.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T12:05:15Z"
    - latency: 4.959269ms
      message: 'load-balancer-api-external: tcp connection to ab4a055a7177e4c5fbec6f77b12a63ff-a496afafa63b7825.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T12:04:15Z"
    - latency: 7.137462ms
      message: 'load-balancer-api-external: resolved host name ab4a055a7177e4c5fbec6f77b12a63ff-a496afafa63b7825.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T12:04:15Z"
    - latency: 3.436365ms
      message: 'load-balancer-api-external: tcp connection to ab4a055a7177e4c5fbec6f77b12a63ff-a496afafa63b7825.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T12:03:15Z"
    - latency: 6.928278ms
      message: 'load-balancer-api-external: resolved host name ab4a055a7177e4c5fbec6f77b12a63ff-a496afafa63b7825.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T12:03:15Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-19T11:37:13Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-209-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-209.ec2.internal
      uid: aebe7c7c-521b-4e75-a48f-7fa98ce7aa46
    resourceVersion: "66166"
    uid: b8602537-83ff-42fa-9d59-ac3504c6a689
  spec:
    sourcePod: network-check-source-7cbc45fddc-hlvdj
    targetEndpoint: ab4a055a7177e4c5fbec6f77b12a63ff-a496afafa63b7825.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-19T11:43:15Z"
      message: 'load-balancer-api-internal: tcp connection to ab4a055a7177e4c5fbec6f77b12a63ff-a496afafa63b7825.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.465453ms
      message: 'load-balancer-api-internal: tcp connection to ab4a055a7177e4c5fbec6f77b12a63ff-a496afafa63b7825.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T12:07:15Z"
    - latency: 8.771016ms
      message: 'load-balancer-api-internal: resolved host name ab4a055a7177e4c5fbec6f77b12a63ff-a496afafa63b7825.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T12:07:15Z"
    - latency: 4.93912ms
      message: 'load-balancer-api-internal: tcp connection to ab4a055a7177e4c5fbec6f77b12a63ff-a496afafa63b7825.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T12:06:15Z"
    - latency: 8.853535ms
      message: 'load-balancer-api-internal: resolved host name ab4a055a7177e4c5fbec6f77b12a63ff-a496afafa63b7825.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T12:06:15Z"
    - latency: 4.827139ms
      message: 'load-balancer-api-internal: tcp connection to ab4a055a7177e4c5fbec6f77b12a63ff-a496afafa63b7825.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T12:05:15Z"
    - latency: 8.993995ms
      message: 'load-balancer-api-internal: resolved host name ab4a055a7177e4c5fbec6f77b12a63ff-a496afafa63b7825.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T12:05:15Z"
    - latency: 4.937302ms
      message: 'load-balancer-api-internal: tcp connection to ab4a055a7177e4c5fbec6f77b12a63ff-a496afafa63b7825.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T12:04:15Z"
    - latency: 7.051517ms
      message: 'load-balancer-api-internal: resolved host name ab4a055a7177e4c5fbec6f77b12a63ff-a496afafa63b7825.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T12:04:15Z"
    - latency: 3.340706ms
      message: 'load-balancer-api-internal: tcp connection to ab4a055a7177e4c5fbec6f77b12a63ff-a496afafa63b7825.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T12:03:15Z"
    - latency: 7.027761ms
      message: 'load-balancer-api-internal: resolved host name ab4a055a7177e4c5fbec6f77b12a63ff-a496afafa63b7825.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T12:03:15Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-19T11:37:13Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-209-to-network-check-target-ip-10-0-133-160
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-209.ec2.internal
      uid: aebe7c7c-521b-4e75-a48f-7fa98ce7aa46
    resourceVersion: "71130"
    uid: ce152835-edf7-40a3-988e-561c193e227e
  spec:
    sourcePod: network-check-source-7cbc45fddc-hlvdj
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-19T11:44:15Z"
      message: 'network-check-target-ip-10-0-133-160: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.18179ms
      message: 'network-check-target-ip-10-0-133-160: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T12:12:15Z"
    - latency: 2.060879ms
      message: 'network-check-target-ip-10-0-133-160: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T12:11:15Z"
    - latency: 2.242221ms
      message: 'network-check-target-ip-10-0-133-160: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T12:10:15Z"
    - latency: 2.416704ms
      message: 'network-check-target-ip-10-0-133-160: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T12:09:15Z"
    - latency: 2.067661ms
      message: 'network-check-target-ip-10-0-133-160: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T12:08:15Z"
    - latency: 2.09609ms
      message: 'network-check-target-ip-10-0-133-160: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T12:07:15Z"
    - latency: 1.985748ms
      message: 'network-check-target-ip-10-0-133-160: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T12:06:15Z"
    - latency: 2.314158ms
      message: 'network-check-target-ip-10-0-133-160: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T12:05:15Z"
    - latency: 2.050587ms
      message: 'network-check-target-ip-10-0-133-160: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T12:04:15Z"
    - latency: 2.183199ms
      message: 'network-check-target-ip-10-0-133-160: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T12:03:15Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-19T11:37:13Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-209-to-network-check-target-ip-10-0-133-209
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-209.ec2.internal
      uid: aebe7c7c-521b-4e75-a48f-7fa98ce7aa46
    resourceVersion: "71128"
    uid: df18b960-3401-4a24-83b0-68f7cb239bbb
  spec:
    sourcePod: network-check-source-7cbc45fddc-hlvdj
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-19T11:44:15Z"
      message: 'network-check-target-ip-10-0-133-209: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 952.213µs
      message: 'network-check-target-ip-10-0-133-209: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T12:12:15Z"
    - latency: 943.78µs
      message: 'network-check-target-ip-10-0-133-209: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T12:11:15Z"
    - latency: 1.599074ms
      message: 'network-check-target-ip-10-0-133-209: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T12:10:15Z"
    - latency: 835.329µs
      message: 'network-check-target-ip-10-0-133-209: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T12:09:15Z"
    - latency: 1.033052ms
      message: 'network-check-target-ip-10-0-133-209: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T12:08:15Z"
    - latency: 901.306µs
      message: 'network-check-target-ip-10-0-133-209: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T12:07:15Z"
    - latency: 1.307108ms
      message: 'network-check-target-ip-10-0-133-209: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T12:06:15Z"
    - latency: 882.749µs
      message: 'network-check-target-ip-10-0-133-209: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T12:05:15Z"
    - latency: 961.664µs
      message: 'network-check-target-ip-10-0-133-209: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T12:04:15Z"
    - latency: 1.166125ms
      message: 'network-check-target-ip-10-0-133-209: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T12:03:15Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-19T11:37:13Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-209-to-network-check-target-ip-10-0-140-136
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-209.ec2.internal
      uid: aebe7c7c-521b-4e75-a48f-7fa98ce7aa46
    resourceVersion: "71129"
    uid: 23dd3577-685a-41ea-96ef-cac78f015f15
  spec:
    sourcePod: network-check-source-7cbc45fddc-hlvdj
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-19T11:44:15Z"
      message: 'network-check-target-ip-10-0-140-136: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.159837ms
      message: 'network-check-target-ip-10-0-140-136: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T12:12:15Z"
    - latency: 2.240379ms
      message: 'network-check-target-ip-10-0-140-136: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T12:11:15Z"
    - latency: 2.397851ms
      message: 'network-check-target-ip-10-0-140-136: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T12:10:15Z"
    - latency: 2.293745ms
      message: 'network-check-target-ip-10-0-140-136: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T12:09:15Z"
    - latency: 1.999615ms
      message: 'network-check-target-ip-10-0-140-136: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T12:08:15Z"
    - latency: 2.3621ms
      message: 'network-check-target-ip-10-0-140-136: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T12:07:15Z"
    - latency: 2.091637ms
      message: 'network-check-target-ip-10-0-140-136: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T12:06:15Z"
    - latency: 1.997165ms
      message: 'network-check-target-ip-10-0-140-136: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T12:05:15Z"
    - latency: 2.449054ms
      message: 'network-check-target-ip-10-0-140-136: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T12:04:15Z"
    - latency: 2.21265ms
      message: 'network-check-target-ip-10-0-140-136: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T12:03:15Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-19T11:37:13Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-209-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-209.ec2.internal
      uid: aebe7c7c-521b-4e75-a48f-7fa98ce7aa46
    resourceVersion: "66164"
    uid: 9c088fbd-4b1d-4be1-a8b9-872ba0bbc666
  spec:
    sourcePod: network-check-source-7cbc45fddc-hlvdj
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-19T11:43:15Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.048155ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T12:07:15Z"
    - latency: 2.172118ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T12:07:15Z"
    - latency: 1.017191ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T12:06:15Z"
    - latency: 1.906336ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T12:06:15Z"
    - latency: 813.374µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T12:05:15Z"
    - latency: 1.868219ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T12:05:15Z"
    - latency: 908.222µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T12:04:15Z"
    - latency: 1.821201ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T12:04:15Z"
    - latency: 1.312064ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T12:03:15Z"
    - latency: 1.887467ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T12:03:15Z"
kind: List
metadata:
  resourceVersion: ""