apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-13T18:36:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-162-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-162.ec2.internal
      uid: 57dcde5b-c190-4f29-90a0-554c12c511dd
    resourceVersion: "62602"
    uid: 60e044af-80b9-4b2a-9ba6-4b048de3fcbd
  spec:
    sourcePod: network-check-source-869dcfcdcd-h5lnr
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-13T18:43:28Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.10229ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T19:18:28Z"
    - latency: 1.09285ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T19:17:28Z"
    - latency: 957.38µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T19:16:28Z"
    - latency: 1.054265ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T19:15:28Z"
    - latency: 1.605661ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T19:14:28Z"
    - latency: 1.521049ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T19:13:28Z"
    - latency: 1.152005ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T19:12:28Z"
    - latency: 1.492184ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T19:11:28Z"
    - latency: 1.203499ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T19:10:28Z"
    - latency: 1.468718ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T19:09:28Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-13T18:36:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-162-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-162.ec2.internal
      uid: 57dcde5b-c190-4f29-90a0-554c12c511dd
    resourceVersion: "62603"
    uid: ed68c324-52c2-41e4-a401-2b3b4b9f2c47
  spec:
    sourcePod: network-check-source-869dcfcdcd-h5lnr
    targetEndpoint: a4275cfd97a594068bf85bcc93aeae9b-4016cc313169619f.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-13T18:42:28Z"
      message: 'load-balancer-api-external: tcp connection to a4275cfd97a594068bf85bcc93aeae9b-4016cc313169619f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.504031ms
      message: 'load-balancer-api-external: tcp connection to a4275cfd97a594068bf85bcc93aeae9b-4016cc313169619f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T19:18:28Z"
    - latency: 8.713669ms
      message: 'load-balancer-api-external: resolved host name a4275cfd97a594068bf85bcc93aeae9b-4016cc313169619f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T19:18:28Z"
    - latency: 3.864844ms
      message: 'load-balancer-api-external: tcp connection to a4275cfd97a594068bf85bcc93aeae9b-4016cc313169619f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T19:17:28Z"
    - latency: 8.352834ms
      message: 'load-balancer-api-external: resolved host name a4275cfd97a594068bf85bcc93aeae9b-4016cc313169619f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T19:17:28Z"
    - latency: 4.891624ms
      message: 'load-balancer-api-external: tcp connection to a4275cfd97a594068bf85bcc93aeae9b-4016cc313169619f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T19:16:28Z"
    - latency: 8.358167ms
      message: 'load-balancer-api-external: resolved host name a4275cfd97a594068bf85bcc93aeae9b-4016cc313169619f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T19:16:28Z"
    - latency: 4.393867ms
      message: 'load-balancer-api-external: tcp connection to a4275cfd97a594068bf85bcc93aeae9b-4016cc313169619f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T19:15:28Z"
    - latency: 8.947279ms
      message: 'load-balancer-api-external: resolved host name a4275cfd97a594068bf85bcc93aeae9b-4016cc313169619f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T19:15:28Z"
    - latency: 4.565387ms
      message: 'load-balancer-api-external: tcp connection to a4275cfd97a594068bf85bcc93aeae9b-4016cc313169619f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T19:14:28Z"
    - latency: 9.604656ms
      message: 'load-balancer-api-external: resolved host name a4275cfd97a594068bf85bcc93aeae9b-4016cc313169619f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T19:14:28Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-13T18:36:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-162-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-162.ec2.internal
      uid: 57dcde5b-c190-4f29-90a0-554c12c511dd
    resourceVersion: "62604"
    uid: 73bc0e02-a0da-4310-b6c4-af5490c2d361
  spec:
    sourcePod: network-check-source-869dcfcdcd-h5lnr
    targetEndpoint: a4275cfd97a594068bf85bcc93aeae9b-4016cc313169619f.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-13T18:42:28Z"
      message: 'load-balancer-api-internal: tcp connection to a4275cfd97a594068bf85bcc93aeae9b-4016cc313169619f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.51374ms
      message: 'load-balancer-api-internal: tcp connection to a4275cfd97a594068bf85bcc93aeae9b-4016cc313169619f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T19:18:28Z"
    - latency: 8.805045ms
      message: 'load-balancer-api-internal: resolved host name a4275cfd97a594068bf85bcc93aeae9b-4016cc313169619f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T19:18:28Z"
    - latency: 3.910991ms
      message: 'load-balancer-api-internal: tcp connection to a4275cfd97a594068bf85bcc93aeae9b-4016cc313169619f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T19:17:28Z"
    - latency: 8.243697ms
      message: 'load-balancer-api-internal: resolved host name a4275cfd97a594068bf85bcc93aeae9b-4016cc313169619f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T19:17:28Z"
    - latency: 4.90142ms
      message: 'load-balancer-api-internal: tcp connection to a4275cfd97a594068bf85bcc93aeae9b-4016cc313169619f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T19:16:28Z"
    - latency: 8.26621ms
      message: 'load-balancer-api-internal: resolved host name a4275cfd97a594068bf85bcc93aeae9b-4016cc313169619f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T19:16:28Z"
    - latency: 4.472997ms
      message: 'load-balancer-api-internal: tcp connection to a4275cfd97a594068bf85bcc93aeae9b-4016cc313169619f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T19:15:28Z"
    - latency: 8.845632ms
      message: 'load-balancer-api-internal: resolved host name a4275cfd97a594068bf85bcc93aeae9b-4016cc313169619f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T19:15:28Z"
    - latency: 5.476394ms
      message: 'load-balancer-api-internal: tcp connection to a4275cfd97a594068bf85bcc93aeae9b-4016cc313169619f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T19:14:28Z"
    - latency: 9.551291ms
      message: 'load-balancer-api-internal: resolved host name a4275cfd97a594068bf85bcc93aeae9b-4016cc313169619f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T19:14:28Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-13T18:36:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-162-to-network-check-target-ip-10-0-129-191
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-162.ec2.internal
      uid: 57dcde5b-c190-4f29-90a0-554c12c511dd
    resourceVersion: "62600"
    uid: c8aec046-ce61-4375-ad8a-dda37c77b14d
  spec:
    sourcePod: network-check-source-869dcfcdcd-h5lnr
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-13T18:43:28Z"
      message: 'network-check-target-ip-10-0-129-191: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.545889ms
      message: 'network-check-target-ip-10-0-129-191: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T19:18:28Z"
    - latency: 2.052871ms
      message: 'network-check-target-ip-10-0-129-191: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T19:17:28Z"
    - latency: 2.030848ms
      message: 'network-check-target-ip-10-0-129-191: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T19:16:28Z"
    - latency: 2.041456ms
      message: 'network-check-target-ip-10-0-129-191: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T19:15:28Z"
    - latency: 1.99432ms
      message: 'network-check-target-ip-10-0-129-191: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T19:14:28Z"
    - latency: 2.03552ms
      message: 'network-check-target-ip-10-0-129-191: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T19:13:28Z"
    - latency: 1.88431ms
      message: 'network-check-target-ip-10-0-129-191: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T19:12:28Z"
    - latency: 1.936716ms
      message: 'network-check-target-ip-10-0-129-191: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T19:11:28Z"
    - latency: 1.893891ms
      message: 'network-check-target-ip-10-0-129-191: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T19:10:28Z"
    - latency: 1.96842ms
      message: 'network-check-target-ip-10-0-129-191: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T19:09:28Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-13T18:36:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-162-to-network-check-target-ip-10-0-131-162
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-162.ec2.internal
      uid: 57dcde5b-c190-4f29-90a0-554c12c511dd
    resourceVersion: "62598"
    uid: 27f30c4e-09db-4028-82d1-d4da21e8088d
  spec:
    sourcePod: network-check-source-869dcfcdcd-h5lnr
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-13T18:43:28Z"
      message: 'network-check-target-ip-10-0-131-162: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 855.738µs
      message: 'network-check-target-ip-10-0-131-162: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T19:18:28Z"
    - latency: 1.495015ms
      message: 'network-check-target-ip-10-0-131-162: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T19:17:28Z"
    - latency: 1.241773ms
      message: 'network-check-target-ip-10-0-131-162: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T19:16:28Z"
    - latency: 946.429µs
      message: 'network-check-target-ip-10-0-131-162: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T19:15:28Z"
    - latency: 901.105µs
      message: 'network-check-target-ip-10-0-131-162: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T19:14:28Z"
    - latency: 910.022µs
      message: 'network-check-target-ip-10-0-131-162: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T19:13:28Z"
    - latency: 1.058082ms
      message: 'network-check-target-ip-10-0-131-162: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T19:12:28Z"
    - latency: 1.027058ms
      message: 'network-check-target-ip-10-0-131-162: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T19:11:28Z"
    - latency: 960.921µs
      message: 'network-check-target-ip-10-0-131-162: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T19:10:28Z"
    - latency: 797.525µs
      message: 'network-check-target-ip-10-0-131-162: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T19:09:28Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-13T18:36:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-162-to-network-check-target-ip-10-0-139-206
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-162.ec2.internal
      uid: 57dcde5b-c190-4f29-90a0-554c12c511dd
    resourceVersion: "62599"
    uid: 63c15094-5f66-4709-a1a5-51261a179be0
  spec:
    sourcePod: network-check-source-869dcfcdcd-h5lnr
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-13T18:43:28Z"
      message: 'network-check-target-ip-10-0-139-206: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.94536ms
      message: 'network-check-target-ip-10-0-139-206: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T19:18:28Z"
    - latency: 2.82442ms
      message: 'network-check-target-ip-10-0-139-206: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T19:17:28Z"
    - latency: 1.913898ms
      message: 'network-check-target-ip-10-0-139-206: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T19:16:28Z"
    - latency: 2.388841ms
      message: 'network-check-target-ip-10-0-139-206: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T19:15:28Z"
    - latency: 2.362659ms
      message: 'network-check-target-ip-10-0-139-206: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T19:14:28Z"
    - latency: 2.809386ms
      message: 'network-check-target-ip-10-0-139-206: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T19:13:28Z"
    - latency: 2.254651ms
      message: 'network-check-target-ip-10-0-139-206: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T19:12:28Z"
    - latency: 2.189323ms
      message: 'network-check-target-ip-10-0-139-206: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T19:11:28Z"
    - latency: 1.873631ms
      message: 'network-check-target-ip-10-0-139-206: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T19:10:28Z"
    - latency: 2.993196ms
      message: 'network-check-target-ip-10-0-139-206: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T19:09:28Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-13T18:36:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-162-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-162.ec2.internal
      uid: 57dcde5b-c190-4f29-90a0-554c12c511dd
    resourceVersion: "62601"
    uid: aac46a26-c942-4ece-954a-903b8e3a0138
  spec:
    sourcePod: network-check-source-869dcfcdcd-h5lnr
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-13T18:42:28Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 979.469µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T19:18:28Z"
    - latency: 1.767602ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T19:18:28Z"
    - latency: 788.406µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T19:17:28Z"
    - latency: 1.729327ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T19:17:28Z"
    - latency: 889.811µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T19:16:28Z"
    - latency: 1.705593ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T19:16:28Z"
    - latency: 864.164µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T19:15:28Z"
    - latency: 1.87041ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T19:15:28Z"
    - latency: 897.738µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T19:14:28Z"
    - latency: 2.102613ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T19:14:28Z"
kind: List
metadata:
  resourceVersion: ""