apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T02:43:52Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-241-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-241.ec2.internal
      uid: aab5f84b-0122-4dbe-b7aa-db9cc1dbcb7c
    resourceVersion: "51790"
    uid: b34ab2af-1557-48c1-893e-9e54ad75e25c
  spec:
    sourcePod: network-check-source-6f78d59f99-7hpk4
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T02:50:53Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.035114ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:14:53Z"
    - latency: 886.993µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:13:53Z"
    - latency: 1.090137ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:12:53Z"
    - latency: 1.118512ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:11:53Z"
    - latency: 1.535ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:10:53Z"
    - latency: 795.799µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:09:53Z"
    - latency: 1.208581ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:08:53Z"
    - latency: 956.554µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:07:53Z"
    - latency: 1.030796ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:06:53Z"
    - latency: 946.846µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:05:53Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T02:43:52Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-241-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-241.ec2.internal
      uid: aab5f84b-0122-4dbe-b7aa-db9cc1dbcb7c
    resourceVersion: "49992"
    uid: f4a4ec05-1321-4776-9a05-162e02ddc2f9
  spec:
    sourcePod: network-check-source-6f78d59f99-7hpk4
    targetEndpoint: a65c893e2a21041a6953366d999e3f3d-6f9d0911bc47b10c.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T02:49:53Z"
      message: 'load-balancer-api-external: tcp connection to a65c893e2a21041a6953366d999e3f3d-6f9d0911bc47b10c.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 17.265905ms
      message: 'load-balancer-api-external: tcp connection to a65c893e2a21041a6953366d999e3f3d-6f9d0911bc47b10c.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:13:53Z"
    - latency: 8.738706ms
      message: 'load-balancer-api-external: resolved host name a65c893e2a21041a6953366d999e3f3d-6f9d0911bc47b10c.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T04:13:53Z"
    - latency: 17.845007ms
      message: 'load-balancer-api-external: tcp connection to a65c893e2a21041a6953366d999e3f3d-6f9d0911bc47b10c.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:12:53Z"
    - latency: 8.214433ms
      message: 'load-balancer-api-external: resolved host name a65c893e2a21041a6953366d999e3f3d-6f9d0911bc47b10c.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T04:12:53Z"
    - latency: 18.460405ms
      message: 'load-balancer-api-external: tcp connection to a65c893e2a21041a6953366d999e3f3d-6f9d0911bc47b10c.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:11:53Z"
    - latency: 6.591215ms
      message: 'load-balancer-api-external: resolved host name a65c893e2a21041a6953366d999e3f3d-6f9d0911bc47b10c.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T04:11:53Z"
    - latency: 16.529833ms
      message: 'load-balancer-api-external: tcp connection to a65c893e2a21041a6953366d999e3f3d-6f9d0911bc47b10c.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:10:53Z"
    - latency: 9.027272ms
      message: 'load-balancer-api-external: resolved host name a65c893e2a21041a6953366d999e3f3d-6f9d0911bc47b10c.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T04:10:53Z"
    - latency: 15.699324ms
      message: 'load-balancer-api-external: tcp connection to a65c893e2a21041a6953366d999e3f3d-6f9d0911bc47b10c.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:09:53Z"
    - latency: 9.499157ms
      message: 'load-balancer-api-external: resolved host name a65c893e2a21041a6953366d999e3f3d-6f9d0911bc47b10c.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T04:09:53Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T02:43:52Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-241-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-241.ec2.internal
      uid: aab5f84b-0122-4dbe-b7aa-db9cc1dbcb7c
    resourceVersion: "49991"
    uid: fece38e6-6fd6-4729-bc21-9c4de4b1cc72
  spec:
    sourcePod: network-check-source-6f78d59f99-7hpk4
    targetEndpoint: a65c893e2a21041a6953366d999e3f3d-6f9d0911bc47b10c.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T02:49:53Z"
      message: 'load-balancer-api-internal: tcp connection to a65c893e2a21041a6953366d999e3f3d-6f9d0911bc47b10c.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 15.415354ms
      message: 'load-balancer-api-internal: tcp connection to a65c893e2a21041a6953366d999e3f3d-6f9d0911bc47b10c.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:13:53Z"
    - latency: 8.780168ms
      message: 'load-balancer-api-internal: resolved host name a65c893e2a21041a6953366d999e3f3d-6f9d0911bc47b10c.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T04:13:53Z"
    - latency: 21.340327ms
      message: 'load-balancer-api-internal: tcp connection to a65c893e2a21041a6953366d999e3f3d-6f9d0911bc47b10c.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:12:53Z"
    - latency: 8.281918ms
      message: 'load-balancer-api-internal: resolved host name a65c893e2a21041a6953366d999e3f3d-6f9d0911bc47b10c.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T04:12:53Z"
    - latency: 17.318383ms
      message: 'load-balancer-api-internal: tcp connection to a65c893e2a21041a6953366d999e3f3d-6f9d0911bc47b10c.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:11:53Z"
    - latency: 6.550672ms
      message: 'load-balancer-api-internal: resolved host name a65c893e2a21041a6953366d999e3f3d-6f9d0911bc47b10c.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T04:11:53Z"
    - latency: 16.426962ms
      message: 'load-balancer-api-internal: tcp connection to a65c893e2a21041a6953366d999e3f3d-6f9d0911bc47b10c.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:10:53Z"
    - latency: 9.101664ms
      message: 'load-balancer-api-internal: resolved host name a65c893e2a21041a6953366d999e3f3d-6f9d0911bc47b10c.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T04:10:53Z"
    - latency: 14.952072ms
      message: 'load-balancer-api-internal: tcp connection to a65c893e2a21041a6953366d999e3f3d-6f9d0911bc47b10c.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:09:53Z"
    - latency: 9.688727ms
      message: 'load-balancer-api-internal: resolved host name a65c893e2a21041a6953366d999e3f3d-6f9d0911bc47b10c.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T04:09:53Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T02:43:52Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-241-to-network-check-target-ip-10-0-128-202
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-241.ec2.internal
      uid: aab5f84b-0122-4dbe-b7aa-db9cc1dbcb7c
    resourceVersion: "51789"
    uid: d0e74a4a-f0ca-4924-8af5-9be88bcd6df0
  spec:
    sourcePod: network-check-source-6f78d59f99-7hpk4
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T02:50:53Z"
      message: 'network-check-target-ip-10-0-128-202: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.125926ms
      message: 'network-check-target-ip-10-0-128-202: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:14:53Z"
    - latency: 2.320551ms
      message: 'network-check-target-ip-10-0-128-202: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:13:53Z"
    - latency: 1.813859ms
      message: 'network-check-target-ip-10-0-128-202: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:12:53Z"
    - latency: 2.102882ms
      message: 'network-check-target-ip-10-0-128-202: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:11:53Z"
    - latency: 1.951112ms
      message: 'network-check-target-ip-10-0-128-202: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:10:53Z"
    - latency: 1.752282ms
      message: 'network-check-target-ip-10-0-128-202: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:09:53Z"
    - latency: 1.928932ms
      message: 'network-check-target-ip-10-0-128-202: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:08:53Z"
    - latency: 2.241668ms
      message: 'network-check-target-ip-10-0-128-202: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:07:53Z"
    - latency: 1.723507ms
      message: 'network-check-target-ip-10-0-128-202: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:06:53Z"
    - latency: 1.886598ms
      message: 'network-check-target-ip-10-0-128-202: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:05:53Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T02:43:53Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-241-to-network-check-target-ip-10-0-128-241
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-241.ec2.internal
      uid: aab5f84b-0122-4dbe-b7aa-db9cc1dbcb7c
    resourceVersion: "51788"
    uid: 1e3e97d5-5c22-4f3e-a6c3-1da23e65fd74
  spec:
    sourcePod: network-check-source-6f78d59f99-7hpk4
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T02:50:53Z"
      message: 'network-check-target-ip-10-0-128-241: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.299093ms
      message: 'network-check-target-ip-10-0-128-241: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:14:53Z"
    - latency: 983.462µs
      message: 'network-check-target-ip-10-0-128-241: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:13:53Z"
    - latency: 897.332µs
      message: 'network-check-target-ip-10-0-128-241: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:12:53Z"
    - latency: 1.62806ms
      message: 'network-check-target-ip-10-0-128-241: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:11:53Z"
    - latency: 877.219µs
      message: 'network-check-target-ip-10-0-128-241: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:10:53Z"
    - latency: 846.145µs
      message: 'network-check-target-ip-10-0-128-241: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:09:53Z"
    - latency: 1.523405ms
      message: 'network-check-target-ip-10-0-128-241: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:08:53Z"
    - latency: 1.097478ms
      message: 'network-check-target-ip-10-0-128-241: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:07:53Z"
    - latency: 712.118µs
      message: 'network-check-target-ip-10-0-128-241: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:06:53Z"
    - latency: 837.756µs
      message: 'network-check-target-ip-10-0-128-241: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:05:53Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T02:43:52Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-241-to-network-check-target-ip-10-0-133-197
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-241.ec2.internal
      uid: aab5f84b-0122-4dbe-b7aa-db9cc1dbcb7c
    resourceVersion: "51787"
    uid: 5eb3af2d-4667-43d6-b2ae-2452a5dc8ca5
  spec:
    sourcePod: network-check-source-6f78d59f99-7hpk4
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T02:50:53Z"
      message: 'network-check-target-ip-10-0-133-197: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.154496ms
      message: 'network-check-target-ip-10-0-133-197: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:14:53Z"
    - latency: 2.226139ms
      message: 'network-check-target-ip-10-0-133-197: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:13:53Z"
    - latency: 2.028102ms
      message: 'network-check-target-ip-10-0-133-197: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:12:53Z"
    - latency: 2.235725ms
      message: 'network-check-target-ip-10-0-133-197: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:11:53Z"
    - latency: 2.216622ms
      message: 'network-check-target-ip-10-0-133-197: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:10:53Z"
    - latency: 2.357098ms
      message: 'network-check-target-ip-10-0-133-197: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:09:53Z"
    - latency: 2.164511ms
      message: 'network-check-target-ip-10-0-133-197: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:08:53Z"
    - latency: 2.274917ms
      message: 'network-check-target-ip-10-0-133-197: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:07:53Z"
    - latency: 1.790165ms
      message: 'network-check-target-ip-10-0-133-197: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:06:53Z"
    - latency: 2.043299ms
      message: 'network-check-target-ip-10-0-133-197: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:05:53Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T02:43:52Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-241-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-241.ec2.internal
      uid: aab5f84b-0122-4dbe-b7aa-db9cc1dbcb7c
    resourceVersion: "49990"
    uid: 1e38b20f-f845-4212-9ff5-003dd144ba66
  spec:
    sourcePod: network-check-source-6f78d59f99-7hpk4
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T02:49:53Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.149342ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:13:53Z"
    - latency: 2.17872ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T04:13:53Z"
    - latency: 1.222813ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:12:53Z"
    - latency: 1.690846ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T04:12:53Z"
    - latency: 1.240158ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:11:53Z"
    - latency: 1.779523ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T04:11:53Z"
    - latency: 1.021939ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:10:53Z"
    - latency: 1.944952ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T04:10:53Z"
    - latency: 799.403µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:09:53Z"
    - latency: 2.286399ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T04:09:53Z"
kind: List
metadata:
  resourceVersion: ""