apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T08:03:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-41-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-41.ec2.internal
      uid: 65e64f01-02b8-42ef-833f-dcf15f210932
    resourceVersion: "60978"
    uid: 9fd8a5f9-9c87-43d2-9f9f-4ae8e7a2516d
  spec:
    sourcePod: network-check-source-869dcfcdcd-f2rdl
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T08:10:31Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.156261ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T08:45:31Z"
    - latency: 1.502266ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T08:44:31Z"
    - latency: 1.348437ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T08:43:31Z"
    - latency: 1.208798ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T08:42:31Z"
    - latency: 929.953µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T08:41:31Z"
    - latency: 1.09315ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T08:40:31Z"
    - latency: 952.137µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T08:39:31Z"
    - latency: 1.72933ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T08:38:31Z"
    - latency: 979.486µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T08:37:31Z"
    - latency: 1.070769ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T08:36:31Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T08:03:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-41-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-41.ec2.internal
      uid: 65e64f01-02b8-42ef-833f-dcf15f210932
    resourceVersion: "60979"
    uid: 65a7f0ab-33b7-4555-8164-bd921d144221
  spec:
    sourcePod: network-check-source-869dcfcdcd-f2rdl
    targetEndpoint: a90fd040ee9214da99b6d18dd5d2326c-9a2d19c97f5ae1da.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T08:09:31Z"
      message: 'load-balancer-api-external: tcp connection to a90fd040ee9214da99b6d18dd5d2326c-9a2d19c97f5ae1da.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.857738ms
      message: 'load-balancer-api-external: tcp connection to a90fd040ee9214da99b6d18dd5d2326c-9a2d19c97f5ae1da.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T08:45:31Z"
    - latency: 6.997374ms
      message: 'load-balancer-api-external: resolved host name a90fd040ee9214da99b6d18dd5d2326c-9a2d19c97f5ae1da.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T08:45:31Z"
    - latency: 5.069176ms
      message: 'load-balancer-api-external: tcp connection to a90fd040ee9214da99b6d18dd5d2326c-9a2d19c97f5ae1da.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T08:44:31Z"
    - latency: 7.663516ms
      message: 'load-balancer-api-external: resolved host name a90fd040ee9214da99b6d18dd5d2326c-9a2d19c97f5ae1da.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T08:44:31Z"
    - latency: 4.248937ms
      message: 'load-balancer-api-external: tcp connection to a90fd040ee9214da99b6d18dd5d2326c-9a2d19c97f5ae1da.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T08:43:31Z"
    - latency: 9.804337ms
      message: 'load-balancer-api-external: resolved host name a90fd040ee9214da99b6d18dd5d2326c-9a2d19c97f5ae1da.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T08:43:31Z"
    - latency: 3.833887ms
      message: 'load-balancer-api-external: tcp connection to a90fd040ee9214da99b6d18dd5d2326c-9a2d19c97f5ae1da.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T08:42:31Z"
    - latency: 10.611995ms
      message: 'load-balancer-api-external: resolved host name a90fd040ee9214da99b6d18dd5d2326c-9a2d19c97f5ae1da.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T08:42:31Z"
    - latency: 3.397166ms
      message: 'load-balancer-api-external: tcp connection to a90fd040ee9214da99b6d18dd5d2326c-9a2d19c97f5ae1da.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T08:41:31Z"
    - latency: 7.000359ms
      message: 'load-balancer-api-external: resolved host name a90fd040ee9214da99b6d18dd5d2326c-9a2d19c97f5ae1da.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T08:41:31Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T08:03:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-41-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-41.ec2.internal
      uid: 65e64f01-02b8-42ef-833f-dcf15f210932
    resourceVersion: "60980"
    uid: 74b2b928-bfc2-4269-aebc-043f3f7d265f
  spec:
    sourcePod: network-check-source-869dcfcdcd-f2rdl
    targetEndpoint: a90fd040ee9214da99b6d18dd5d2326c-9a2d19c97f5ae1da.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T08:09:31Z"
      message: 'load-balancer-api-internal: tcp connection to a90fd040ee9214da99b6d18dd5d2326c-9a2d19c97f5ae1da.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.866001ms
      message: 'load-balancer-api-internal: tcp connection to a90fd040ee9214da99b6d18dd5d2326c-9a2d19c97f5ae1da.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T08:45:31Z"
    - latency: 6.932093ms
      message: 'load-balancer-api-internal: resolved host name a90fd040ee9214da99b6d18dd5d2326c-9a2d19c97f5ae1da.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T08:45:31Z"
    - latency: 5.101609ms
      message: 'load-balancer-api-internal: tcp connection to a90fd040ee9214da99b6d18dd5d2326c-9a2d19c97f5ae1da.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T08:44:31Z"
    - latency: 7.649295ms
      message: 'load-balancer-api-internal: resolved host name a90fd040ee9214da99b6d18dd5d2326c-9a2d19c97f5ae1da.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T08:44:31Z"
    - latency: 4.228398ms
      message: 'load-balancer-api-internal: tcp connection to a90fd040ee9214da99b6d18dd5d2326c-9a2d19c97f5ae1da.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T08:43:31Z"
    - latency: 9.781179ms
      message: 'load-balancer-api-internal: resolved host name a90fd040ee9214da99b6d18dd5d2326c-9a2d19c97f5ae1da.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T08:43:31Z"
    - latency: 3.853577ms
      message: 'load-balancer-api-internal: tcp connection to a90fd040ee9214da99b6d18dd5d2326c-9a2d19c97f5ae1da.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T08:42:31Z"
    - latency: 10.538918ms
      message: 'load-balancer-api-internal: resolved host name a90fd040ee9214da99b6d18dd5d2326c-9a2d19c97f5ae1da.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T08:42:31Z"
    - latency: 3.41389ms
      message: 'load-balancer-api-internal: tcp connection to a90fd040ee9214da99b6d18dd5d2326c-9a2d19c97f5ae1da.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T08:41:31Z"
    - latency: 7.365881ms
      message: 'load-balancer-api-internal: resolved host name a90fd040ee9214da99b6d18dd5d2326c-9a2d19c97f5ae1da.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T08:41:31Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T08:03:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-41-to-network-check-target-ip-10-0-128-37
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-41.ec2.internal
      uid: 65e64f01-02b8-42ef-833f-dcf15f210932
    resourceVersion: "60975"
    uid: 6322e899-d203-44a6-8e23-0659b4b62618
  spec:
    sourcePod: network-check-source-869dcfcdcd-f2rdl
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T08:10:31Z"
      message: 'network-check-target-ip-10-0-128-37: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.126697ms
      message: 'network-check-target-ip-10-0-128-37: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T08:45:31Z"
    - latency: 2.020354ms
      message: 'network-check-target-ip-10-0-128-37: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T08:44:31Z"
    - latency: 2.197927ms
      message: 'network-check-target-ip-10-0-128-37: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T08:43:31Z"
    - latency: 2.340635ms
      message: 'network-check-target-ip-10-0-128-37: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T08:42:31Z"
    - latency: 2.523017ms
      message: 'network-check-target-ip-10-0-128-37: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T08:41:31Z"
    - latency: 2.255697ms
      message: 'network-check-target-ip-10-0-128-37: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T08:40:31Z"
    - latency: 2.284726ms
      message: 'network-check-target-ip-10-0-128-37: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T08:39:31Z"
    - latency: 1.926832ms
      message: 'network-check-target-ip-10-0-128-37: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T08:38:31Z"
    - latency: 1.927086ms
      message: 'network-check-target-ip-10-0-128-37: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T08:37:31Z"
    - latency: 2.669285ms
      message: 'network-check-target-ip-10-0-128-37: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T08:36:31Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T08:03:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-41-to-network-check-target-ip-10-0-139-41
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-41.ec2.internal
      uid: 65e64f01-02b8-42ef-833f-dcf15f210932
    resourceVersion: "60974"
    uid: 3b587a17-f748-4030-b17c-ed905b40b799
  spec:
    sourcePod: network-check-source-869dcfcdcd-f2rdl
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T08:10:31Z"
      message: 'network-check-target-ip-10-0-139-41: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.326639ms
      message: 'network-check-target-ip-10-0-139-41: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T08:45:31Z"
    - latency: 865.038µs
      message: 'network-check-target-ip-10-0-139-41: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T08:44:31Z"
    - latency: 950.809µs
      message: 'network-check-target-ip-10-0-139-41: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T08:43:31Z"
    - latency: 841.284µs
      message: 'network-check-target-ip-10-0-139-41: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T08:42:31Z"
    - latency: 1.110671ms
      message: 'network-check-target-ip-10-0-139-41: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T08:41:31Z"
    - latency: 874.484µs
      message: 'network-check-target-ip-10-0-139-41: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T08:40:31Z"
    - latency: 1.015362ms
      message: 'network-check-target-ip-10-0-139-41: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T08:39:31Z"
    - latency: 733.449µs
      message: 'network-check-target-ip-10-0-139-41: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T08:38:31Z"
    - latency: 857.729µs
      message: 'network-check-target-ip-10-0-139-41: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T08:37:31Z"
    - latency: 1.017887ms
      message: 'network-check-target-ip-10-0-139-41: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T08:36:31Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T08:03:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-41-to-network-check-target-ip-10-0-141-240
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-41.ec2.internal
      uid: 65e64f01-02b8-42ef-833f-dcf15f210932
    resourceVersion: "60976"
    uid: 88df193b-2437-4f2c-b9f9-2895a1071ca0
  spec:
    sourcePod: network-check-source-869dcfcdcd-f2rdl
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T08:10:31Z"
      message: 'network-check-target-ip-10-0-141-240: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.353958ms
      message: 'network-check-target-ip-10-0-141-240: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T08:45:31Z"
    - latency: 2.243605ms
      message: 'network-check-target-ip-10-0-141-240: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T08:44:31Z"
    - latency: 2.274025ms
      message: 'network-check-target-ip-10-0-141-240: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T08:43:31Z"
    - latency: 2.23196ms
      message: 'network-check-target-ip-10-0-141-240: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T08:42:31Z"
    - latency: 3.451436ms
      message: 'network-check-target-ip-10-0-141-240: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T08:41:31Z"
    - latency: 2.150732ms
      message: 'network-check-target-ip-10-0-141-240: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T08:40:31Z"
    - latency: 2.597963ms
      message: 'network-check-target-ip-10-0-141-240: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T08:39:31Z"
    - latency: 2.742479ms
      message: 'network-check-target-ip-10-0-141-240: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T08:38:31Z"
    - latency: 2.254752ms
      message: 'network-check-target-ip-10-0-141-240: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T08:37:31Z"
    - latency: 2.348746ms
      message: 'network-check-target-ip-10-0-141-240: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T08:36:31Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T08:03:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-41-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-41.ec2.internal
      uid: 65e64f01-02b8-42ef-833f-dcf15f210932
    resourceVersion: "60977"
    uid: eeb5faaf-3a85-4968-8776-2c30a2d71fa9
  spec:
    sourcePod: network-check-source-869dcfcdcd-f2rdl
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T08:09:31Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 900.75µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T08:45:31Z"
    - latency: 2.077941ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T08:45:31Z"
    - latency: 896.727µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T08:44:31Z"
    - latency: 2.101134ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T08:44:31Z"
    - latency: 1.114287ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T08:43:31Z"
    - latency: 1.601295ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T08:43:31Z"
    - latency: 1.037274ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T08:42:31Z"
    - latency: 2.111856ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T08:42:31Z"
    - latency: 860.673µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T08:41:31Z"
    - latency: 1.924757ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T08:41:31Z"
kind: List
metadata:
  resourceVersion: ""