apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-26T17:53:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-45-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-45.ec2.internal
      uid: 7e0dd6bc-cedd-4d84-af98-b80a12b85b2c
    resourceVersion: "70822"
    uid: 88b8bc14-2760-4086-8f4e-a7c5931556d7
  spec:
    sourcePod: network-check-source-7d88cb55d8-z2knl
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-26T18:00:29Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.14819ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T18:42:29Z"
    - latency: 1.629555ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T18:41:29Z"
    - latency: 1.177169ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T18:40:29Z"
    - latency: 906.714µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T18:39:29Z"
    - latency: 950.076µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T18:38:29Z"
    - latency: 1.463331ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T18:37:29Z"
    - latency: 1.505101ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T18:36:29Z"
    - latency: 1.337376ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T18:35:29Z"
    - latency: 1.360335ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T18:34:29Z"
    - latency: 881.432µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T18:33:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-26T17:53:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-45-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-45.ec2.internal
      uid: 7e0dd6bc-cedd-4d84-af98-b80a12b85b2c
    resourceVersion: "69670"
    uid: 747b92d3-bb6b-40f3-8c92-49e55b4f73e7
  spec:
    sourcePod: network-check-source-7d88cb55d8-z2knl
    targetEndpoint: abb5bbada1b2c444c949f30b853b969e-b1aea9d8fc233123.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-26T17:59:29Z"
      message: 'load-balancer-api-external: tcp connection to abb5bbada1b2c444c949f30b853b969e-b1aea9d8fc233123.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.41634ms
      message: 'load-balancer-api-external: tcp connection to abb5bbada1b2c444c949f30b853b969e-b1aea9d8fc233123.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T18:41:29Z"
    - latency: 8.662055ms
      message: 'load-balancer-api-external: resolved host name abb5bbada1b2c444c949f30b853b969e-b1aea9d8fc233123.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-26T18:41:29Z"
    - latency: 5.77688ms
      message: 'load-balancer-api-external: tcp connection to abb5bbada1b2c444c949f30b853b969e-b1aea9d8fc233123.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T18:40:29Z"
    - latency: 7.907081ms
      message: 'load-balancer-api-external: resolved host name abb5bbada1b2c444c949f30b853b969e-b1aea9d8fc233123.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-26T18:40:29Z"
    - latency: 4.211054ms
      message: 'load-balancer-api-external: tcp connection to abb5bbada1b2c444c949f30b853b969e-b1aea9d8fc233123.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T18:39:29Z"
    - latency: 6.930181ms
      message: 'load-balancer-api-external: resolved host name abb5bbada1b2c444c949f30b853b969e-b1aea9d8fc233123.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-26T18:39:29Z"
    - latency: 5.755577ms
      message: 'load-balancer-api-external: tcp connection to abb5bbada1b2c444c949f30b853b969e-b1aea9d8fc233123.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T18:38:29Z"
    - latency: 9.105217ms
      message: 'load-balancer-api-external: resolved host name abb5bbada1b2c444c949f30b853b969e-b1aea9d8fc233123.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-26T18:38:29Z"
    - latency: 4.666815ms
      message: 'load-balancer-api-external: tcp connection to abb5bbada1b2c444c949f30b853b969e-b1aea9d8fc233123.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T18:37:29Z"
    - latency: 8.460227ms
      message: 'load-balancer-api-external: resolved host name abb5bbada1b2c444c949f30b853b969e-b1aea9d8fc233123.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-26T18:37:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-26T17:53:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-45-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-45.ec2.internal
      uid: 7e0dd6bc-cedd-4d84-af98-b80a12b85b2c
    resourceVersion: "69669"
    uid: 4096a6cf-a476-4538-bd18-9037d14d9897
  spec:
    sourcePod: network-check-source-7d88cb55d8-z2knl
    targetEndpoint: abb5bbada1b2c444c949f30b853b969e-b1aea9d8fc233123.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-26T17:59:29Z"
      message: 'load-balancer-api-internal: tcp connection to abb5bbada1b2c444c949f30b853b969e-b1aea9d8fc233123.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.183839ms
      message: 'load-balancer-api-internal: tcp connection to abb5bbada1b2c444c949f30b853b969e-b1aea9d8fc233123.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T18:41:29Z"
    - latency: 8.74875ms
      message: 'load-balancer-api-internal: resolved host name abb5bbada1b2c444c949f30b853b969e-b1aea9d8fc233123.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-26T18:41:29Z"
    - latency: 3.268034ms
      message: 'load-balancer-api-internal: tcp connection to abb5bbada1b2c444c949f30b853b969e-b1aea9d8fc233123.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T18:40:29Z"
    - latency: 8.025401ms
      message: 'load-balancer-api-internal: resolved host name abb5bbada1b2c444c949f30b853b969e-b1aea9d8fc233123.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-26T18:40:29Z"
    - latency: 5.325689ms
      message: 'load-balancer-api-internal: tcp connection to abb5bbada1b2c444c949f30b853b969e-b1aea9d8fc233123.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T18:39:29Z"
    - latency: 6.901831ms
      message: 'load-balancer-api-internal: resolved host name abb5bbada1b2c444c949f30b853b969e-b1aea9d8fc233123.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-26T18:39:29Z"
    - latency: 5.804367ms
      message: 'load-balancer-api-internal: tcp connection to abb5bbada1b2c444c949f30b853b969e-b1aea9d8fc233123.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T18:38:29Z"
    - latency: 9.079866ms
      message: 'load-balancer-api-internal: resolved host name abb5bbada1b2c444c949f30b853b969e-b1aea9d8fc233123.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-26T18:38:29Z"
    - latency: 5.013166ms
      message: 'load-balancer-api-internal: tcp connection to abb5bbada1b2c444c949f30b853b969e-b1aea9d8fc233123.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T18:37:29Z"
    - latency: 8.540888ms
      message: 'load-balancer-api-internal: resolved host name abb5bbada1b2c444c949f30b853b969e-b1aea9d8fc233123.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-26T18:37:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-26T17:53:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-45-to-network-check-target-ip-10-0-128-209
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-45.ec2.internal
      uid: 7e0dd6bc-cedd-4d84-af98-b80a12b85b2c
    resourceVersion: "70820"
    uid: 079475e0-e657-436e-9456-93e483392d09
  spec:
    sourcePod: network-check-source-7d88cb55d8-z2knl
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-26T18:00:29Z"
      message: 'network-check-target-ip-10-0-128-209: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.640755ms
      message: 'network-check-target-ip-10-0-128-209: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T18:42:29Z"
    - latency: 2.680091ms
      message: 'network-check-target-ip-10-0-128-209: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T18:41:29Z"
    - latency: 2.369325ms
      message: 'network-check-target-ip-10-0-128-209: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T18:40:29Z"
    - latency: 2.253754ms
      message: 'network-check-target-ip-10-0-128-209: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T18:39:29Z"
    - latency: 2.032532ms
      message: 'network-check-target-ip-10-0-128-209: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T18:38:29Z"
    - latency: 2.124137ms
      message: 'network-check-target-ip-10-0-128-209: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T18:37:29Z"
    - latency: 2.364727ms
      message: 'network-check-target-ip-10-0-128-209: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T18:36:29Z"
    - latency: 2.263766ms
      message: 'network-check-target-ip-10-0-128-209: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T18:35:29Z"
    - latency: 2.195009ms
      message: 'network-check-target-ip-10-0-128-209: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T18:34:29Z"
    - latency: 2.264687ms
      message: 'network-check-target-ip-10-0-128-209: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T18:33:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-26T17:53:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-45-to-network-check-target-ip-10-0-128-45
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-45.ec2.internal
      uid: 7e0dd6bc-cedd-4d84-af98-b80a12b85b2c
    resourceVersion: "70818"
    uid: 8eedd46a-813a-4fb1-8b98-d7b392fb6a24
  spec:
    sourcePod: network-check-source-7d88cb55d8-z2knl
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-26T18:00:29Z"
      message: 'network-check-target-ip-10-0-128-45: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.186052ms
      message: 'network-check-target-ip-10-0-128-45: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T18:42:29Z"
    - latency: 1.134302ms
      message: 'network-check-target-ip-10-0-128-45: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T18:41:29Z"
    - latency: 1.021449ms
      message: 'network-check-target-ip-10-0-128-45: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T18:40:29Z"
    - latency: 1.086685ms
      message: 'network-check-target-ip-10-0-128-45: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T18:39:29Z"
    - latency: 1.863111ms
      message: 'network-check-target-ip-10-0-128-45: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T18:38:29Z"
    - latency: 1.218897ms
      message: 'network-check-target-ip-10-0-128-45: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T18:37:29Z"
    - latency: 1.769466ms
      message: 'network-check-target-ip-10-0-128-45: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T18:36:29Z"
    - latency: 1.160432ms
      message: 'network-check-target-ip-10-0-128-45: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T18:35:29Z"
    - latency: 968.557µs
      message: 'network-check-target-ip-10-0-128-45: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T18:34:29Z"
    - latency: 1.764078ms
      message: 'network-check-target-ip-10-0-128-45: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T18:33:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-26T17:53:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-45-to-network-check-target-ip-10-0-138-219
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-45.ec2.internal
      uid: 7e0dd6bc-cedd-4d84-af98-b80a12b85b2c
    resourceVersion: "70819"
    uid: 34860303-6a7b-4d62-8acb-26df7bb2edc4
  spec:
    sourcePod: network-check-source-7d88cb55d8-z2knl
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-26T18:00:29Z"
      message: 'network-check-target-ip-10-0-138-219: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.161557ms
      message: 'network-check-target-ip-10-0-138-219: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T18:42:29Z"
    - latency: 2.350908ms
      message: 'network-check-target-ip-10-0-138-219: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T18:41:29Z"
    - latency: 2.515327ms
      message: 'network-check-target-ip-10-0-138-219: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T18:40:29Z"
    - latency: 2.286034ms
      message: 'network-check-target-ip-10-0-138-219: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T18:39:29Z"
    - latency: 2.297448ms
      message: 'network-check-target-ip-10-0-138-219: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T18:38:29Z"
    - latency: 2.187766ms
      message: 'network-check-target-ip-10-0-138-219: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T18:37:29Z"
    - latency: 2.453003ms
      message: 'network-check-target-ip-10-0-138-219: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T18:36:29Z"
    - latency: 2.293444ms
      message: 'network-check-target-ip-10-0-138-219: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T18:35:29Z"
    - latency: 2.426629ms
      message: 'network-check-target-ip-10-0-138-219: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T18:34:29Z"
    - latency: 2.388872ms
      message: 'network-check-target-ip-10-0-138-219: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T18:33:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-26T17:53:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-45-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-45.ec2.internal
      uid: 7e0dd6bc-cedd-4d84-af98-b80a12b85b2c
    resourceVersion: "69668"
    uid: 52d6b81b-b96e-4eb2-bdd9-d7ce46cce88f
  spec:
    sourcePod: network-check-source-7d88cb55d8-z2knl
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-26T17:59:29Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.06408ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T18:41:29Z"
    - latency: 2.793781ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-26T18:41:29Z"
    - latency: 1.390733ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T18:40:29Z"
    - latency: 1.947472ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-26T18:40:29Z"
    - latency: 994.374µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T18:39:29Z"
    - latency: 1.727029ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-26T18:39:29Z"
    - latency: 1.056374ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T18:38:29Z"
    - latency: 2.172439ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-26T18:38:29Z"
    - latency: 1.113188ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T18:37:29Z"
    - latency: 2.140164ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-26T18:37:29Z"
kind: List
metadata:
  resourceVersion: ""