apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-11T18:33:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-170-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-170.ec2.internal
      uid: 51c14791-4e21-43ff-b2df-aa0a07a8cddc
    resourceVersion: "31621"
    uid: 5acee05c-857f-4fdd-a9d9-2c7154d082ed
  spec:
    sourcePod: network-check-source-6947749cfc-8zxb4
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-06-11T18:40:59Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.25322ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T18:47:59Z"
    - latency: 1.130253ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T18:46:59Z"
    - latency: 1.574043ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T18:45:59Z"
    - latency: 906.674µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T18:44:59Z"
    - latency: 1.26557ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T18:43:59Z"
    - latency: 1.157226ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T18:42:59Z"
    - latency: 887.876µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T18:41:59Z"
    - latency: 879.629µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T18:40:59Z"
    - latency: 978.795µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T18:39:59Z"
    - latency: 2.271747ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T18:38:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-11T18:33:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-170-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-170.ec2.internal
      uid: 51c14791-4e21-43ff-b2df-aa0a07a8cddc
    resourceVersion: "29721"
    uid: 6d2e43f8-49e5-48e4-85b4-f76e9b6bb181
  spec:
    sourcePod: network-check-source-6947749cfc-8zxb4
    targetEndpoint: a88fde2a9a0aa4f48aca5b2d4706618f-fb911bc6279dc9ff.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-11T18:39:59Z"
      message: 'load-balancer-api-external: tcp connection to a88fde2a9a0aa4f48aca5b2d4706618f-fb911bc6279dc9ff.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.922416ms
      message: 'load-balancer-api-external: tcp connection to a88fde2a9a0aa4f48aca5b2d4706618f-fb911bc6279dc9ff.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T18:45:59Z"
    - latency: 9.718636ms
      message: 'load-balancer-api-external: resolved host name a88fde2a9a0aa4f48aca5b2d4706618f-fb911bc6279dc9ff.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T18:45:59Z"
    - latency: 4.131394ms
      message: 'load-balancer-api-external: tcp connection to a88fde2a9a0aa4f48aca5b2d4706618f-fb911bc6279dc9ff.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T18:44:59Z"
    - latency: 8.717976ms
      message: 'load-balancer-api-external: resolved host name a88fde2a9a0aa4f48aca5b2d4706618f-fb911bc6279dc9ff.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T18:44:59Z"
    - latency: 3.659389ms
      message: 'load-balancer-api-external: tcp connection to a88fde2a9a0aa4f48aca5b2d4706618f-fb911bc6279dc9ff.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T18:43:59Z"
    - latency: 7.029136ms
      message: 'load-balancer-api-external: resolved host name a88fde2a9a0aa4f48aca5b2d4706618f-fb911bc6279dc9ff.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T18:43:59Z"
    - latency: 5.032798ms
      message: 'load-balancer-api-external: tcp connection to a88fde2a9a0aa4f48aca5b2d4706618f-fb911bc6279dc9ff.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T18:42:59Z"
    - latency: 9.244569ms
      message: 'load-balancer-api-external: resolved host name a88fde2a9a0aa4f48aca5b2d4706618f-fb911bc6279dc9ff.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T18:42:59Z"
    - latency: 4.825441ms
      message: 'load-balancer-api-external: tcp connection to a88fde2a9a0aa4f48aca5b2d4706618f-fb911bc6279dc9ff.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T18:41:59Z"
    - latency: 8.044943ms
      message: 'load-balancer-api-external: resolved host name a88fde2a9a0aa4f48aca5b2d4706618f-fb911bc6279dc9ff.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T18:41:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-11T18:33:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-170-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-170.ec2.internal
      uid: 51c14791-4e21-43ff-b2df-aa0a07a8cddc
    resourceVersion: "29720"
    uid: 4706770f-f31c-46a3-908d-abf0668065e3
  spec:
    sourcePod: network-check-source-6947749cfc-8zxb4
    targetEndpoint: a88fde2a9a0aa4f48aca5b2d4706618f-fb911bc6279dc9ff.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-11T18:39:59Z"
      message: 'load-balancer-api-internal: tcp connection to a88fde2a9a0aa4f48aca5b2d4706618f-fb911bc6279dc9ff.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.94133ms
      message: 'load-balancer-api-internal: tcp connection to a88fde2a9a0aa4f48aca5b2d4706618f-fb911bc6279dc9ff.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T18:45:59Z"
    - latency: 9.565873ms
      message: 'load-balancer-api-internal: resolved host name a88fde2a9a0aa4f48aca5b2d4706618f-fb911bc6279dc9ff.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T18:45:59Z"
    - latency: 4.173784ms
      message: 'load-balancer-api-internal: tcp connection to a88fde2a9a0aa4f48aca5b2d4706618f-fb911bc6279dc9ff.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T18:44:59Z"
    - latency: 8.587756ms
      message: 'load-balancer-api-internal: resolved host name a88fde2a9a0aa4f48aca5b2d4706618f-fb911bc6279dc9ff.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T18:44:59Z"
    - latency: 4.214587ms
      message: 'load-balancer-api-internal: tcp connection to a88fde2a9a0aa4f48aca5b2d4706618f-fb911bc6279dc9ff.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T18:43:59Z"
    - latency: 7.111649ms
      message: 'load-balancer-api-internal: resolved host name a88fde2a9a0aa4f48aca5b2d4706618f-fb911bc6279dc9ff.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T18:43:59Z"
    - latency: 5.043955ms
      message: 'load-balancer-api-internal: tcp connection to a88fde2a9a0aa4f48aca5b2d4706618f-fb911bc6279dc9ff.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T18:42:59Z"
    - latency: 9.134899ms
      message: 'load-balancer-api-internal: resolved host name a88fde2a9a0aa4f48aca5b2d4706618f-fb911bc6279dc9ff.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T18:42:59Z"
    - latency: 4.888951ms
      message: 'load-balancer-api-internal: tcp connection to a88fde2a9a0aa4f48aca5b2d4706618f-fb911bc6279dc9ff.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T18:41:59Z"
    - latency: 7.965522ms
      message: 'load-balancer-api-internal: resolved host name a88fde2a9a0aa4f48aca5b2d4706618f-fb911bc6279dc9ff.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T18:41:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-11T18:33:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-170-to-network-check-target-ip-10-0-128-178
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-170.ec2.internal
      uid: 51c14791-4e21-43ff-b2df-aa0a07a8cddc
    resourceVersion: "31619"
    uid: 6f15b430-21c3-4882-a07b-ce840ce0ae5b
  spec:
    sourcePod: network-check-source-6947749cfc-8zxb4
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-11T18:40:59Z"
      message: 'network-check-target-ip-10-0-128-178: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.243941ms
      message: 'network-check-target-ip-10-0-128-178: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T18:47:59Z"
    - latency: 2.373852ms
      message: 'network-check-target-ip-10-0-128-178: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T18:46:59Z"
    - latency: 2.589699ms
      message: 'network-check-target-ip-10-0-128-178: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T18:45:59Z"
    - latency: 2.173459ms
      message: 'network-check-target-ip-10-0-128-178: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T18:44:59Z"
    - latency: 2.439166ms
      message: 'network-check-target-ip-10-0-128-178: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T18:43:59Z"
    - latency: 2.394373ms
      message: 'network-check-target-ip-10-0-128-178: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T18:42:59Z"
    - latency: 2.218101ms
      message: 'network-check-target-ip-10-0-128-178: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T18:41:59Z"
    - latency: 2.496332ms
      message: 'network-check-target-ip-10-0-128-178: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T18:40:59Z"
    - latency: 2.788492ms
      message: 'network-check-target-ip-10-0-128-178: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T18:39:59Z"
    - latency: 3.772241ms
      message: 'network-check-target-ip-10-0-128-178: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T18:38:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-11T18:33:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-170-to-network-check-target-ip-10-0-130-170
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-170.ec2.internal
      uid: 51c14791-4e21-43ff-b2df-aa0a07a8cddc
    resourceVersion: "31618"
    uid: c1db884e-786b-48f2-b7c3-d185ed941fe1
  spec:
    sourcePod: network-check-source-6947749cfc-8zxb4
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-11T18:40:59Z"
      message: 'network-check-target-ip-10-0-130-170: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.160856ms
      message: 'network-check-target-ip-10-0-130-170: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T18:47:59Z"
    - latency: 839.606µs
      message: 'network-check-target-ip-10-0-130-170: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T18:46:59Z"
    - latency: 1.791558ms
      message: 'network-check-target-ip-10-0-130-170: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T18:45:59Z"
    - latency: 782.143µs
      message: 'network-check-target-ip-10-0-130-170: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T18:44:59Z"
    - latency: 1.685023ms
      message: 'network-check-target-ip-10-0-130-170: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T18:43:59Z"
    - latency: 935.94µs
      message: 'network-check-target-ip-10-0-130-170: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T18:42:59Z"
    - latency: 931.883µs
      message: 'network-check-target-ip-10-0-130-170: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T18:41:59Z"
    - latency: 1.390976ms
      message: 'network-check-target-ip-10-0-130-170: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T18:40:59Z"
    - latency: 1.179966ms
      message: 'network-check-target-ip-10-0-130-170: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T18:39:59Z"
    - latency: 1.978718ms
      message: 'network-check-target-ip-10-0-130-170: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T18:38:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-11T18:33:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-170-to-network-check-target-ip-10-0-143-116
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-170.ec2.internal
      uid: 51c14791-4e21-43ff-b2df-aa0a07a8cddc
    resourceVersion: "31620"
    uid: f7e879b1-1b29-44ea-b90e-4c9ebae54072
  spec:
    sourcePod: network-check-source-6947749cfc-8zxb4
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-11T18:40:59Z"
      message: 'network-check-target-ip-10-0-143-116: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.255048ms
      message: 'network-check-target-ip-10-0-143-116: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T18:47:59Z"
    - latency: 2.355163ms
      message: 'network-check-target-ip-10-0-143-116: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T18:46:59Z"
    - latency: 2.499997ms
      message: 'network-check-target-ip-10-0-143-116: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T18:45:59Z"
    - latency: 2.325683ms
      message: 'network-check-target-ip-10-0-143-116: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T18:44:59Z"
    - latency: 2.390478ms
      message: 'network-check-target-ip-10-0-143-116: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T18:43:59Z"
    - latency: 2.364292ms
      message: 'network-check-target-ip-10-0-143-116: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T18:42:59Z"
    - latency: 2.075684ms
      message: 'network-check-target-ip-10-0-143-116: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T18:41:59Z"
    - latency: 2.436331ms
      message: 'network-check-target-ip-10-0-143-116: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T18:40:59Z"
    - latency: 2.806539ms
      message: 'network-check-target-ip-10-0-143-116: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T18:39:59Z"
    - latency: 3.671644ms
      message: 'network-check-target-ip-10-0-143-116: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T18:38:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-11T18:33:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-170-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-170.ec2.internal
      uid: 51c14791-4e21-43ff-b2df-aa0a07a8cddc
    resourceVersion: "29718"
    uid: 151a45ae-b3b5-4522-90c2-d46ed830c30e
  spec:
    sourcePod: network-check-source-6947749cfc-8zxb4
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-06-11T18:39:59Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 957.27µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T18:45:59Z"
    - latency: 2.004301ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T18:45:59Z"
    - latency: 804.544µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T18:44:59Z"
    - latency: 1.596469ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T18:44:59Z"
    - latency: 983.061µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T18:43:59Z"
    - latency: 1.720195ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T18:43:59Z"
    - latency: 1.059946ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T18:42:59Z"
    - latency: 1.915072ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T18:42:59Z"
    - latency: 1.220911ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T18:41:59Z"
    - latency: 1.699065ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T18:41:59Z"
kind: List
metadata:
  resourceVersion: ""