apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-05T02:21:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-91-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-91.ec2.internal
      uid: 6fe3e2fa-ca38-4e0a-9da1-54c7509c860d
    resourceVersion: "23149"
    uid: 7da0e59d-7186-4806-9d5f-1eb3e962df40
  spec:
    sourcePod: network-check-source-685456655f-8tdx7
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-05T02:28:39Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.328623ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:42:39Z"
    - latency: 1.220015ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:41:39Z"
    - latency: 955.52µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:40:39Z"
    - latency: 1.438242ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:39:39Z"
    - latency: 1.084018ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:38:39Z"
    - latency: 1.227003ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:37:39Z"
    - latency: 1.06543ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:36:39Z"
    - latency: 1.923188ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:35:39Z"
    - latency: 1.143253ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:34:39Z"
    - latency: 983.772µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:33:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-05T02:21:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-91-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-91.ec2.internal
      uid: 6fe3e2fa-ca38-4e0a-9da1-54c7509c860d
    resourceVersion: "24668"
    uid: 38eecc09-17ec-43e5-9a0a-4ec4a9234270
  spec:
    sourcePod: network-check-source-685456655f-8tdx7
    targetEndpoint: a22d454afa104408099af5e7322e698c-a4bb1ae42ddff7df.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-05T02:27:39Z"
      message: 'load-balancer-api-external: tcp connection to a22d454afa104408099af5e7322e698c-a4bb1ae42ddff7df.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.974387ms
      message: 'load-balancer-api-external: tcp connection to a22d454afa104408099af5e7322e698c-a4bb1ae42ddff7df.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:45:39Z"
    - latency: 8.385368ms
      message: 'load-balancer-api-external: resolved host name a22d454afa104408099af5e7322e698c-a4bb1ae42ddff7df.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T02:45:39Z"
    - latency: 5.946574ms
      message: 'load-balancer-api-external: tcp connection to a22d454afa104408099af5e7322e698c-a4bb1ae42ddff7df.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:44:39Z"
    - latency: 15.068728ms
      message: 'load-balancer-api-external: resolved host name a22d454afa104408099af5e7322e698c-a4bb1ae42ddff7df.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T02:44:39Z"
    - latency: 5.373513ms
      message: 'load-balancer-api-external: tcp connection to a22d454afa104408099af5e7322e698c-a4bb1ae42ddff7df.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:43:39Z"
    - latency: 9.195576ms
      message: 'load-balancer-api-external: resolved host name a22d454afa104408099af5e7322e698c-a4bb1ae42ddff7df.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T02:43:39Z"
    - latency: 5.104353ms
      message: 'load-balancer-api-external: tcp connection to a22d454afa104408099af5e7322e698c-a4bb1ae42ddff7df.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:42:39Z"
    - latency: 9.730197ms
      message: 'load-balancer-api-external: resolved host name a22d454afa104408099af5e7322e698c-a4bb1ae42ddff7df.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T02:42:39Z"
    - latency: 4.981268ms
      message: 'load-balancer-api-external: tcp connection to a22d454afa104408099af5e7322e698c-a4bb1ae42ddff7df.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:41:39Z"
    - latency: 8.57681ms
      message: 'load-balancer-api-external: resolved host name a22d454afa104408099af5e7322e698c-a4bb1ae42ddff7df.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T02:41:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-05T02:21:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-91-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-91.ec2.internal
      uid: 6fe3e2fa-ca38-4e0a-9da1-54c7509c860d
    resourceVersion: "24667"
    uid: 1f2f4481-3e4f-4baf-8048-43851881570e
  spec:
    sourcePod: network-check-source-685456655f-8tdx7
    targetEndpoint: a22d454afa104408099af5e7322e698c-a4bb1ae42ddff7df.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-05T02:27:39Z"
      message: 'load-balancer-api-internal: tcp connection to a22d454afa104408099af5e7322e698c-a4bb1ae42ddff7df.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.567426ms
      message: 'load-balancer-api-internal: tcp connection to a22d454afa104408099af5e7322e698c-a4bb1ae42ddff7df.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:45:39Z"
    - latency: 8.404143ms
      message: 'load-balancer-api-internal: resolved host name a22d454afa104408099af5e7322e698c-a4bb1ae42ddff7df.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T02:45:39Z"
    - latency: 5.928258ms
      message: 'load-balancer-api-internal: tcp connection to a22d454afa104408099af5e7322e698c-a4bb1ae42ddff7df.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:44:39Z"
    - latency: 15.036815ms
      message: 'load-balancer-api-internal: resolved host name a22d454afa104408099af5e7322e698c-a4bb1ae42ddff7df.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T02:44:39Z"
    - latency: 5.388761ms
      message: 'load-balancer-api-internal: tcp connection to a22d454afa104408099af5e7322e698c-a4bb1ae42ddff7df.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:43:39Z"
    - latency: 9.247636ms
      message: 'load-balancer-api-internal: resolved host name a22d454afa104408099af5e7322e698c-a4bb1ae42ddff7df.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T02:43:39Z"
    - latency: 5.169804ms
      message: 'load-balancer-api-internal: tcp connection to a22d454afa104408099af5e7322e698c-a4bb1ae42ddff7df.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:42:39Z"
    - latency: 9.809943ms
      message: 'load-balancer-api-internal: resolved host name a22d454afa104408099af5e7322e698c-a4bb1ae42ddff7df.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T02:42:39Z"
    - latency: 4.992394ms
      message: 'load-balancer-api-internal: tcp connection to a22d454afa104408099af5e7322e698c-a4bb1ae42ddff7df.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:41:39Z"
    - latency: 8.497099ms
      message: 'load-balancer-api-internal: resolved host name a22d454afa104408099af5e7322e698c-a4bb1ae42ddff7df.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T02:41:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-05T02:21:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-91-to-network-check-target-ip-10-0-131-142
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-91.ec2.internal
      uid: 6fe3e2fa-ca38-4e0a-9da1-54c7509c860d
    resourceVersion: "23147"
    uid: a496f948-3d23-44f0-9edd-e16d25319b3e
  spec:
    sourcePod: network-check-source-685456655f-8tdx7
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-05T02:28:39Z"
      message: 'network-check-target-ip-10-0-131-142: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.466282ms
      message: 'network-check-target-ip-10-0-131-142: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:42:39Z"
    - latency: 2.263495ms
      message: 'network-check-target-ip-10-0-131-142: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:41:39Z"
    - latency: 2.883205ms
      message: 'network-check-target-ip-10-0-131-142: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:40:39Z"
    - latency: 2.242958ms
      message: 'network-check-target-ip-10-0-131-142: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:39:39Z"
    - latency: 2.382268ms
      message: 'network-check-target-ip-10-0-131-142: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:38:39Z"
    - latency: 2.390234ms
      message: 'network-check-target-ip-10-0-131-142: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:37:39Z"
    - latency: 2.209357ms
      message: 'network-check-target-ip-10-0-131-142: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:36:39Z"
    - latency: 4.108599ms
      message: 'network-check-target-ip-10-0-131-142: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:35:39Z"
    - latency: 2.266995ms
      message: 'network-check-target-ip-10-0-131-142: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:34:39Z"
    - latency: 2.283432ms
      message: 'network-check-target-ip-10-0-131-142: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:33:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-05T02:21:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-91-to-network-check-target-ip-10-0-133-250
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-91.ec2.internal
      uid: 6fe3e2fa-ca38-4e0a-9da1-54c7509c860d
    resourceVersion: "23148"
    uid: cdc75f40-cb78-45fd-85d5-56b5016d3f17
  spec:
    sourcePod: network-check-source-685456655f-8tdx7
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-05T02:28:39Z"
      message: 'network-check-target-ip-10-0-133-250: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.37802ms
      message: 'network-check-target-ip-10-0-133-250: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:42:39Z"
    - latency: 1.998013ms
      message: 'network-check-target-ip-10-0-133-250: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:41:39Z"
    - latency: 2.536154ms
      message: 'network-check-target-ip-10-0-133-250: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:40:39Z"
    - latency: 2.202947ms
      message: 'network-check-target-ip-10-0-133-250: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:39:39Z"
    - latency: 2.184233ms
      message: 'network-check-target-ip-10-0-133-250: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:38:39Z"
    - latency: 2.123305ms
      message: 'network-check-target-ip-10-0-133-250: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:37:39Z"
    - latency: 2.24385ms
      message: 'network-check-target-ip-10-0-133-250: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:36:39Z"
    - latency: 4.217927ms
      message: 'network-check-target-ip-10-0-133-250: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:35:39Z"
    - latency: 2.358294ms
      message: 'network-check-target-ip-10-0-133-250: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:34:39Z"
    - latency: 2.286598ms
      message: 'network-check-target-ip-10-0-133-250: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:33:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-05T02:21:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-91-to-network-check-target-ip-10-0-138-91
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-91.ec2.internal
      uid: 6fe3e2fa-ca38-4e0a-9da1-54c7509c860d
    resourceVersion: "23146"
    uid: e9a642e3-4e53-4439-b285-829765c1435f
  spec:
    sourcePod: network-check-source-685456655f-8tdx7
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-05T02:28:39Z"
      message: 'network-check-target-ip-10-0-138-91: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 895.607µs
      message: 'network-check-target-ip-10-0-138-91: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:42:39Z"
    - latency: 1.071011ms
      message: 'network-check-target-ip-10-0-138-91: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:41:39Z"
    - latency: 1.116648ms
      message: 'network-check-target-ip-10-0-138-91: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:40:39Z"
    - latency: 964.901µs
      message: 'network-check-target-ip-10-0-138-91: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:39:39Z"
    - latency: 970.058µs
      message: 'network-check-target-ip-10-0-138-91: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:38:39Z"
    - latency: 1.526712ms
      message: 'network-check-target-ip-10-0-138-91: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:37:39Z"
    - latency: 1.376199ms
      message: 'network-check-target-ip-10-0-138-91: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:36:39Z"
    - latency: 2.459256ms
      message: 'network-check-target-ip-10-0-138-91: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:35:39Z"
    - latency: 1.062887ms
      message: 'network-check-target-ip-10-0-138-91: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:34:39Z"
    - latency: 1.382553ms
      message: 'network-check-target-ip-10-0-138-91: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:33:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-05T02:21:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-91-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-91.ec2.internal
      uid: 6fe3e2fa-ca38-4e0a-9da1-54c7509c860d
    resourceVersion: "24666"
    uid: 1c413c40-2763-4d4b-a196-422e23f6b37e
  spec:
    sourcePod: network-check-source-685456655f-8tdx7
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-05T02:27:39Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.049749ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:45:39Z"
    - latency: 2.072298ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T02:45:39Z"
    - latency: 1.653904ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:44:39Z"
    - latency: 3.030064ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T02:44:39Z"
    - latency: 1.011226ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:43:39Z"
    - latency: 2.124095ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T02:43:39Z"
    - latency: 1.345386ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:42:39Z"
    - latency: 1.878201ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T02:42:39Z"
    - latency: 1.015854ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:41:39Z"
    - latency: 2.045843ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T02:41:39Z"
kind: List
metadata:
  resourceVersion: ""