apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T18:12:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-158-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-158.ec2.internal
      uid: 0e506488-b6ed-409b-9aca-b5f5fe2d77ca
    resourceVersion: "22395"
    uid: 00dd567f-9b9e-4d90-ac11-174c76ecb7db
  spec:
    sourcePod: network-check-source-56499946bc-c9pdm
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T18:19:09Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 923.693µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:33:09Z"
    - latency: 980.491µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:32:09Z"
    - latency: 982.338µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:31:09Z"
    - latency: 1.09961ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:30:09Z"
    - latency: 1.027223ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:29:09Z"
    - latency: 1.190575ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:28:09Z"
    - latency: 946.096µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:27:09Z"
    - latency: 1.012018ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:26:09Z"
    - latency: 1.001235ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:25:09Z"
    - latency: 1.026653ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:24:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T18:12:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-158-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-158.ec2.internal
      uid: 0e506488-b6ed-409b-9aca-b5f5fe2d77ca
    resourceVersion: "21058"
    uid: b2758d4e-1bf9-47a4-b5aa-e865a15b558f
  spec:
    sourcePod: network-check-source-56499946bc-c9pdm
    targetEndpoint: acd987f872b9444a5962822b6975f81c-f5178f383bcfee95.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T18:18:09Z"
      message: 'load-balancer-api-external: tcp connection to acd987f872b9444a5962822b6975f81c-f5178f383bcfee95.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.384817ms
      message: 'load-balancer-api-external: tcp connection to acd987f872b9444a5962822b6975f81c-f5178f383bcfee95.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:30:09Z"
    - latency: 6.48952ms
      message: 'load-balancer-api-external: resolved host name acd987f872b9444a5962822b6975f81c-f5178f383bcfee95.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T18:30:09Z"
    - latency: 4.421211ms
      message: 'load-balancer-api-external: tcp connection to acd987f872b9444a5962822b6975f81c-f5178f383bcfee95.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:29:09Z"
    - latency: 6.539334ms
      message: 'load-balancer-api-external: resolved host name acd987f872b9444a5962822b6975f81c-f5178f383bcfee95.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T18:29:09Z"
    - latency: 4.300663ms
      message: 'load-balancer-api-external: tcp connection to acd987f872b9444a5962822b6975f81c-f5178f383bcfee95.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:28:09Z"
    - latency: 6.739856ms
      message: 'load-balancer-api-external: resolved host name acd987f872b9444a5962822b6975f81c-f5178f383bcfee95.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T18:28:09Z"
    - latency: 5.445311ms
      message: 'load-balancer-api-external: tcp connection to acd987f872b9444a5962822b6975f81c-f5178f383bcfee95.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:27:09Z"
    - latency: 7.639557ms
      message: 'load-balancer-api-external: resolved host name acd987f872b9444a5962822b6975f81c-f5178f383bcfee95.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T18:27:09Z"
    - latency: 6.624861ms
      message: 'load-balancer-api-external: tcp connection to acd987f872b9444a5962822b6975f81c-f5178f383bcfee95.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:26:09Z"
    - latency: 7.300084ms
      message: 'load-balancer-api-external: resolved host name acd987f872b9444a5962822b6975f81c-f5178f383bcfee95.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T18:26:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T18:12:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-158-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-158.ec2.internal
      uid: 0e506488-b6ed-409b-9aca-b5f5fe2d77ca
    resourceVersion: "21057"
    uid: 57a81455-120a-4327-9e24-d671c2e1b841
  spec:
    sourcePod: network-check-source-56499946bc-c9pdm
    targetEndpoint: acd987f872b9444a5962822b6975f81c-f5178f383bcfee95.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T18:18:09Z"
      message: 'load-balancer-api-internal: tcp connection to acd987f872b9444a5962822b6975f81c-f5178f383bcfee95.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.420638ms
      message: 'load-balancer-api-internal: tcp connection to acd987f872b9444a5962822b6975f81c-f5178f383bcfee95.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:30:09Z"
    - latency: 6.56857ms
      message: 'load-balancer-api-internal: resolved host name acd987f872b9444a5962822b6975f81c-f5178f383bcfee95.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T18:30:09Z"
    - latency: 4.052444ms
      message: 'load-balancer-api-internal: tcp connection to acd987f872b9444a5962822b6975f81c-f5178f383bcfee95.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:29:09Z"
    - latency: 6.610654ms
      message: 'load-balancer-api-internal: resolved host name acd987f872b9444a5962822b6975f81c-f5178f383bcfee95.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T18:29:09Z"
    - latency: 5.069848ms
      message: 'load-balancer-api-internal: tcp connection to acd987f872b9444a5962822b6975f81c-f5178f383bcfee95.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:28:09Z"
    - latency: 6.785685ms
      message: 'load-balancer-api-internal: resolved host name acd987f872b9444a5962822b6975f81c-f5178f383bcfee95.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T18:28:09Z"
    - latency: 5.688842ms
      message: 'load-balancer-api-internal: tcp connection to acd987f872b9444a5962822b6975f81c-f5178f383bcfee95.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:27:09Z"
    - latency: 7.717743ms
      message: 'load-balancer-api-internal: resolved host name acd987f872b9444a5962822b6975f81c-f5178f383bcfee95.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T18:27:09Z"
    - latency: 5.530499ms
      message: 'load-balancer-api-internal: tcp connection to acd987f872b9444a5962822b6975f81c-f5178f383bcfee95.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:26:09Z"
    - latency: 7.338788ms
      message: 'load-balancer-api-internal: resolved host name acd987f872b9444a5962822b6975f81c-f5178f383bcfee95.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T18:26:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T18:12:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-158-to-network-check-target-ip-10-0-136-158
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-158.ec2.internal
      uid: 0e506488-b6ed-409b-9aca-b5f5fe2d77ca
    resourceVersion: "22392"
    uid: 7fdc2ba2-b082-4f08-9ec9-fb2ca1810364
  spec:
    sourcePod: network-check-source-56499946bc-c9pdm
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T18:19:09Z"
      message: 'network-check-target-ip-10-0-136-158: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 907.733µs
      message: 'network-check-target-ip-10-0-136-158: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:33:09Z"
    - latency: 1.532034ms
      message: 'network-check-target-ip-10-0-136-158: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:32:09Z"
    - latency: 1.112587ms
      message: 'network-check-target-ip-10-0-136-158: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:31:09Z"
    - latency: 1.244877ms
      message: 'network-check-target-ip-10-0-136-158: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:30:09Z"
    - latency: 974.167µs
      message: 'network-check-target-ip-10-0-136-158: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:29:09Z"
    - latency: 887.024µs
      message: 'network-check-target-ip-10-0-136-158: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:28:09Z"
    - latency: 927.398µs
      message: 'network-check-target-ip-10-0-136-158: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:27:09Z"
    - latency: 1.048732ms
      message: 'network-check-target-ip-10-0-136-158: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:26:09Z"
    - latency: 926.884µs
      message: 'network-check-target-ip-10-0-136-158: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:25:09Z"
    - latency: 917.063µs
      message: 'network-check-target-ip-10-0-136-158: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:24:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T18:12:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-158-to-network-check-target-ip-10-0-139-128
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-158.ec2.internal
      uid: 0e506488-b6ed-409b-9aca-b5f5fe2d77ca
    resourceVersion: "22393"
    uid: 1a8c86fc-c3fd-432e-b610-992d3bdce6c7
  spec:
    sourcePod: network-check-source-56499946bc-c9pdm
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T18:19:09Z"
      message: 'network-check-target-ip-10-0-139-128: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.216129ms
      message: 'network-check-target-ip-10-0-139-128: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:33:09Z"
    - latency: 2.212256ms
      message: 'network-check-target-ip-10-0-139-128: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:32:09Z"
    - latency: 2.233644ms
      message: 'network-check-target-ip-10-0-139-128: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:31:09Z"
    - latency: 2.225559ms
      message: 'network-check-target-ip-10-0-139-128: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:30:09Z"
    - latency: 2.161488ms
      message: 'network-check-target-ip-10-0-139-128: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:29:09Z"
    - latency: 2.341279ms
      message: 'network-check-target-ip-10-0-139-128: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:28:09Z"
    - latency: 2.345825ms
      message: 'network-check-target-ip-10-0-139-128: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:27:09Z"
    - latency: 2.780999ms
      message: 'network-check-target-ip-10-0-139-128: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:26:09Z"
    - latency: 2.349976ms
      message: 'network-check-target-ip-10-0-139-128: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:25:09Z"
    - latency: 2.491566ms
      message: 'network-check-target-ip-10-0-139-128: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:24:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T18:12:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-158-to-network-check-target-ip-10-0-140-183
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-158.ec2.internal
      uid: 0e506488-b6ed-409b-9aca-b5f5fe2d77ca
    resourceVersion: "22394"
    uid: 709afa3c-a5b7-4ad9-9c49-bd9b1f725483
  spec:
    sourcePod: network-check-source-56499946bc-c9pdm
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T18:19:09Z"
      message: 'network-check-target-ip-10-0-140-183: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.255725ms
      message: 'network-check-target-ip-10-0-140-183: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:33:09Z"
    - latency: 2.501008ms
      message: 'network-check-target-ip-10-0-140-183: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:32:09Z"
    - latency: 2.667189ms
      message: 'network-check-target-ip-10-0-140-183: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:31:09Z"
    - latency: 2.347457ms
      message: 'network-check-target-ip-10-0-140-183: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:30:09Z"
    - latency: 2.215648ms
      message: 'network-check-target-ip-10-0-140-183: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:29:09Z"
    - latency: 2.502963ms
      message: 'network-check-target-ip-10-0-140-183: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:28:09Z"
    - latency: 2.39448ms
      message: 'network-check-target-ip-10-0-140-183: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:27:09Z"
    - latency: 2.141764ms
      message: 'network-check-target-ip-10-0-140-183: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:26:09Z"
    - latency: 2.590096ms
      message: 'network-check-target-ip-10-0-140-183: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:25:09Z"
    - latency: 2.136625ms
      message: 'network-check-target-ip-10-0-140-183: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:24:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T18:12:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-158-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-158.ec2.internal
      uid: 0e506488-b6ed-409b-9aca-b5f5fe2d77ca
    resourceVersion: "21056"
    uid: a3918e01-478d-42e3-a7c9-5e2683da760a
  spec:
    sourcePod: network-check-source-56499946bc-c9pdm
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T18:18:09Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.197755ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:30:09Z"
    - latency: 1.86007ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T18:30:09Z"
    - latency: 884.097µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:29:09Z"
    - latency: 1.593168ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T18:29:09Z"
    - latency: 976.439µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:28:09Z"
    - latency: 1.89879ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T18:28:09Z"
    - latency: 699.324µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:27:09Z"
    - latency: 2.392271ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T18:27:09Z"
    - latency: 928.185µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:26:09Z"
    - latency: 2.104114ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T18:26:09Z"
kind: List
metadata:
  resourceVersion: ""