apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-02T09:37:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-118-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-118.ec2.internal
      uid: bb28d5dd-35e5-45b3-9ecb-e03ea7064f30
    resourceVersion: "76850"
    uid: 3da1c349-8b4e-4cef-84a9-2873078f8047
  spec:
    sourcePod: network-check-source-65bdbbff45-n6ngw
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-08-02T09:44:04Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.038455ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-02T10:33:04Z"
    - latency: 1.157497ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-02T10:32:04Z"
    - latency: 785.285µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-02T10:31:04Z"
    - latency: 1.117259ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-02T10:30:04Z"
    - latency: 906.337µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-02T10:29:04Z"
    - latency: 988.866µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-02T10:28:04Z"
    - latency: 1.171198ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-02T10:27:04Z"
    - latency: 1.285239ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-02T10:26:04Z"
    - latency: 1.581729ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-02T10:25:04Z"
    - latency: 840.074µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-02T10:24:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-02T09:37:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-118-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-118.ec2.internal
      uid: bb28d5dd-35e5-45b3-9ecb-e03ea7064f30
    resourceVersion: "74518"
    uid: f6dae544-312a-44af-95ee-1304b51cf962
  spec:
    sourcePod: network-check-source-65bdbbff45-n6ngw
    targetEndpoint: a63a66d6a8f7b4c4ab35091b602706ab-96fe7ee93b461e23.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-08-02T09:43:04Z"
      message: 'load-balancer-api-external: tcp connection to a63a66d6a8f7b4c4ab35091b602706ab-96fe7ee93b461e23.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.945216ms
      message: 'load-balancer-api-external: tcp connection to a63a66d6a8f7b4c4ab35091b602706ab-96fe7ee93b461e23.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-02T10:31:04Z"
    - latency: 7.466228ms
      message: 'load-balancer-api-external: resolved host name a63a66d6a8f7b4c4ab35091b602706ab-96fe7ee93b461e23.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-02T10:31:04Z"
    - latency: 5.757735ms
      message: 'load-balancer-api-external: tcp connection to a63a66d6a8f7b4c4ab35091b602706ab-96fe7ee93b461e23.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-02T10:30:04Z"
    - latency: 7.472401ms
      message: 'load-balancer-api-external: resolved host name a63a66d6a8f7b4c4ab35091b602706ab-96fe7ee93b461e23.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-02T10:30:04Z"
    - latency: 4.841469ms
      message: 'load-balancer-api-external: tcp connection to a63a66d6a8f7b4c4ab35091b602706ab-96fe7ee93b461e23.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-02T10:29:04Z"
    - latency: 7.330312ms
      message: 'load-balancer-api-external: resolved host name a63a66d6a8f7b4c4ab35091b602706ab-96fe7ee93b461e23.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-02T10:29:04Z"
    - latency: 5.738993ms
      message: 'load-balancer-api-external: tcp connection to a63a66d6a8f7b4c4ab35091b602706ab-96fe7ee93b461e23.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-02T10:28:04Z"
    - latency: 7.047895ms
      message: 'load-balancer-api-external: resolved host name a63a66d6a8f7b4c4ab35091b602706ab-96fe7ee93b461e23.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-02T10:28:04Z"
    - latency: 5.283267ms
      message: 'load-balancer-api-external: tcp connection to a63a66d6a8f7b4c4ab35091b602706ab-96fe7ee93b461e23.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-02T10:27:04Z"
    - latency: 7.649714ms
      message: 'load-balancer-api-external: resolved host name a63a66d6a8f7b4c4ab35091b602706ab-96fe7ee93b461e23.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-02T10:27:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-02T09:37:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-118-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-118.ec2.internal
      uid: bb28d5dd-35e5-45b3-9ecb-e03ea7064f30
    resourceVersion: "74519"
    uid: e3692c74-7450-4f8f-be69-c52971eb8cf9
  spec:
    sourcePod: network-check-source-65bdbbff45-n6ngw
    targetEndpoint: a63a66d6a8f7b4c4ab35091b602706ab-96fe7ee93b461e23.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-08-02T09:43:04Z"
      message: 'load-balancer-api-internal: tcp connection to a63a66d6a8f7b4c4ab35091b602706ab-96fe7ee93b461e23.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 8.725358ms
      message: 'load-balancer-api-internal: tcp connection to a63a66d6a8f7b4c4ab35091b602706ab-96fe7ee93b461e23.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-02T10:31:04Z"
    - latency: 7.543716ms
      message: 'load-balancer-api-internal: resolved host name a63a66d6a8f7b4c4ab35091b602706ab-96fe7ee93b461e23.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-02T10:31:04Z"
    - latency: 5.147518ms
      message: 'load-balancer-api-internal: tcp connection to a63a66d6a8f7b4c4ab35091b602706ab-96fe7ee93b461e23.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-02T10:30:04Z"
    - latency: 7.363069ms
      message: 'load-balancer-api-internal: resolved host name a63a66d6a8f7b4c4ab35091b602706ab-96fe7ee93b461e23.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-02T10:30:04Z"
    - latency: 4.836037ms
      message: 'load-balancer-api-internal: tcp connection to a63a66d6a8f7b4c4ab35091b602706ab-96fe7ee93b461e23.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-02T10:29:04Z"
    - latency: 7.360908ms
      message: 'load-balancer-api-internal: resolved host name a63a66d6a8f7b4c4ab35091b602706ab-96fe7ee93b461e23.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-02T10:29:04Z"
    - latency: 5.700794ms
      message: 'load-balancer-api-internal: tcp connection to a63a66d6a8f7b4c4ab35091b602706ab-96fe7ee93b461e23.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-02T10:28:04Z"
    - latency: 7.015714ms
      message: 'load-balancer-api-internal: resolved host name a63a66d6a8f7b4c4ab35091b602706ab-96fe7ee93b461e23.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-02T10:28:04Z"
    - latency: 4.798772ms
      message: 'load-balancer-api-internal: tcp connection to a63a66d6a8f7b4c4ab35091b602706ab-96fe7ee93b461e23.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-02T10:27:04Z"
    - latency: 7.756992ms
      message: 'load-balancer-api-internal: resolved host name a63a66d6a8f7b4c4ab35091b602706ab-96fe7ee93b461e23.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-02T10:27:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-02T09:37:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-118-to-network-check-target-ip-10-0-130-182
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-118.ec2.internal
      uid: bb28d5dd-35e5-45b3-9ecb-e03ea7064f30
    resourceVersion: "76849"
    uid: a6dae2f5-9bd8-4d00-bdbe-eef3b2dcc777
  spec:
    sourcePod: network-check-source-65bdbbff45-n6ngw
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-08-02T09:44:04Z"
      message: 'network-check-target-ip-10-0-130-182: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.24996ms
      message: 'network-check-target-ip-10-0-130-182: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-02T10:33:04Z"
    - latency: 2.122918ms
      message: 'network-check-target-ip-10-0-130-182: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-02T10:32:04Z"
    - latency: 1.809783ms
      message: 'network-check-target-ip-10-0-130-182: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-02T10:31:04Z"
    - latency: 2.034324ms
      message: 'network-check-target-ip-10-0-130-182: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-02T10:30:04Z"
    - latency: 1.618792ms
      message: 'network-check-target-ip-10-0-130-182: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-02T10:29:04Z"
    - latency: 1.93066ms
      message: 'network-check-target-ip-10-0-130-182: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-02T10:28:04Z"
    - latency: 1.705473ms
      message: 'network-check-target-ip-10-0-130-182: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-02T10:27:04Z"
    - latency: 1.905062ms
      message: 'network-check-target-ip-10-0-130-182: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-02T10:26:04Z"
    - latency: 1.922148ms
      message: 'network-check-target-ip-10-0-130-182: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-02T10:25:04Z"
    - latency: 1.708778ms
      message: 'network-check-target-ip-10-0-130-182: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-02T10:24:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-02T09:37:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-118-to-network-check-target-ip-10-0-141-232
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-118.ec2.internal
      uid: bb28d5dd-35e5-45b3-9ecb-e03ea7064f30
    resourceVersion: "76847"
    uid: 577d8d8a-180c-41c7-8379-2abfb7d6ae29
  spec:
    sourcePod: network-check-source-65bdbbff45-n6ngw
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-08-02T09:44:04Z"
      message: 'network-check-target-ip-10-0-141-232: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.285331ms
      message: 'network-check-target-ip-10-0-141-232: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-02T10:33:04Z"
    - latency: 2.43185ms
      message: 'network-check-target-ip-10-0-141-232: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-02T10:32:04Z"
    - latency: 2.103146ms
      message: 'network-check-target-ip-10-0-141-232: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-02T10:31:04Z"
    - latency: 2.432445ms
      message: 'network-check-target-ip-10-0-141-232: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-02T10:30:04Z"
    - latency: 2.371876ms
      message: 'network-check-target-ip-10-0-141-232: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-02T10:29:04Z"
    - latency: 2.287451ms
      message: 'network-check-target-ip-10-0-141-232: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-02T10:28:04Z"
    - latency: 2.38645ms
      message: 'network-check-target-ip-10-0-141-232: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-02T10:27:04Z"
    - latency: 2.424175ms
      message: 'network-check-target-ip-10-0-141-232: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-02T10:26:04Z"
    - latency: 2.088388ms
      message: 'network-check-target-ip-10-0-141-232: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-02T10:25:04Z"
    - latency: 2.276765ms
      message: 'network-check-target-ip-10-0-141-232: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-02T10:24:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-02T09:37:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-118-to-network-check-target-ip-10-0-142-118
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-118.ec2.internal
      uid: bb28d5dd-35e5-45b3-9ecb-e03ea7064f30
    resourceVersion: "76848"
    uid: 0ce14f87-0dc4-40ae-87de-b66f76d1785a
  spec:
    sourcePod: network-check-source-65bdbbff45-n6ngw
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-08-02T09:44:04Z"
      message: 'network-check-target-ip-10-0-142-118: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.516702ms
      message: 'network-check-target-ip-10-0-142-118: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-02T10:33:04Z"
    - latency: 1.354179ms
      message: 'network-check-target-ip-10-0-142-118: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-02T10:32:04Z"
    - latency: 931.914µs
      message: 'network-check-target-ip-10-0-142-118: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-02T10:31:04Z"
    - latency: 1.059036ms
      message: 'network-check-target-ip-10-0-142-118: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-02T10:30:04Z"
    - latency: 1.136667ms
      message: 'network-check-target-ip-10-0-142-118: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-02T10:29:04Z"
    - latency: 1.416159ms
      message: 'network-check-target-ip-10-0-142-118: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-02T10:28:04Z"
    - latency: 1.450288ms
      message: 'network-check-target-ip-10-0-142-118: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-02T10:27:04Z"
    - latency: 910.348µs
      message: 'network-check-target-ip-10-0-142-118: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-02T10:26:04Z"
    - latency: 1.293901ms
      message: 'network-check-target-ip-10-0-142-118: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-02T10:25:04Z"
    - latency: 1.377031ms
      message: 'network-check-target-ip-10-0-142-118: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-02T10:24:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-02T09:37:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-118-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-118.ec2.internal
      uid: bb28d5dd-35e5-45b3-9ecb-e03ea7064f30
    resourceVersion: "74517"
    uid: 5b33bbe8-6a3a-4369-9fc5-bcdaa96f81bf
  spec:
    sourcePod: network-check-source-65bdbbff45-n6ngw
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-08-02T09:43:04Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 911.292µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-02T10:31:04Z"
    - latency: 2.029438ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-02T10:31:04Z"
    - latency: 1.434402ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-02T10:30:04Z"
    - latency: 1.898832ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-02T10:30:04Z"
    - latency: 925.812µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-02T10:29:04Z"
    - latency: 1.819195ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-02T10:29:04Z"
    - latency: 1.046772ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-02T10:28:04Z"
    - latency: 1.779335ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-02T10:28:04Z"
    - latency: 1.530732ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-02T10:27:04Z"
    - latency: 1.839637ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-02T10:27:04Z"
kind: List
metadata:
  resourceVersion: ""