apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T16:36:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-76-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-76.ec2.internal
      uid: c48977e2-7373-45a7-90fb-80c73c678318
    resourceVersion: "22524"
    uid: 9f6c050e-664c-4c03-a2df-49ed9f122729
  spec:
    sourcePod: network-check-source-7cbc45fddc-4kvm8
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T16:43:26Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 905.418µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:50:26Z"
    - latency: 968.504µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:49:26Z"
    - latency: 1.303254ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:48:26Z"
    - latency: 890.754µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:47:26Z"
    - latency: 918.343µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:46:26Z"
    - latency: 1.069703ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:45:26Z"
    - latency: 1.027606ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:44:26Z"
    - latency: 1.068273ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:43:26Z"
    - latency: 951.037µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:42:26Z"
    - latency: 988.007µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:41:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T16:36:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-76-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-76.ec2.internal
      uid: c48977e2-7373-45a7-90fb-80c73c678318
    resourceVersion: "21467"
    uid: 6358b6b7-e28f-4fd8-9f71-33bf58b9dea5
  spec:
    sourcePod: network-check-source-7cbc45fddc-4kvm8
    targetEndpoint: a421721aa0cb24939ba02fe4830b0bd0-fa027696ebbd4d2c.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T16:42:26Z"
      message: 'load-balancer-api-external: tcp connection to a421721aa0cb24939ba02fe4830b0bd0-fa027696ebbd4d2c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.646187ms
      message: 'load-balancer-api-external: tcp connection to a421721aa0cb24939ba02fe4830b0bd0-fa027696ebbd4d2c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:48:26Z"
    - latency: 6.890587ms
      message: 'load-balancer-api-external: resolved host name a421721aa0cb24939ba02fe4830b0bd0-fa027696ebbd4d2c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T16:48:26Z"
    - latency: 8.879748ms
      message: 'load-balancer-api-external: tcp connection to a421721aa0cb24939ba02fe4830b0bd0-fa027696ebbd4d2c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:47:26Z"
    - latency: 6.705361ms
      message: 'load-balancer-api-external: resolved host name a421721aa0cb24939ba02fe4830b0bd0-fa027696ebbd4d2c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T16:47:26Z"
    - latency: 6.045019ms
      message: 'load-balancer-api-external: tcp connection to a421721aa0cb24939ba02fe4830b0bd0-fa027696ebbd4d2c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:46:26Z"
    - latency: 7.732255ms
      message: 'load-balancer-api-external: resolved host name a421721aa0cb24939ba02fe4830b0bd0-fa027696ebbd4d2c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T16:46:26Z"
    - latency: 3.731036ms
      message: 'load-balancer-api-external: tcp connection to a421721aa0cb24939ba02fe4830b0bd0-fa027696ebbd4d2c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:45:26Z"
    - latency: 6.826458ms
      message: 'load-balancer-api-external: resolved host name a421721aa0cb24939ba02fe4830b0bd0-fa027696ebbd4d2c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T16:45:26Z"
    - latency: 6.063856ms
      message: 'load-balancer-api-external: tcp connection to a421721aa0cb24939ba02fe4830b0bd0-fa027696ebbd4d2c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:44:26Z"
    - latency: 5.699398ms
      message: 'load-balancer-api-external: resolved host name a421721aa0cb24939ba02fe4830b0bd0-fa027696ebbd4d2c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T16:44:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T16:36:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-76-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-76.ec2.internal
      uid: c48977e2-7373-45a7-90fb-80c73c678318
    resourceVersion: "21466"
    uid: 38759ed0-9f0f-4566-b947-7fd61f3ddafa
  spec:
    sourcePod: network-check-source-7cbc45fddc-4kvm8
    targetEndpoint: a421721aa0cb24939ba02fe4830b0bd0-fa027696ebbd4d2c.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T16:42:26Z"
      message: 'load-balancer-api-internal: tcp connection to a421721aa0cb24939ba02fe4830b0bd0-fa027696ebbd4d2c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.661606ms
      message: 'load-balancer-api-internal: tcp connection to a421721aa0cb24939ba02fe4830b0bd0-fa027696ebbd4d2c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:48:26Z"
    - latency: 6.950595ms
      message: 'load-balancer-api-internal: resolved host name a421721aa0cb24939ba02fe4830b0bd0-fa027696ebbd4d2c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T16:48:26Z"
    - latency: 3.936106ms
      message: 'load-balancer-api-internal: tcp connection to a421721aa0cb24939ba02fe4830b0bd0-fa027696ebbd4d2c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:47:26Z"
    - latency: 6.790882ms
      message: 'load-balancer-api-internal: resolved host name a421721aa0cb24939ba02fe4830b0bd0-fa027696ebbd4d2c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T16:47:26Z"
    - latency: 6.00266ms
      message: 'load-balancer-api-internal: tcp connection to a421721aa0cb24939ba02fe4830b0bd0-fa027696ebbd4d2c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:46:26Z"
    - latency: 7.809299ms
      message: 'load-balancer-api-internal: resolved host name a421721aa0cb24939ba02fe4830b0bd0-fa027696ebbd4d2c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T16:46:26Z"
    - latency: 4.438542ms
      message: 'load-balancer-api-internal: tcp connection to a421721aa0cb24939ba02fe4830b0bd0-fa027696ebbd4d2c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:45:26Z"
    - latency: 6.800955ms
      message: 'load-balancer-api-internal: resolved host name a421721aa0cb24939ba02fe4830b0bd0-fa027696ebbd4d2c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T16:45:26Z"
    - latency: 6.065817ms
      message: 'load-balancer-api-internal: tcp connection to a421721aa0cb24939ba02fe4830b0bd0-fa027696ebbd4d2c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:44:26Z"
    - latency: 5.638301ms
      message: 'load-balancer-api-internal: resolved host name a421721aa0cb24939ba02fe4830b0bd0-fa027696ebbd4d2c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T16:44:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T16:36:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-76-to-network-check-target-ip-10-0-128-76
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-76.ec2.internal
      uid: c48977e2-7373-45a7-90fb-80c73c678318
    resourceVersion: "22521"
    uid: 77f646fe-09c3-4927-bb10-e585fbbf27d4
  spec:
    sourcePod: network-check-source-7cbc45fddc-4kvm8
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T16:43:26Z"
      message: 'network-check-target-ip-10-0-128-76: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 866.583µs
      message: 'network-check-target-ip-10-0-128-76: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:50:26Z"
    - latency: 866.059µs
      message: 'network-check-target-ip-10-0-128-76: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:49:26Z"
    - latency: 1.446654ms
      message: 'network-check-target-ip-10-0-128-76: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:48:26Z"
    - latency: 814.072µs
      message: 'network-check-target-ip-10-0-128-76: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:47:26Z"
    - latency: 959.008µs
      message: 'network-check-target-ip-10-0-128-76: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:46:26Z"
    - latency: 818.12µs
      message: 'network-check-target-ip-10-0-128-76: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:45:26Z"
    - latency: 1.237889ms
      message: 'network-check-target-ip-10-0-128-76: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:44:26Z"
    - latency: 879.049µs
      message: 'network-check-target-ip-10-0-128-76: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:43:26Z"
    - latency: 1.336901ms
      message: 'network-check-target-ip-10-0-128-76: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:42:26Z"
    - latency: 879.788µs
      message: 'network-check-target-ip-10-0-128-76: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:41:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T16:36:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-76-to-network-check-target-ip-10-0-129-101
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-76.ec2.internal
      uid: c48977e2-7373-45a7-90fb-80c73c678318
    resourceVersion: "22522"
    uid: b9fbc977-cf73-410f-b5b5-82d913be3025
  spec:
    sourcePod: network-check-source-7cbc45fddc-4kvm8
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T16:43:26Z"
      message: 'network-check-target-ip-10-0-129-101: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.261547ms
      message: 'network-check-target-ip-10-0-129-101: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:50:26Z"
    - latency: 2.175677ms
      message: 'network-check-target-ip-10-0-129-101: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:49:26Z"
    - latency: 2.194718ms
      message: 'network-check-target-ip-10-0-129-101: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:48:26Z"
    - latency: 1.89646ms
      message: 'network-check-target-ip-10-0-129-101: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:47:26Z"
    - latency: 1.999031ms
      message: 'network-check-target-ip-10-0-129-101: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:46:26Z"
    - latency: 2.198734ms
      message: 'network-check-target-ip-10-0-129-101: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:45:26Z"
    - latency: 2.421147ms
      message: 'network-check-target-ip-10-0-129-101: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:44:26Z"
    - latency: 2.136551ms
      message: 'network-check-target-ip-10-0-129-101: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:43:26Z"
    - latency: 2.344993ms
      message: 'network-check-target-ip-10-0-129-101: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:42:26Z"
    - latency: 2.126051ms
      message: 'network-check-target-ip-10-0-129-101: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:41:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T16:36:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-76-to-network-check-target-ip-10-0-136-27
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-76.ec2.internal
      uid: c48977e2-7373-45a7-90fb-80c73c678318
    resourceVersion: "22523"
    uid: e2422519-3331-4270-ab13-2ca553290f7f
  spec:
    sourcePod: network-check-source-7cbc45fddc-4kvm8
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T16:43:26Z"
      message: 'network-check-target-ip-10-0-136-27: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.279179ms
      message: 'network-check-target-ip-10-0-136-27: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:50:26Z"
    - latency: 2.391441ms
      message: 'network-check-target-ip-10-0-136-27: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:49:26Z"
    - latency: 2.462376ms
      message: 'network-check-target-ip-10-0-136-27: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:48:26Z"
    - latency: 2.247978ms
      message: 'network-check-target-ip-10-0-136-27: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:47:26Z"
    - latency: 2.568216ms
      message: 'network-check-target-ip-10-0-136-27: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:46:26Z"
    - latency: 2.178214ms
      message: 'network-check-target-ip-10-0-136-27: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:45:26Z"
    - latency: 2.409654ms
      message: 'network-check-target-ip-10-0-136-27: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:44:26Z"
    - latency: 2.478361ms
      message: 'network-check-target-ip-10-0-136-27: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:43:26Z"
    - latency: 1.979472ms
      message: 'network-check-target-ip-10-0-136-27: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:42:26Z"
    - latency: 2.347884ms
      message: 'network-check-target-ip-10-0-136-27: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:41:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T16:36:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-76-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-76.ec2.internal
      uid: c48977e2-7373-45a7-90fb-80c73c678318
    resourceVersion: "21465"
    uid: 1f4fcc27-168f-42f5-812d-e1dfed04045f
  spec:
    sourcePod: network-check-source-7cbc45fddc-4kvm8
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T16:42:26Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.095558ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:48:26Z"
    - latency: 1.606528ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T16:48:26Z"
    - latency: 925.149µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:47:26Z"
    - latency: 1.447567ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T16:47:26Z"
    - latency: 1.269192ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:46:26Z"
    - latency: 1.646436ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T16:46:26Z"
    - latency: 993.801µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:45:26Z"
    - latency: 1.616122ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T16:45:26Z"
    - latency: 709.201µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:44:26Z"
    - latency: 1.517732ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T16:44:26Z"
kind: List
metadata:
  resourceVersion: ""