apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T13:34:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-208-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-208.ec2.internal
      uid: 661b91f0-2ba7-4b56-bb63-59232d0f8e8d
    resourceVersion: "63563"
    uid: 57396091-6cdf-4a13-bae5-2aa8cb5433d2
  spec:
    sourcePod: network-check-source-685456655f-k67vc
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T13:41:10Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 850.032µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:09:10Z"
    - latency: 1.295359ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:08:10Z"
    - latency: 982.065µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:07:10Z"
    - latency: 965.911µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:06:10Z"
    - latency: 1.104628ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:05:10Z"
    - latency: 1.280453ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:04:10Z"
    - latency: 967.662µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:03:10Z"
    - latency: 1.28829ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:02:10Z"
    - latency: 1.079175ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:01:10Z"
    - latency: 1.032182ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:00:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T13:34:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-208-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-208.ec2.internal
      uid: 661b91f0-2ba7-4b56-bb63-59232d0f8e8d
    resourceVersion: "58829"
    uid: da42146a-4c7b-449c-b9d9-c9fba920d9cd
  spec:
    sourcePod: network-check-source-685456655f-k67vc
    targetEndpoint: ad5abf354409b44248e943a4a1a5e31b-9e4df101270808d3.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T13:40:10Z"
      message: 'load-balancer-api-external: tcp connection to ad5abf354409b44248e943a4a1a5e31b-9e4df101270808d3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.754442ms
      message: 'load-balancer-api-external: tcp connection to ad5abf354409b44248e943a4a1a5e31b-9e4df101270808d3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:04:10Z"
    - latency: 7.461423ms
      message: 'load-balancer-api-external: resolved host name ad5abf354409b44248e943a4a1a5e31b-9e4df101270808d3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T14:04:10Z"
    - latency: 4.477717ms
      message: 'load-balancer-api-external: tcp connection to ad5abf354409b44248e943a4a1a5e31b-9e4df101270808d3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:03:10Z"
    - latency: 7.232868ms
      message: 'load-balancer-api-external: resolved host name ad5abf354409b44248e943a4a1a5e31b-9e4df101270808d3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T14:03:10Z"
    - latency: 6.910047ms
      message: 'load-balancer-api-external: tcp connection to ad5abf354409b44248e943a4a1a5e31b-9e4df101270808d3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:02:10Z"
    - latency: 7.123171ms
      message: 'load-balancer-api-external: resolved host name ad5abf354409b44248e943a4a1a5e31b-9e4df101270808d3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T14:02:10Z"
    - latency: 4.054704ms
      message: 'load-balancer-api-external: tcp connection to ad5abf354409b44248e943a4a1a5e31b-9e4df101270808d3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:01:10Z"
    - latency: 7.335689ms
      message: 'load-balancer-api-external: resolved host name ad5abf354409b44248e943a4a1a5e31b-9e4df101270808d3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T14:01:10Z"
    - latency: 3.94522ms
      message: 'load-balancer-api-external: tcp connection to ad5abf354409b44248e943a4a1a5e31b-9e4df101270808d3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:00:10Z"
    - latency: 6.60142ms
      message: 'load-balancer-api-external: resolved host name ad5abf354409b44248e943a4a1a5e31b-9e4df101270808d3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T14:00:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T13:34:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-208-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-208.ec2.internal
      uid: 661b91f0-2ba7-4b56-bb63-59232d0f8e8d
    resourceVersion: "58830"
    uid: 9e00b538-e5a5-41fe-8000-d169fbdac17d
  spec:
    sourcePod: network-check-source-685456655f-k67vc
    targetEndpoint: ad5abf354409b44248e943a4a1a5e31b-9e4df101270808d3.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T13:40:10Z"
      message: 'load-balancer-api-internal: tcp connection to ad5abf354409b44248e943a4a1a5e31b-9e4df101270808d3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.758346ms
      message: 'load-balancer-api-internal: tcp connection to ad5abf354409b44248e943a4a1a5e31b-9e4df101270808d3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:04:10Z"
    - latency: 7.437034ms
      message: 'load-balancer-api-internal: resolved host name ad5abf354409b44248e943a4a1a5e31b-9e4df101270808d3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T14:04:10Z"
    - latency: 5.993145ms
      message: 'load-balancer-api-internal: tcp connection to ad5abf354409b44248e943a4a1a5e31b-9e4df101270808d3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:03:10Z"
    - latency: 7.137044ms
      message: 'load-balancer-api-internal: resolved host name ad5abf354409b44248e943a4a1a5e31b-9e4df101270808d3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T14:03:10Z"
    - latency: 6.844766ms
      message: 'load-balancer-api-internal: tcp connection to ad5abf354409b44248e943a4a1a5e31b-9e4df101270808d3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:02:10Z"
    - latency: 7.018847ms
      message: 'load-balancer-api-internal: resolved host name ad5abf354409b44248e943a4a1a5e31b-9e4df101270808d3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T14:02:10Z"
    - latency: 4.443645ms
      message: 'load-balancer-api-internal: tcp connection to ad5abf354409b44248e943a4a1a5e31b-9e4df101270808d3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:01:10Z"
    - latency: 7.374805ms
      message: 'load-balancer-api-internal: resolved host name ad5abf354409b44248e943a4a1a5e31b-9e4df101270808d3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T14:01:10Z"
    - latency: 3.945042ms
      message: 'load-balancer-api-internal: tcp connection to ad5abf354409b44248e943a4a1a5e31b-9e4df101270808d3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:00:10Z"
    - latency: 6.430924ms
      message: 'load-balancer-api-internal: resolved host name ad5abf354409b44248e943a4a1a5e31b-9e4df101270808d3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T14:00:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T13:34:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-208-to-network-check-target-ip-10-0-130-202
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-208.ec2.internal
      uid: 661b91f0-2ba7-4b56-bb63-59232d0f8e8d
    resourceVersion: "63565"
    uid: 3a5e954c-8530-4900-b334-376d847c4301
  spec:
    sourcePod: network-check-source-685456655f-k67vc
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T13:41:10Z"
      message: 'network-check-target-ip-10-0-130-202: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.999367ms
      message: 'network-check-target-ip-10-0-130-202: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:09:10Z"
    - latency: 2.134565ms
      message: 'network-check-target-ip-10-0-130-202: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:08:10Z"
    - latency: 2.243937ms
      message: 'network-check-target-ip-10-0-130-202: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:07:10Z"
    - latency: 2.039936ms
      message: 'network-check-target-ip-10-0-130-202: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:06:10Z"
    - latency: 2.113769ms
      message: 'network-check-target-ip-10-0-130-202: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:05:10Z"
    - latency: 2.069417ms
      message: 'network-check-target-ip-10-0-130-202: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:04:10Z"
    - latency: 1.935561ms
      message: 'network-check-target-ip-10-0-130-202: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:03:10Z"
    - latency: 1.899512ms
      message: 'network-check-target-ip-10-0-130-202: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:02:10Z"
    - latency: 2.231829ms
      message: 'network-check-target-ip-10-0-130-202: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:01:10Z"
    - latency: 2.116162ms
      message: 'network-check-target-ip-10-0-130-202: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:00:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T13:34:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-208-to-network-check-target-ip-10-0-133-208
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-208.ec2.internal
      uid: 661b91f0-2ba7-4b56-bb63-59232d0f8e8d
    resourceVersion: "63564"
    uid: 748e468c-cc82-464e-8322-ca71afce796f
  spec:
    sourcePod: network-check-source-685456655f-k67vc
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T13:41:10Z"
      message: 'network-check-target-ip-10-0-133-208: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.082917ms
      message: 'network-check-target-ip-10-0-133-208: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:09:10Z"
    - latency: 987.98µs
      message: 'network-check-target-ip-10-0-133-208: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:08:10Z"
    - latency: 1.225471ms
      message: 'network-check-target-ip-10-0-133-208: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:07:10Z"
    - latency: 1.268533ms
      message: 'network-check-target-ip-10-0-133-208: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:06:10Z"
    - latency: 1.035373ms
      message: 'network-check-target-ip-10-0-133-208: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:05:10Z"
    - latency: 2.018127ms
      message: 'network-check-target-ip-10-0-133-208: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:04:10Z"
    - latency: 994.979µs
      message: 'network-check-target-ip-10-0-133-208: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:03:10Z"
    - latency: 1.017346ms
      message: 'network-check-target-ip-10-0-133-208: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:02:10Z"
    - latency: 943.253µs
      message: 'network-check-target-ip-10-0-133-208: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:01:10Z"
    - latency: 1.241417ms
      message: 'network-check-target-ip-10-0-133-208: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:00:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T13:34:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-208-to-network-check-target-ip-10-0-137-53
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-208.ec2.internal
      uid: 661b91f0-2ba7-4b56-bb63-59232d0f8e8d
    resourceVersion: "63562"
    uid: 691357c0-4499-42ac-82ec-ea9e48492034
  spec:
    sourcePod: network-check-source-685456655f-k67vc
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T13:41:10Z"
      message: 'network-check-target-ip-10-0-137-53: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.219254ms
      message: 'network-check-target-ip-10-0-137-53: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:09:10Z"
    - latency: 2.496148ms
      message: 'network-check-target-ip-10-0-137-53: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:08:10Z"
    - latency: 2.41205ms
      message: 'network-check-target-ip-10-0-137-53: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:07:10Z"
    - latency: 2.352536ms
      message: 'network-check-target-ip-10-0-137-53: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:06:10Z"
    - latency: 2.238375ms
      message: 'network-check-target-ip-10-0-137-53: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:05:10Z"
    - latency: 2.299004ms
      message: 'network-check-target-ip-10-0-137-53: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:04:10Z"
    - latency: 2.503008ms
      message: 'network-check-target-ip-10-0-137-53: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:03:10Z"
    - latency: 2.413362ms
      message: 'network-check-target-ip-10-0-137-53: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:02:10Z"
    - latency: 2.30665ms
      message: 'network-check-target-ip-10-0-137-53: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:01:10Z"
    - latency: 2.181217ms
      message: 'network-check-target-ip-10-0-137-53: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:00:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T13:34:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-208-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-208.ec2.internal
      uid: 661b91f0-2ba7-4b56-bb63-59232d0f8e8d
    resourceVersion: "58828"
    uid: 1981f063-716e-40d3-9cbb-206e352a0274
  spec:
    sourcePod: network-check-source-685456655f-k67vc
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T13:40:10Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 987.219µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:04:10Z"
    - latency: 2.284573ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T14:04:10Z"
    - latency: 1.323611ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:03:10Z"
    - latency: 1.974696ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T14:03:10Z"
    - latency: 1.163472ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:02:10Z"
    - latency: 1.922246ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T14:02:10Z"
    - latency: 1.160494ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:01:10Z"
    - latency: 2.02686ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T14:01:10Z"
    - latency: 993.12µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:00:10Z"
    - latency: 1.907319ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T14:00:10Z"
kind: List
metadata:
  resourceVersion: ""