apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-01T05:47:14Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-254-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-254.ec2.internal
      uid: e5ea164c-f7ea-459f-8f9c-0e74e82584a4
    resourceVersion: "17452"
    uid: e0684165-fa13-433b-a8db-903b8e5554ed
  spec:
    sourcePod: network-check-source-65bdbbff45-lkvpm
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-08-01T05:54: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.413901ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T06:01:15Z"
    - latency: 1.170289ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T06:00:15Z"
    - latency: 1.143143ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T05:59:15Z"
    - latency: 948.987µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T05:58:15Z"
    - latency: 1.114439ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T05:57:15Z"
    - latency: 1.000809ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T05:56:15Z"
    - latency: 1.359327ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T05:55:15Z"
    - latency: 967.561µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T05:54:15Z"
    - latency: 992.954µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T05:53:15Z"
    - latency: 1.026473ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T05:52:15Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-01T05:47:14Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-254-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-254.ec2.internal
      uid: e5ea164c-f7ea-459f-8f9c-0e74e82584a4
    resourceVersion: "16839"
    uid: cd90f2b3-4b12-409c-88c3-1abf81595b78
  spec:
    sourcePod: network-check-source-65bdbbff45-lkvpm
    targetEndpoint: a48d16c6daeb34c738eede2cf3d45c93-2bfe81bc5b5cb074.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-08-01T05:53:15Z"
      message: 'load-balancer-api-external: tcp connection to a48d16c6daeb34c738eede2cf3d45c93-2bfe81bc5b5cb074.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.46862ms
      message: 'load-balancer-api-external: tcp connection to a48d16c6daeb34c738eede2cf3d45c93-2bfe81bc5b5cb074.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T05:59:15Z"
    - latency: 8.655548ms
      message: 'load-balancer-api-external: resolved host name a48d16c6daeb34c738eede2cf3d45c93-2bfe81bc5b5cb074.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-01T05:59:15Z"
    - latency: 6.435809ms
      message: 'load-balancer-api-external: tcp connection to a48d16c6daeb34c738eede2cf3d45c93-2bfe81bc5b5cb074.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T05:58:15Z"
    - latency: 8.756525ms
      message: 'load-balancer-api-external: resolved host name a48d16c6daeb34c738eede2cf3d45c93-2bfe81bc5b5cb074.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-01T05:58:15Z"
    - latency: 6.661385ms
      message: 'load-balancer-api-external: tcp connection to a48d16c6daeb34c738eede2cf3d45c93-2bfe81bc5b5cb074.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T05:57:15Z"
    - latency: 8.505983ms
      message: 'load-balancer-api-external: resolved host name a48d16c6daeb34c738eede2cf3d45c93-2bfe81bc5b5cb074.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-01T05:57:15Z"
    - latency: 6.163386ms
      message: 'load-balancer-api-external: tcp connection to a48d16c6daeb34c738eede2cf3d45c93-2bfe81bc5b5cb074.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T05:56:15Z"
    - latency: 8.237509ms
      message: 'load-balancer-api-external: resolved host name a48d16c6daeb34c738eede2cf3d45c93-2bfe81bc5b5cb074.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-01T05:56:15Z"
    - latency: 4.936632ms
      message: 'load-balancer-api-external: tcp connection to a48d16c6daeb34c738eede2cf3d45c93-2bfe81bc5b5cb074.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T05:55:15Z"
    - latency: 7.421313ms
      message: 'load-balancer-api-external: resolved host name a48d16c6daeb34c738eede2cf3d45c93-2bfe81bc5b5cb074.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-01T05:55:15Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-01T05:47:14Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-254-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-254.ec2.internal
      uid: e5ea164c-f7ea-459f-8f9c-0e74e82584a4
    resourceVersion: "16838"
    uid: 6fa150c0-6366-40fc-b5b7-414cda7dc406
  spec:
    sourcePod: network-check-source-65bdbbff45-lkvpm
    targetEndpoint: a48d16c6daeb34c738eede2cf3d45c93-2bfe81bc5b5cb074.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-08-01T05:53:15Z"
      message: 'load-balancer-api-internal: tcp connection to a48d16c6daeb34c738eede2cf3d45c93-2bfe81bc5b5cb074.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.543154ms
      message: 'load-balancer-api-internal: tcp connection to a48d16c6daeb34c738eede2cf3d45c93-2bfe81bc5b5cb074.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T05:59:15Z"
    - latency: 8.596898ms
      message: 'load-balancer-api-internal: resolved host name a48d16c6daeb34c738eede2cf3d45c93-2bfe81bc5b5cb074.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-01T05:59:15Z"
    - latency: 5.604612ms
      message: 'load-balancer-api-internal: tcp connection to a48d16c6daeb34c738eede2cf3d45c93-2bfe81bc5b5cb074.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T05:58:15Z"
    - latency: 8.690813ms
      message: 'load-balancer-api-internal: resolved host name a48d16c6daeb34c738eede2cf3d45c93-2bfe81bc5b5cb074.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-01T05:58:15Z"
    - latency: 6.645155ms
      message: 'load-balancer-api-internal: tcp connection to a48d16c6daeb34c738eede2cf3d45c93-2bfe81bc5b5cb074.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T05:57:15Z"
    - latency: 8.570728ms
      message: 'load-balancer-api-internal: resolved host name a48d16c6daeb34c738eede2cf3d45c93-2bfe81bc5b5cb074.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-01T05:57:15Z"
    - latency: 6.127219ms
      message: 'load-balancer-api-internal: tcp connection to a48d16c6daeb34c738eede2cf3d45c93-2bfe81bc5b5cb074.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T05:56:15Z"
    - latency: 8.180592ms
      message: 'load-balancer-api-internal: resolved host name a48d16c6daeb34c738eede2cf3d45c93-2bfe81bc5b5cb074.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-01T05:56:15Z"
    - latency: 4.972249ms
      message: 'load-balancer-api-internal: tcp connection to a48d16c6daeb34c738eede2cf3d45c93-2bfe81bc5b5cb074.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T05:55:15Z"
    - latency: 7.374952ms
      message: 'load-balancer-api-internal: resolved host name a48d16c6daeb34c738eede2cf3d45c93-2bfe81bc5b5cb074.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-01T05:55:15Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-01T05:47:14Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-254-to-network-check-target-ip-10-0-136-146
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-254.ec2.internal
      uid: e5ea164c-f7ea-459f-8f9c-0e74e82584a4
    resourceVersion: "17451"
    uid: 8411b27a-59fa-44e7-84c9-dda8fb0bb62e
  spec:
    sourcePod: network-check-source-65bdbbff45-lkvpm
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-08-01T05:54:15Z"
      message: 'network-check-target-ip-10-0-136-146: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.657095ms
      message: 'network-check-target-ip-10-0-136-146: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T06:01:15Z"
    - latency: 2.206738ms
      message: 'network-check-target-ip-10-0-136-146: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T06:00:15Z"
    - latency: 2.377334ms
      message: 'network-check-target-ip-10-0-136-146: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T05:59:15Z"
    - latency: 2.16717ms
      message: 'network-check-target-ip-10-0-136-146: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T05:58:15Z"
    - latency: 2.155203ms
      message: 'network-check-target-ip-10-0-136-146: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T05:57:15Z"
    - latency: 2.351613ms
      message: 'network-check-target-ip-10-0-136-146: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T05:56:15Z"
    - latency: 2.39554ms
      message: 'network-check-target-ip-10-0-136-146: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T05:55:15Z"
    - latency: 2.368979ms
      message: 'network-check-target-ip-10-0-136-146: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T05:54:15Z"
    - latency: 10.93416ms
      message: 'network-check-target-ip-10-0-136-146: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T05:53:15Z"
    - latency: 2.306579ms
      message: 'network-check-target-ip-10-0-136-146: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T05:52:15Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-01T05:47:14Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-254-to-network-check-target-ip-10-0-137-254
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-254.ec2.internal
      uid: e5ea164c-f7ea-459f-8f9c-0e74e82584a4
    resourceVersion: "17449"
    uid: 352c1b8f-65fa-481f-b4a3-4101685623ab
  spec:
    sourcePod: network-check-source-65bdbbff45-lkvpm
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-08-01T05:54:15Z"
      message: 'network-check-target-ip-10-0-137-254: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.414099ms
      message: 'network-check-target-ip-10-0-137-254: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T06:01:15Z"
    - latency: 994.1µs
      message: 'network-check-target-ip-10-0-137-254: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T06:00:15Z"
    - latency: 954.943µs
      message: 'network-check-target-ip-10-0-137-254: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T05:59:15Z"
    - latency: 1.004195ms
      message: 'network-check-target-ip-10-0-137-254: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T05:58:15Z"
    - latency: 1.074694ms
      message: 'network-check-target-ip-10-0-137-254: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T05:57:15Z"
    - latency: 1.00857ms
      message: 'network-check-target-ip-10-0-137-254: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T05:56:15Z"
    - latency: 1.021822ms
      message: 'network-check-target-ip-10-0-137-254: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T05:55:15Z"
    - latency: 1.111692ms
      message: 'network-check-target-ip-10-0-137-254: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T05:54:15Z"
    - latency: 10.095668ms
      message: 'network-check-target-ip-10-0-137-254: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T05:53:15Z"
    - latency: 1.377855ms
      message: 'network-check-target-ip-10-0-137-254: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T05:52:15Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-01T05:47:14Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-254-to-network-check-target-ip-10-0-138-6
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-254.ec2.internal
      uid: e5ea164c-f7ea-459f-8f9c-0e74e82584a4
    resourceVersion: "17450"
    uid: 59388a62-625f-4d19-b65e-a4b38f17e4f2
  spec:
    sourcePod: network-check-source-65bdbbff45-lkvpm
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-08-01T05:54:15Z"
      message: 'network-check-target-ip-10-0-138-6: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.254108ms
      message: 'network-check-target-ip-10-0-138-6: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T06:01:15Z"
    - latency: 2.104751ms
      message: 'network-check-target-ip-10-0-138-6: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T06:00:15Z"
    - latency: 2.410101ms
      message: 'network-check-target-ip-10-0-138-6: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T05:59:15Z"
    - latency: 2.251971ms
      message: 'network-check-target-ip-10-0-138-6: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T05:58:15Z"
    - latency: 2.344766ms
      message: 'network-check-target-ip-10-0-138-6: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T05:57:15Z"
    - latency: 2.293865ms
      message: 'network-check-target-ip-10-0-138-6: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T05:56:15Z"
    - latency: 2.323269ms
      message: 'network-check-target-ip-10-0-138-6: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T05:55:15Z"
    - latency: 2.254259ms
      message: 'network-check-target-ip-10-0-138-6: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T05:54:15Z"
    - latency: 9.940144ms
      message: 'network-check-target-ip-10-0-138-6: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T05:53:15Z"
    - latency: 2.394425ms
      message: 'network-check-target-ip-10-0-138-6: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T05:52:15Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-01T05:47:14Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-254-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-254.ec2.internal
      uid: e5ea164c-f7ea-459f-8f9c-0e74e82584a4
    resourceVersion: "16837"
    uid: b93b9fb2-3959-4844-9333-871923da2989
  spec:
    sourcePod: network-check-source-65bdbbff45-lkvpm
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-08-01T05:53:15Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 812.297µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T05:59:15Z"
    - latency: 1.888211ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-01T05:59:15Z"
    - latency: 892.179µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T05:58:15Z"
    - latency: 1.895973ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-01T05:58:15Z"
    - latency: 1.133545ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T05:57:15Z"
    - latency: 1.885231ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-01T05:57:15Z"
    - latency: 1.283689ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T05:56:15Z"
    - latency: 1.743425ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-01T05:56:15Z"
    - latency: 1.232062ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T05:55:15Z"
    - latency: 1.906486ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-01T05:55:15Z"
kind: List
metadata:
  resourceVersion: ""