apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-28T19:24:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-34-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-34.ec2.internal
      uid: 9cf3a5f0-f30e-40a8-b273-54d70220112a
    resourceVersion: "32930"
    uid: 51c251c5-42c3-4489-b14f-4a542c6f6a6c
  spec:
    sourcePod: network-check-source-8894fc9bd-8fxnw
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-04-28T19:32:00Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.008125ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-28T20:07:00Z"
    - latency: 1.085478ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-28T20:06:00Z"
    - latency: 870.864µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-28T20:05:00Z"
    - latency: 1.025436ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-28T20:04:00Z"
    - latency: 1.017626ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-28T20:03:00Z"
    - latency: 898.626µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-28T20:02:00Z"
    - latency: 1.006016ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-28T20:01:00Z"
    - latency: 1.610979ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-28T20:00:00Z"
    - latency: 960.857µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-28T19:59:00Z"
    - latency: 1.031413ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-28T19:58:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-28T19:24:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-34-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-34.ec2.internal
      uid: 9cf3a5f0-f30e-40a8-b273-54d70220112a
    resourceVersion: "32932"
    uid: 4e7274cf-7d14-4e46-bf63-083739abd278
  spec:
    sourcePod: network-check-source-8894fc9bd-8fxnw
    targetEndpoint: ad25238e5e4a044969da54efa5bc9dd2-deb528e2894465cc.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-04-28T19:31:00Z"
      message: 'load-balancer-api-external: tcp connection to ad25238e5e4a044969da54efa5bc9dd2-deb528e2894465cc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.301367ms
      message: 'load-balancer-api-external: tcp connection to ad25238e5e4a044969da54efa5bc9dd2-deb528e2894465cc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-28T20:07:00Z"
    - latency: 8.284848ms
      message: 'load-balancer-api-external: resolved host name ad25238e5e4a044969da54efa5bc9dd2-deb528e2894465cc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-28T20:07:00Z"
    - latency: 4.986556ms
      message: 'load-balancer-api-external: tcp connection to ad25238e5e4a044969da54efa5bc9dd2-deb528e2894465cc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-28T20:06:00Z"
    - latency: 8.538478ms
      message: 'load-balancer-api-external: resolved host name ad25238e5e4a044969da54efa5bc9dd2-deb528e2894465cc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-28T20:06:00Z"
    - latency: 4.643375ms
      message: 'load-balancer-api-external: tcp connection to ad25238e5e4a044969da54efa5bc9dd2-deb528e2894465cc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-28T20:05:00Z"
    - latency: 8.198173ms
      message: 'load-balancer-api-external: resolved host name ad25238e5e4a044969da54efa5bc9dd2-deb528e2894465cc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-28T20:05:00Z"
    - latency: 5.544788ms
      message: 'load-balancer-api-external: tcp connection to ad25238e5e4a044969da54efa5bc9dd2-deb528e2894465cc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-28T20:04:00Z"
    - latency: 7.513642ms
      message: 'load-balancer-api-external: resolved host name ad25238e5e4a044969da54efa5bc9dd2-deb528e2894465cc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-28T20:04:00Z"
    - latency: 4.886391ms
      message: 'load-balancer-api-external: tcp connection to ad25238e5e4a044969da54efa5bc9dd2-deb528e2894465cc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-28T20:03:00Z"
    - latency: 7.654962ms
      message: 'load-balancer-api-external: resolved host name ad25238e5e4a044969da54efa5bc9dd2-deb528e2894465cc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-28T20:03:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-28T19:24:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-34-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-34.ec2.internal
      uid: 9cf3a5f0-f30e-40a8-b273-54d70220112a
    resourceVersion: "32931"
    uid: 1cfcf53c-74cc-48f8-88e0-fd58d7beb535
  spec:
    sourcePod: network-check-source-8894fc9bd-8fxnw
    targetEndpoint: ad25238e5e4a044969da54efa5bc9dd2-deb528e2894465cc.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-04-28T19:31:00Z"
      message: 'load-balancer-api-internal: tcp connection to ad25238e5e4a044969da54efa5bc9dd2-deb528e2894465cc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.337332ms
      message: 'load-balancer-api-internal: tcp connection to ad25238e5e4a044969da54efa5bc9dd2-deb528e2894465cc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-28T20:07:00Z"
    - latency: 8.192547ms
      message: 'load-balancer-api-internal: resolved host name ad25238e5e4a044969da54efa5bc9dd2-deb528e2894465cc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-28T20:07:00Z"
    - latency: 4.892646ms
      message: 'load-balancer-api-internal: tcp connection to ad25238e5e4a044969da54efa5bc9dd2-deb528e2894465cc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-28T20:06:00Z"
    - latency: 8.575485ms
      message: 'load-balancer-api-internal: resolved host name ad25238e5e4a044969da54efa5bc9dd2-deb528e2894465cc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-28T20:06:00Z"
    - latency: 4.525731ms
      message: 'load-balancer-api-internal: tcp connection to ad25238e5e4a044969da54efa5bc9dd2-deb528e2894465cc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-28T20:05:00Z"
    - latency: 8.174414ms
      message: 'load-balancer-api-internal: resolved host name ad25238e5e4a044969da54efa5bc9dd2-deb528e2894465cc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-28T20:05:00Z"
    - latency: 5.512269ms
      message: 'load-balancer-api-internal: tcp connection to ad25238e5e4a044969da54efa5bc9dd2-deb528e2894465cc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-28T20:04:00Z"
    - latency: 7.533213ms
      message: 'load-balancer-api-internal: resolved host name ad25238e5e4a044969da54efa5bc9dd2-deb528e2894465cc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-28T20:04:00Z"
    - latency: 4.864847ms
      message: 'load-balancer-api-internal: tcp connection to ad25238e5e4a044969da54efa5bc9dd2-deb528e2894465cc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-28T20:03:00Z"
    - latency: 7.714523ms
      message: 'load-balancer-api-internal: resolved host name ad25238e5e4a044969da54efa5bc9dd2-deb528e2894465cc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-28T20:03:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-28T19:24:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-34-to-network-check-target-ip-10-0-138-34
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-34.ec2.internal
      uid: 9cf3a5f0-f30e-40a8-b273-54d70220112a
    resourceVersion: "32926"
    uid: 3ec48ee5-b77b-4863-acb6-7aa72358ac1b
  spec:
    sourcePod: network-check-source-8894fc9bd-8fxnw
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-28T19:32:00Z"
      message: 'network-check-target-ip-10-0-138-34: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 818.121µs
      message: 'network-check-target-ip-10-0-138-34: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-28T20:07:00Z"
    - latency: 941.236µs
      message: 'network-check-target-ip-10-0-138-34: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-28T20:06:00Z"
    - latency: 830.986µs
      message: 'network-check-target-ip-10-0-138-34: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-28T20:05:00Z"
    - latency: 802.03µs
      message: 'network-check-target-ip-10-0-138-34: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-28T20:04:00Z"
    - latency: 937.603µs
      message: 'network-check-target-ip-10-0-138-34: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-28T20:03:00Z"
    - latency: 791.043µs
      message: 'network-check-target-ip-10-0-138-34: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-28T20:02:00Z"
    - latency: 862.202µs
      message: 'network-check-target-ip-10-0-138-34: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-28T20:01:00Z"
    - latency: 870.94µs
      message: 'network-check-target-ip-10-0-138-34: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-28T20:00:00Z"
    - latency: 1.145426ms
      message: 'network-check-target-ip-10-0-138-34: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-28T19:59:00Z"
    - latency: 1.213852ms
      message: 'network-check-target-ip-10-0-138-34: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-28T19:58:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-28T19:24:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-34-to-network-check-target-ip-10-0-139-184
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-34.ec2.internal
      uid: 9cf3a5f0-f30e-40a8-b273-54d70220112a
    resourceVersion: "32927"
    uid: 22cfe722-6a4d-45ec-94e6-1e40c32d3f47
  spec:
    sourcePod: network-check-source-8894fc9bd-8fxnw
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-28T19:32:00Z"
      message: 'network-check-target-ip-10-0-139-184: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.292558ms
      message: 'network-check-target-ip-10-0-139-184: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-28T20:07:00Z"
    - latency: 2.435284ms
      message: 'network-check-target-ip-10-0-139-184: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-28T20:06:00Z"
    - latency: 2.301746ms
      message: 'network-check-target-ip-10-0-139-184: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-28T20:05:00Z"
    - latency: 2.336889ms
      message: 'network-check-target-ip-10-0-139-184: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-28T20:04:00Z"
    - latency: 2.20464ms
      message: 'network-check-target-ip-10-0-139-184: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-28T20:03:00Z"
    - latency: 2.228963ms
      message: 'network-check-target-ip-10-0-139-184: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-28T20:02:00Z"
    - latency: 2.184371ms
      message: 'network-check-target-ip-10-0-139-184: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-28T20:01:00Z"
    - latency: 2.353966ms
      message: 'network-check-target-ip-10-0-139-184: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-28T20:00:00Z"
    - latency: 2.343625ms
      message: 'network-check-target-ip-10-0-139-184: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-28T19:59:00Z"
    - latency: 2.450067ms
      message: 'network-check-target-ip-10-0-139-184: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-28T19:58:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-28T19:24:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-34-to-network-check-target-ip-10-0-140-230
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-34.ec2.internal
      uid: 9cf3a5f0-f30e-40a8-b273-54d70220112a
    resourceVersion: "32928"
    uid: 94932da7-2d29-4e88-9386-6da38aea8961
  spec:
    sourcePod: network-check-source-8894fc9bd-8fxnw
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-28T19:32:00Z"
      message: 'network-check-target-ip-10-0-140-230: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.2897ms
      message: 'network-check-target-ip-10-0-140-230: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-28T20:07:00Z"
    - latency: 2.299581ms
      message: 'network-check-target-ip-10-0-140-230: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-28T20:06:00Z"
    - latency: 2.089803ms
      message: 'network-check-target-ip-10-0-140-230: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-28T20:05:00Z"
    - latency: 2.224593ms
      message: 'network-check-target-ip-10-0-140-230: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-28T20:04:00Z"
    - latency: 1.952943ms
      message: 'network-check-target-ip-10-0-140-230: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-28T20:03:00Z"
    - latency: 2.238399ms
      message: 'network-check-target-ip-10-0-140-230: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-28T20:02:00Z"
    - latency: 2.091781ms
      message: 'network-check-target-ip-10-0-140-230: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-28T20:01:00Z"
    - latency: 2.264536ms
      message: 'network-check-target-ip-10-0-140-230: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-28T20:00:00Z"
    - latency: 2.486659ms
      message: 'network-check-target-ip-10-0-140-230: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-28T19:59:00Z"
    - latency: 2.150099ms
      message: 'network-check-target-ip-10-0-140-230: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-28T19:58:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-28T19:24:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-34-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-34.ec2.internal
      uid: 9cf3a5f0-f30e-40a8-b273-54d70220112a
    resourceVersion: "32929"
    uid: 006c022b-d897-4c7e-8c2a-ff31cbc8fd1d
  spec:
    sourcePod: network-check-source-8894fc9bd-8fxnw
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-04-28T19:31:00Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 802.896µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-28T20:07:00Z"
    - latency: 1.625925ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-28T20:07:00Z"
    - latency: 797.138µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-28T20:06:00Z"
    - latency: 1.776028ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-28T20:06:00Z"
    - latency: 914.15µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-28T20:05:00Z"
    - latency: 1.692461ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-28T20:05:00Z"
    - latency: 904.804µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-28T20:04:00Z"
    - latency: 1.563982ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-28T20:04:00Z"
    - latency: 838.95µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-28T20:03:00Z"
    - latency: 1.491942ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-28T20:03:00Z"
kind: List
metadata:
  resourceVersion: ""