apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T11:26:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-163-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-163.ec2.internal
      uid: a92e93ee-b250-4127-87f5-39bb009dba3a
    resourceVersion: "53462"
    uid: 4c1fdc66-18bc-4191-a098-000aca70a784
  spec:
    sourcePod: network-check-source-685456655f-vhznl
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T11:33:28Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 842.187µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T11:54:28Z"
    - latency: 1.160669ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T11:53:28Z"
    - latency: 993.852µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T11:52:28Z"
    - latency: 904.592µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T11:51:28Z"
    - latency: 1.309692ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T11:50:28Z"
    - latency: 886.721µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T11:49:28Z"
    - latency: 909.107µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T11:48:28Z"
    - latency: 945.519µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T11:47:28Z"
    - latency: 1.213577ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T11:46:28Z"
    - latency: 1.506414ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T11:45:28Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T11:26:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-163-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-163.ec2.internal
      uid: a92e93ee-b250-4127-87f5-39bb009dba3a
    resourceVersion: "55147"
    uid: 1a11dd08-b217-4481-bf13-a321b4b72fe5
  spec:
    sourcePod: network-check-source-685456655f-vhznl
    targetEndpoint: a0ae91481ffa64920893fc5f6e32f5f1-6c0f19f271fc9f0b.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T11:32:28Z"
      message: 'load-balancer-api-external: tcp connection to a0ae91481ffa64920893fc5f6e32f5f1-6c0f19f271fc9f0b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.206855ms
      message: 'load-balancer-api-external: tcp connection to a0ae91481ffa64920893fc5f6e32f5f1-6c0f19f271fc9f0b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T11:56:28Z"
    - latency: 7.776544ms
      message: 'load-balancer-api-external: resolved host name a0ae91481ffa64920893fc5f6e32f5f1-6c0f19f271fc9f0b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T11:56:28Z"
    - latency: 4.605352ms
      message: 'load-balancer-api-external: tcp connection to a0ae91481ffa64920893fc5f6e32f5f1-6c0f19f271fc9f0b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T11:55:28Z"
    - latency: 7.566186ms
      message: 'load-balancer-api-external: resolved host name a0ae91481ffa64920893fc5f6e32f5f1-6c0f19f271fc9f0b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T11:55:28Z"
    - latency: 3.093188ms
      message: 'load-balancer-api-external: tcp connection to a0ae91481ffa64920893fc5f6e32f5f1-6c0f19f271fc9f0b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T11:54:28Z"
    - latency: 7.581394ms
      message: 'load-balancer-api-external: resolved host name a0ae91481ffa64920893fc5f6e32f5f1-6c0f19f271fc9f0b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T11:54:28Z"
    - latency: 4.638929ms
      message: 'load-balancer-api-external: tcp connection to a0ae91481ffa64920893fc5f6e32f5f1-6c0f19f271fc9f0b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T11:53:28Z"
    - latency: 8.619841ms
      message: 'load-balancer-api-external: resolved host name a0ae91481ffa64920893fc5f6e32f5f1-6c0f19f271fc9f0b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T11:53:28Z"
    - latency: 4.801797ms
      message: 'load-balancer-api-external: tcp connection to a0ae91481ffa64920893fc5f6e32f5f1-6c0f19f271fc9f0b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T11:52:28Z"
    - latency: 7.264961ms
      message: 'load-balancer-api-external: resolved host name a0ae91481ffa64920893fc5f6e32f5f1-6c0f19f271fc9f0b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T11:52:28Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T11:26:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-163-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-163.ec2.internal
      uid: a92e93ee-b250-4127-87f5-39bb009dba3a
    resourceVersion: "55146"
    uid: 80a10022-c55b-4d72-a264-01363e140e48
  spec:
    sourcePod: network-check-source-685456655f-vhznl
    targetEndpoint: a0ae91481ffa64920893fc5f6e32f5f1-6c0f19f271fc9f0b.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T11:32:28Z"
      message: 'load-balancer-api-internal: tcp connection to a0ae91481ffa64920893fc5f6e32f5f1-6c0f19f271fc9f0b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.603361ms
      message: 'load-balancer-api-internal: tcp connection to a0ae91481ffa64920893fc5f6e32f5f1-6c0f19f271fc9f0b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T11:56:28Z"
    - latency: 7.872217ms
      message: 'load-balancer-api-internal: resolved host name a0ae91481ffa64920893fc5f6e32f5f1-6c0f19f271fc9f0b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T11:56:28Z"
    - latency: 4.58713ms
      message: 'load-balancer-api-internal: tcp connection to a0ae91481ffa64920893fc5f6e32f5f1-6c0f19f271fc9f0b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T11:55:28Z"
    - latency: 7.612029ms
      message: 'load-balancer-api-internal: resolved host name a0ae91481ffa64920893fc5f6e32f5f1-6c0f19f271fc9f0b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T11:55:28Z"
    - latency: 3.082245ms
      message: 'load-balancer-api-internal: tcp connection to a0ae91481ffa64920893fc5f6e32f5f1-6c0f19f271fc9f0b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T11:54:28Z"
    - latency: 7.662384ms
      message: 'load-balancer-api-internal: resolved host name a0ae91481ffa64920893fc5f6e32f5f1-6c0f19f271fc9f0b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T11:54:28Z"
    - latency: 4.596527ms
      message: 'load-balancer-api-internal: tcp connection to a0ae91481ffa64920893fc5f6e32f5f1-6c0f19f271fc9f0b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T11:53:28Z"
    - latency: 8.649362ms
      message: 'load-balancer-api-internal: resolved host name a0ae91481ffa64920893fc5f6e32f5f1-6c0f19f271fc9f0b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T11:53:28Z"
    - latency: 3.828028ms
      message: 'load-balancer-api-internal: tcp connection to a0ae91481ffa64920893fc5f6e32f5f1-6c0f19f271fc9f0b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T11:52:28Z"
    - latency: 7.327362ms
      message: 'load-balancer-api-internal: resolved host name a0ae91481ffa64920893fc5f6e32f5f1-6c0f19f271fc9f0b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T11:52:28Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T11:26:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-163-to-network-check-target-ip-10-0-129-163
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-163.ec2.internal
      uid: a92e93ee-b250-4127-87f5-39bb009dba3a
    resourceVersion: "53460"
    uid: 343da0ef-e1ea-45b9-8a0d-573d86d0254f
  spec:
    sourcePod: network-check-source-685456655f-vhznl
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T11:33:28Z"
      message: 'network-check-target-ip-10-0-129-163: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.149718ms
      message: 'network-check-target-ip-10-0-129-163: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T11:54:28Z"
    - latency: 952.757µs
      message: 'network-check-target-ip-10-0-129-163: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T11:53:28Z"
    - latency: 1.252961ms
      message: 'network-check-target-ip-10-0-129-163: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T11:52:28Z"
    - latency: 936.11µs
      message: 'network-check-target-ip-10-0-129-163: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T11:51:28Z"
    - latency: 934.048µs
      message: 'network-check-target-ip-10-0-129-163: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T11:50:28Z"
    - latency: 1.246234ms
      message: 'network-check-target-ip-10-0-129-163: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T11:49:28Z"
    - latency: 1.038357ms
      message: 'network-check-target-ip-10-0-129-163: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T11:48:28Z"
    - latency: 1.049568ms
      message: 'network-check-target-ip-10-0-129-163: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T11:47:28Z"
    - latency: 1.028933ms
      message: 'network-check-target-ip-10-0-129-163: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T11:46:28Z"
    - latency: 1.063552ms
      message: 'network-check-target-ip-10-0-129-163: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T11:45:28Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T11:26:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-163-to-network-check-target-ip-10-0-138-45
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-163.ec2.internal
      uid: a92e93ee-b250-4127-87f5-39bb009dba3a
    resourceVersion: "53461"
    uid: 3a5ea011-d227-49c8-8fed-ed686fcfb2c1
  spec:
    sourcePod: network-check-source-685456655f-vhznl
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T11:33:28Z"
      message: 'network-check-target-ip-10-0-138-45: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.079526ms
      message: 'network-check-target-ip-10-0-138-45: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T11:54:28Z"
    - latency: 2.119992ms
      message: 'network-check-target-ip-10-0-138-45: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T11:53:28Z"
    - latency: 2.106809ms
      message: 'network-check-target-ip-10-0-138-45: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T11:52:28Z"
    - latency: 1.997973ms
      message: 'network-check-target-ip-10-0-138-45: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T11:51:28Z"
    - latency: 1.795872ms
      message: 'network-check-target-ip-10-0-138-45: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T11:50:28Z"
    - latency: 2.092192ms
      message: 'network-check-target-ip-10-0-138-45: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T11:49:28Z"
    - latency: 2.165938ms
      message: 'network-check-target-ip-10-0-138-45: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T11:48:28Z"
    - latency: 1.906384ms
      message: 'network-check-target-ip-10-0-138-45: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T11:47:28Z"
    - latency: 1.956273ms
      message: 'network-check-target-ip-10-0-138-45: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T11:46:28Z"
    - latency: 2.115525ms
      message: 'network-check-target-ip-10-0-138-45: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T11:45:28Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T11:26:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-163-to-network-check-target-ip-10-0-143-241
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-163.ec2.internal
      uid: a92e93ee-b250-4127-87f5-39bb009dba3a
    resourceVersion: "53459"
    uid: 88afbce8-22e9-4927-9075-aa2b98aa4e9f
  spec:
    sourcePod: network-check-source-685456655f-vhznl
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T11:33:28Z"
      message: 'network-check-target-ip-10-0-143-241: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.047251ms
      message: 'network-check-target-ip-10-0-143-241: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T11:54:28Z"
    - latency: 2.384251ms
      message: 'network-check-target-ip-10-0-143-241: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T11:53:28Z"
    - latency: 1.997452ms
      message: 'network-check-target-ip-10-0-143-241: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T11:52:28Z"
    - latency: 1.961345ms
      message: 'network-check-target-ip-10-0-143-241: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T11:51:28Z"
    - latency: 2.21827ms
      message: 'network-check-target-ip-10-0-143-241: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T11:50:28Z"
    - latency: 2.305564ms
      message: 'network-check-target-ip-10-0-143-241: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T11:49:28Z"
    - latency: 2.384015ms
      message: 'network-check-target-ip-10-0-143-241: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T11:48:28Z"
    - latency: 2.194205ms
      message: 'network-check-target-ip-10-0-143-241: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T11:47:28Z"
    - latency: 2.09022ms
      message: 'network-check-target-ip-10-0-143-241: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T11:46:28Z"
    - latency: 2.341152ms
      message: 'network-check-target-ip-10-0-143-241: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T11:45:28Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T11:26:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-163-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-163.ec2.internal
      uid: a92e93ee-b250-4127-87f5-39bb009dba3a
    resourceVersion: "55145"
    uid: 925e878c-71b9-48b9-9a5a-16566935418c
  spec:
    sourcePod: network-check-source-685456655f-vhznl
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T11:32:28Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 705.04µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T11:56:28Z"
    - latency: 1.749287ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T11:56:28Z"
    - latency: 962.285µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T11:55:28Z"
    - latency: 2.605526ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T11:55:28Z"
    - latency: 1.069222ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T11:54:28Z"
    - latency: 2.08783ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T11:54:28Z"
    - latency: 892.197µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T11:53:28Z"
    - latency: 2.031163ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T11:53:28Z"
    - latency: 832.101µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T11:52:28Z"
    - latency: 1.735779ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T11:52:28Z"
kind: List
metadata:
  resourceVersion: ""