apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T19:49:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-173-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-173.ec2.internal
      uid: fdea857a-cd3c-45f8-a55a-6744772e84c0
    resourceVersion: "59526"
    uid: fe00d49d-05e1-4e7c-8e4b-3f3f86557bcd
  spec:
    sourcePod: network-check-source-6f78d59f99-k8mq4
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T19:56:33Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.324276ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:17:33Z"
    - latency: 1.017986ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:16:33Z"
    - latency: 1.241515ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:15:33Z"
    - latency: 1.006451ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:14:33Z"
    - latency: 1.260625ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:13:33Z"
    - latency: 3.697385ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:12:33Z"
    - latency: 2.360756ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:11:33Z"
    - latency: 1.292728ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:10:33Z"
    - latency: 3.817157ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:09:33Z"
    - latency: 1.258594ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:08:33Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T19:49:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-173-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-173.ec2.internal
      uid: fdea857a-cd3c-45f8-a55a-6744772e84c0
    resourceVersion: "62630"
    uid: 0fbf98e5-95ca-4c43-a233-1d7d0ed82dc7
  spec:
    sourcePod: network-check-source-6f78d59f99-k8mq4
    targetEndpoint: ab962f218708a4a3a94563c5003e2683-35dcd4391a080576.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T19:55:33Z"
      message: 'load-balancer-api-external: tcp connection to ab962f218708a4a3a94563c5003e2683-35dcd4391a080576.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 17.861853ms
      message: 'load-balancer-api-external: tcp connection to ab962f218708a4a3a94563c5003e2683-35dcd4391a080576.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:19:33Z"
    - latency: 7.157522ms
      message: 'load-balancer-api-external: resolved host name ab962f218708a4a3a94563c5003e2683-35dcd4391a080576.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T20:19:33Z"
    - latency: 16.802984ms
      message: 'load-balancer-api-external: tcp connection to ab962f218708a4a3a94563c5003e2683-35dcd4391a080576.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:18:33Z"
    - latency: 7.291174ms
      message: 'load-balancer-api-external: resolved host name ab962f218708a4a3a94563c5003e2683-35dcd4391a080576.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T20:18:33Z"
    - latency: 23.652ms
      message: 'load-balancer-api-external: tcp connection to ab962f218708a4a3a94563c5003e2683-35dcd4391a080576.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:17:33Z"
    - latency: 6.301846ms
      message: 'load-balancer-api-external: resolved host name ab962f218708a4a3a94563c5003e2683-35dcd4391a080576.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T20:17:33Z"
    - latency: 14.923352ms
      message: 'load-balancer-api-external: tcp connection to ab962f218708a4a3a94563c5003e2683-35dcd4391a080576.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:16:33Z"
    - latency: 7.250574ms
      message: 'load-balancer-api-external: resolved host name ab962f218708a4a3a94563c5003e2683-35dcd4391a080576.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T20:16:33Z"
    - latency: 17.266343ms
      message: 'load-balancer-api-external: tcp connection to ab962f218708a4a3a94563c5003e2683-35dcd4391a080576.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:15:33Z"
    - latency: 6.825834ms
      message: 'load-balancer-api-external: resolved host name ab962f218708a4a3a94563c5003e2683-35dcd4391a080576.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T20:15:33Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T19:49:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-173-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-173.ec2.internal
      uid: fdea857a-cd3c-45f8-a55a-6744772e84c0
    resourceVersion: "62631"
    uid: b943ff64-5489-4c89-8420-f8e9690b9fd7
  spec:
    sourcePod: network-check-source-6f78d59f99-k8mq4
    targetEndpoint: ab962f218708a4a3a94563c5003e2683-35dcd4391a080576.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T19:55:33Z"
      message: 'load-balancer-api-internal: tcp connection to ab962f218708a4a3a94563c5003e2683-35dcd4391a080576.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 18.632982ms
      message: 'load-balancer-api-internal: tcp connection to ab962f218708a4a3a94563c5003e2683-35dcd4391a080576.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:19:33Z"
    - latency: 7.192077ms
      message: 'load-balancer-api-internal: resolved host name ab962f218708a4a3a94563c5003e2683-35dcd4391a080576.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T20:19:33Z"
    - latency: 16.300333ms
      message: 'load-balancer-api-internal: tcp connection to ab962f218708a4a3a94563c5003e2683-35dcd4391a080576.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:18:33Z"
    - latency: 7.320231ms
      message: 'load-balancer-api-internal: resolved host name ab962f218708a4a3a94563c5003e2683-35dcd4391a080576.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T20:18:33Z"
    - latency: 17.384726ms
      message: 'load-balancer-api-internal: tcp connection to ab962f218708a4a3a94563c5003e2683-35dcd4391a080576.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:17:33Z"
    - latency: 6.382709ms
      message: 'load-balancer-api-internal: resolved host name ab962f218708a4a3a94563c5003e2683-35dcd4391a080576.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T20:17:33Z"
    - latency: 17.335757ms
      message: 'load-balancer-api-internal: tcp connection to ab962f218708a4a3a94563c5003e2683-35dcd4391a080576.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:16:33Z"
    - latency: 7.126398ms
      message: 'load-balancer-api-internal: resolved host name ab962f218708a4a3a94563c5003e2683-35dcd4391a080576.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T20:16:33Z"
    - latency: 17.311292ms
      message: 'load-balancer-api-internal: tcp connection to ab962f218708a4a3a94563c5003e2683-35dcd4391a080576.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:15:33Z"
    - latency: 6.718268ms
      message: 'load-balancer-api-internal: resolved host name ab962f218708a4a3a94563c5003e2683-35dcd4391a080576.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T20:15:33Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T19:49:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-173-to-network-check-target-ip-10-0-131-26
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-173.ec2.internal
      uid: fdea857a-cd3c-45f8-a55a-6744772e84c0
    resourceVersion: "59523"
    uid: 15a2f0a8-a0e8-4108-b590-13da75caba20
  spec:
    sourcePod: network-check-source-6f78d59f99-k8mq4
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T19:56:33Z"
      message: 'network-check-target-ip-10-0-131-26: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.354359ms
      message: 'network-check-target-ip-10-0-131-26: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:17:33Z"
    - latency: 2.756867ms
      message: 'network-check-target-ip-10-0-131-26: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:16:33Z"
    - latency: 2.147508ms
      message: 'network-check-target-ip-10-0-131-26: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:15:33Z"
    - latency: 2.173225ms
      message: 'network-check-target-ip-10-0-131-26: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:14:33Z"
    - latency: 2.269791ms
      message: 'network-check-target-ip-10-0-131-26: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:13:33Z"
    - latency: 15.979443ms
      message: 'network-check-target-ip-10-0-131-26: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:12:33Z"
    - latency: 3.320872ms
      message: 'network-check-target-ip-10-0-131-26: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:11:33Z"
    - latency: 2.475976ms
      message: 'network-check-target-ip-10-0-131-26: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:10:33Z"
    - latency: 4.612519ms
      message: 'network-check-target-ip-10-0-131-26: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:09:33Z"
    - latency: 2.933531ms
      message: 'network-check-target-ip-10-0-131-26: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:08:33Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T19:49:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-173-to-network-check-target-ip-10-0-132-173
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-173.ec2.internal
      uid: fdea857a-cd3c-45f8-a55a-6744772e84c0
    resourceVersion: "59522"
    uid: c00da65e-7d64-4a5e-bfc4-4e792a57af3b
  spec:
    sourcePod: network-check-source-6f78d59f99-k8mq4
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T19:56:33Z"
      message: 'network-check-target-ip-10-0-132-173: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 898.473µs
      message: 'network-check-target-ip-10-0-132-173: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:17:33Z"
    - latency: 1.077003ms
      message: 'network-check-target-ip-10-0-132-173: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:16:33Z"
    - latency: 945.609µs
      message: 'network-check-target-ip-10-0-132-173: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:15:33Z"
    - latency: 768.15µs
      message: 'network-check-target-ip-10-0-132-173: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:14:33Z"
    - latency: 1.50928ms
      message: 'network-check-target-ip-10-0-132-173: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:13:33Z"
    - latency: 22.256ms
      message: 'network-check-target-ip-10-0-132-173: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:12:33Z"
    - latency: 1.708003ms
      message: 'network-check-target-ip-10-0-132-173: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:11:33Z"
    - latency: 887.152µs
      message: 'network-check-target-ip-10-0-132-173: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:10:33Z"
    - latency: 5.555366ms
      message: 'network-check-target-ip-10-0-132-173: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:09:33Z"
    - latency: 1.374605ms
      message: 'network-check-target-ip-10-0-132-173: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:08:33Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T19:49:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-173-to-network-check-target-ip-10-0-142-168
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-173.ec2.internal
      uid: fdea857a-cd3c-45f8-a55a-6744772e84c0
    resourceVersion: "59524"
    uid: 3d010ae9-66d3-4821-9227-34930d6cbbd4
  spec:
    sourcePod: network-check-source-6f78d59f99-k8mq4
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T19:56:33Z"
      message: 'network-check-target-ip-10-0-142-168: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.528669ms
      message: 'network-check-target-ip-10-0-142-168: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:17:33Z"
    - latency: 2.276378ms
      message: 'network-check-target-ip-10-0-142-168: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:16:33Z"
    - latency: 2.657175ms
      message: 'network-check-target-ip-10-0-142-168: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:15:33Z"
    - latency: 2.689889ms
      message: 'network-check-target-ip-10-0-142-168: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:14:33Z"
    - latency: 2.890542ms
      message: 'network-check-target-ip-10-0-142-168: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:13:33Z"
    - latency: 33.133396ms
      message: 'network-check-target-ip-10-0-142-168: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:12:33Z"
    - latency: 3.257728ms
      message: 'network-check-target-ip-10-0-142-168: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:11:33Z"
    - latency: 2.8173ms
      message: 'network-check-target-ip-10-0-142-168: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:10:33Z"
    - latency: 9.860028ms
      message: 'network-check-target-ip-10-0-142-168: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:09:33Z"
    - latency: 2.725491ms
      message: 'network-check-target-ip-10-0-142-168: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:08:33Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T19:49:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-173-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-173.ec2.internal
      uid: fdea857a-cd3c-45f8-a55a-6744772e84c0
    resourceVersion: "62628"
    uid: 61a27081-91e2-4e29-a568-063f020c113f
  spec:
    sourcePod: network-check-source-6f78d59f99-k8mq4
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T19:55:33Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 992.874µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:19:33Z"
    - latency: 2.345901ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T20:19:33Z"
    - latency: 960.812µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:18:33Z"
    - latency: 2.284908ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T20:18:33Z"
    - latency: 909.226µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:17:33Z"
    - latency: 1.745181ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T20:17:33Z"
    - latency: 1.050338ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:16:33Z"
    - latency: 2.287609ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T20:16:33Z"
    - latency: 911.225µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:15:33Z"
    - latency: 1.828369ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T20:15:33Z"
kind: List
metadata:
  resourceVersion: ""