apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-29T17:00:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-169-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-169.ec2.internal
      uid: e95db708-b04b-431c-8d6f-d75c5ed27ec9
    resourceVersion: "45685"
    uid: ff9e7657-8572-4081-8401-4071a4770540
  spec:
    sourcePod: network-check-source-56d84b9f44-b5nnj
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-05-29T17:07:20Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 870.252µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T17:28:20Z"
    - latency: 1.202964ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T17:27:20Z"
    - latency: 1.181256ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T17:26:20Z"
    - latency: 845.584µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T17:25:20Z"
    - latency: 769.808µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T17:24:20Z"
    - latency: 1.080457ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T17:23:20Z"
    - latency: 1.073745ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T17:22:20Z"
    - latency: 1.704029ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T17:21:20Z"
    - latency: 1.136042ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T17:20:20Z"
    - latency: 1.080811ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T17:19:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-29T17:00:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-169-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-169.ec2.internal
      uid: e95db708-b04b-431c-8d6f-d75c5ed27ec9
    resourceVersion: "47796"
    uid: ecdafa47-17ee-4ce4-b670-f4bef7147497
  spec:
    sourcePod: network-check-source-56d84b9f44-b5nnj
    targetEndpoint: a18f2904f29a54084b5d87744116ca42-3e840008b3611567.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-05-29T17:06:20Z"
      message: 'load-balancer-api-external: tcp connection to a18f2904f29a54084b5d87744116ca42-3e840008b3611567.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.502074ms
      message: 'load-balancer-api-external: tcp connection to a18f2904f29a54084b5d87744116ca42-3e840008b3611567.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T17:30:20Z"
    - latency: 8.07899ms
      message: 'load-balancer-api-external: resolved host name a18f2904f29a54084b5d87744116ca42-3e840008b3611567.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-29T17:30:20Z"
    - latency: 4.32856ms
      message: 'load-balancer-api-external: tcp connection to a18f2904f29a54084b5d87744116ca42-3e840008b3611567.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T17:29:20Z"
    - latency: 15.117947ms
      message: 'load-balancer-api-external: resolved host name a18f2904f29a54084b5d87744116ca42-3e840008b3611567.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-29T17:29:20Z"
    - latency: 6.097451ms
      message: 'load-balancer-api-external: tcp connection to a18f2904f29a54084b5d87744116ca42-3e840008b3611567.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T17:28:20Z"
    - latency: 7.643028ms
      message: 'load-balancer-api-external: resolved host name a18f2904f29a54084b5d87744116ca42-3e840008b3611567.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-29T17:28:20Z"
    - latency: 4.864899ms
      message: 'load-balancer-api-external: tcp connection to a18f2904f29a54084b5d87744116ca42-3e840008b3611567.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T17:27:20Z"
    - latency: 8.713784ms
      message: 'load-balancer-api-external: resolved host name a18f2904f29a54084b5d87744116ca42-3e840008b3611567.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-29T17:27:20Z"
    - latency: 2.878064ms
      message: 'load-balancer-api-external: tcp connection to a18f2904f29a54084b5d87744116ca42-3e840008b3611567.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T17:26:20Z"
    - latency: 7.349303ms
      message: 'load-balancer-api-external: resolved host name a18f2904f29a54084b5d87744116ca42-3e840008b3611567.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-29T17:26:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-29T17:00:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-169-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-169.ec2.internal
      uid: e95db708-b04b-431c-8d6f-d75c5ed27ec9
    resourceVersion: "47795"
    uid: ffe9761f-78bb-445c-8c28-0e8bcdb98176
  spec:
    sourcePod: network-check-source-56d84b9f44-b5nnj
    targetEndpoint: a18f2904f29a54084b5d87744116ca42-3e840008b3611567.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-05-29T17:06:20Z"
      message: 'load-balancer-api-internal: tcp connection to a18f2904f29a54084b5d87744116ca42-3e840008b3611567.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.495681ms
      message: 'load-balancer-api-internal: tcp connection to a18f2904f29a54084b5d87744116ca42-3e840008b3611567.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T17:30:20Z"
    - latency: 8.108802ms
      message: 'load-balancer-api-internal: resolved host name a18f2904f29a54084b5d87744116ca42-3e840008b3611567.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-29T17:30:20Z"
    - latency: 4.296898ms
      message: 'load-balancer-api-internal: tcp connection to a18f2904f29a54084b5d87744116ca42-3e840008b3611567.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T17:29:20Z"
    - latency: 15.156822ms
      message: 'load-balancer-api-internal: resolved host name a18f2904f29a54084b5d87744116ca42-3e840008b3611567.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-29T17:29:20Z"
    - latency: 4.039434ms
      message: 'load-balancer-api-internal: tcp connection to a18f2904f29a54084b5d87744116ca42-3e840008b3611567.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T17:28:20Z"
    - latency: 7.564608ms
      message: 'load-balancer-api-internal: resolved host name a18f2904f29a54084b5d87744116ca42-3e840008b3611567.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-29T17:28:20Z"
    - latency: 4.90107ms
      message: 'load-balancer-api-internal: tcp connection to a18f2904f29a54084b5d87744116ca42-3e840008b3611567.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T17:27:20Z"
    - latency: 8.767783ms
      message: 'load-balancer-api-internal: resolved host name a18f2904f29a54084b5d87744116ca42-3e840008b3611567.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-29T17:27:20Z"
    - latency: 3.974034ms
      message: 'load-balancer-api-internal: tcp connection to a18f2904f29a54084b5d87744116ca42-3e840008b3611567.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T17:26:20Z"
    - latency: 7.251532ms
      message: 'load-balancer-api-internal: resolved host name a18f2904f29a54084b5d87744116ca42-3e840008b3611567.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-29T17:26:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-29T17:00:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-169-to-network-check-target-ip-10-0-128-169
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-169.ec2.internal
      uid: e95db708-b04b-431c-8d6f-d75c5ed27ec9
    resourceVersion: "45683"
    uid: 281e5087-e251-4020-8c59-bc28c62409d8
  spec:
    sourcePod: network-check-source-56d84b9f44-b5nnj
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-05-29T17:07:20Z"
      message: 'network-check-target-ip-10-0-128-169: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 873.245µs
      message: 'network-check-target-ip-10-0-128-169: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T17:28:20Z"
    - latency: 956.354µs
      message: 'network-check-target-ip-10-0-128-169: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T17:27:20Z"
    - latency: 1.184781ms
      message: 'network-check-target-ip-10-0-128-169: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T17:26:20Z"
    - latency: 812.499µs
      message: 'network-check-target-ip-10-0-128-169: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T17:25:20Z"
    - latency: 1.448833ms
      message: 'network-check-target-ip-10-0-128-169: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T17:24:20Z"
    - latency: 1.259248ms
      message: 'network-check-target-ip-10-0-128-169: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T17:23:20Z"
    - latency: 837.246µs
      message: 'network-check-target-ip-10-0-128-169: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T17:22:20Z"
    - latency: 822.603µs
      message: 'network-check-target-ip-10-0-128-169: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T17:21:20Z"
    - latency: 1.209266ms
      message: 'network-check-target-ip-10-0-128-169: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T17:20:20Z"
    - latency: 786.066µs
      message: 'network-check-target-ip-10-0-128-169: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T17:19:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-29T17:00:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-169-to-network-check-target-ip-10-0-137-133
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-169.ec2.internal
      uid: e95db708-b04b-431c-8d6f-d75c5ed27ec9
    resourceVersion: "45684"
    uid: fbe9f0e7-8dea-41c6-8a1c-73b1c6683e4e
  spec:
    sourcePod: network-check-source-56d84b9f44-b5nnj
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-05-29T17:07:20Z"
      message: 'network-check-target-ip-10-0-137-133: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.126988ms
      message: 'network-check-target-ip-10-0-137-133: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T17:28:20Z"
    - latency: 2.11927ms
      message: 'network-check-target-ip-10-0-137-133: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T17:27:20Z"
    - latency: 2.09055ms
      message: 'network-check-target-ip-10-0-137-133: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T17:26:20Z"
    - latency: 2.280323ms
      message: 'network-check-target-ip-10-0-137-133: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T17:25:20Z"
    - latency: 2.551175ms
      message: 'network-check-target-ip-10-0-137-133: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T17:24:20Z"
    - latency: 2.196872ms
      message: 'network-check-target-ip-10-0-137-133: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T17:23:20Z"
    - latency: 2.302583ms
      message: 'network-check-target-ip-10-0-137-133: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T17:22:20Z"
    - latency: 2.459963ms
      message: 'network-check-target-ip-10-0-137-133: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T17:21:20Z"
    - latency: 2.17312ms
      message: 'network-check-target-ip-10-0-137-133: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T17:20:20Z"
    - latency: 2.304516ms
      message: 'network-check-target-ip-10-0-137-133: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T17:19:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-29T17:00:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-169-to-network-check-target-ip-10-0-141-197
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-169.ec2.internal
      uid: e95db708-b04b-431c-8d6f-d75c5ed27ec9
    resourceVersion: "45686"
    uid: fa66c0b6-0def-47dc-8b91-ade6af99d5c8
  spec:
    sourcePod: network-check-source-56d84b9f44-b5nnj
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-05-29T17:07:20Z"
      message: 'network-check-target-ip-10-0-141-197: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.028156ms
      message: 'network-check-target-ip-10-0-141-197: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T17:28:20Z"
    - latency: 2.051903ms
      message: 'network-check-target-ip-10-0-141-197: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T17:27:20Z"
    - latency: 1.918956ms
      message: 'network-check-target-ip-10-0-141-197: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T17:26:20Z"
    - latency: 1.72526ms
      message: 'network-check-target-ip-10-0-141-197: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T17:25:20Z"
    - latency: 1.956988ms
      message: 'network-check-target-ip-10-0-141-197: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T17:24:20Z"
    - latency: 1.993731ms
      message: 'network-check-target-ip-10-0-141-197: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T17:23:20Z"
    - latency: 1.804501ms
      message: 'network-check-target-ip-10-0-141-197: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T17:22:20Z"
    - latency: 2.09283ms
      message: 'network-check-target-ip-10-0-141-197: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T17:21:20Z"
    - latency: 2.411751ms
      message: 'network-check-target-ip-10-0-141-197: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T17:20:20Z"
    - latency: 2.06186ms
      message: 'network-check-target-ip-10-0-141-197: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T17:19:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-29T17:00:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-169-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-169.ec2.internal
      uid: e95db708-b04b-431c-8d6f-d75c5ed27ec9
    resourceVersion: "47793"
    uid: 4fd0e0fa-f964-4043-83c0-016539037b57
  spec:
    sourcePod: network-check-source-56d84b9f44-b5nnj
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-05-29T17:06:20Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 848.452µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T17:30:20Z"
    - latency: 1.631103ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-29T17:30:20Z"
    - latency: 873.444µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T17:29:20Z"
    - latency: 2.022538ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-29T17:29:20Z"
    - latency: 1.00843ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T17:28:20Z"
    - latency: 1.694396ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-29T17:28:20Z"
    - latency: 887.044µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T17:27:20Z"
    - latency: 1.66477ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-29T17:27:20Z"
    - latency: 896.143µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T17:26:20Z"
    - latency: 1.766214ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-29T17:26:20Z"
kind: List
metadata:
  resourceVersion: ""