apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-24T16:45:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-227-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-227.ec2.internal
      uid: 1e1a213b-9de6-4159-9a13-7c26460ce701
    resourceVersion: "48331"
    uid: e3727bf9-cccc-462a-a00d-30907116ab0c
  spec:
    sourcePod: network-check-source-8894fc9bd-nfd4n
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-04-24T16:52:04Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 967.629µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T17:27:04Z"
    - latency: 1.047729ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T17:26:04Z"
    - latency: 1.293384ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T17:25:04Z"
    - latency: 1.48622ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T17:24:04Z"
    - latency: 1.211472ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T17:23:04Z"
    - latency: 1.011908ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T17:22:04Z"
    - latency: 1.251534ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T17:21:04Z"
    - latency: 1.05115ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T17:20:04Z"
    - latency: 1.18719ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T17:19:04Z"
    - latency: 1.557615ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T17:18:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-24T16:45:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-227-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-227.ec2.internal
      uid: 1e1a213b-9de6-4159-9a13-7c26460ce701
    resourceVersion: "48333"
    uid: afcdbd35-5908-4b84-bd4e-a6d0744f7b3c
  spec:
    sourcePod: network-check-source-8894fc9bd-nfd4n
    targetEndpoint: afefc2d63016a48a7b3bc98b036aee43-752635f0a1cd7f42.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-04-24T16:51:04Z"
      message: 'load-balancer-api-external: tcp connection to afefc2d63016a48a7b3bc98b036aee43-752635f0a1cd7f42.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.488657ms
      message: 'load-balancer-api-external: tcp connection to afefc2d63016a48a7b3bc98b036aee43-752635f0a1cd7f42.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T17:27:04Z"
    - latency: 8.627306ms
      message: 'load-balancer-api-external: resolved host name afefc2d63016a48a7b3bc98b036aee43-752635f0a1cd7f42.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-24T17:27:04Z"
    - latency: 4.31027ms
      message: 'load-balancer-api-external: tcp connection to afefc2d63016a48a7b3bc98b036aee43-752635f0a1cd7f42.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T17:26:04Z"
    - latency: 6.336124ms
      message: 'load-balancer-api-external: resolved host name afefc2d63016a48a7b3bc98b036aee43-752635f0a1cd7f42.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-24T17:26:04Z"
    - latency: 3.650711ms
      message: 'load-balancer-api-external: tcp connection to afefc2d63016a48a7b3bc98b036aee43-752635f0a1cd7f42.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T17:25:04Z"
    - latency: 7.93459ms
      message: 'load-balancer-api-external: resolved host name afefc2d63016a48a7b3bc98b036aee43-752635f0a1cd7f42.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-24T17:25:04Z"
    - latency: 4.511586ms
      message: 'load-balancer-api-external: tcp connection to afefc2d63016a48a7b3bc98b036aee43-752635f0a1cd7f42.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T17:24:04Z"
    - latency: 6.930469ms
      message: 'load-balancer-api-external: resolved host name afefc2d63016a48a7b3bc98b036aee43-752635f0a1cd7f42.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-24T17:24:04Z"
    - latency: 3.954845ms
      message: 'load-balancer-api-external: tcp connection to afefc2d63016a48a7b3bc98b036aee43-752635f0a1cd7f42.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T17:23:04Z"
    - latency: 6.948904ms
      message: 'load-balancer-api-external: resolved host name afefc2d63016a48a7b3bc98b036aee43-752635f0a1cd7f42.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-24T17:23:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-24T16:45:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-227-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-227.ec2.internal
      uid: 1e1a213b-9de6-4159-9a13-7c26460ce701
    resourceVersion: "48332"
    uid: 5105ed25-616b-40e7-9f09-30423de610ae
  spec:
    sourcePod: network-check-source-8894fc9bd-nfd4n
    targetEndpoint: afefc2d63016a48a7b3bc98b036aee43-752635f0a1cd7f42.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-04-24T16:51:04Z"
      message: 'load-balancer-api-internal: tcp connection to afefc2d63016a48a7b3bc98b036aee43-752635f0a1cd7f42.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.633541ms
      message: 'load-balancer-api-internal: tcp connection to afefc2d63016a48a7b3bc98b036aee43-752635f0a1cd7f42.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T17:27:04Z"
    - latency: 8.566368ms
      message: 'load-balancer-api-internal: resolved host name afefc2d63016a48a7b3bc98b036aee43-752635f0a1cd7f42.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-24T17:27:04Z"
    - latency: 4.302277ms
      message: 'load-balancer-api-internal: tcp connection to afefc2d63016a48a7b3bc98b036aee43-752635f0a1cd7f42.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T17:26:04Z"
    - latency: 6.400805ms
      message: 'load-balancer-api-internal: resolved host name afefc2d63016a48a7b3bc98b036aee43-752635f0a1cd7f42.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-24T17:26:04Z"
    - latency: 4.452988ms
      message: 'load-balancer-api-internal: tcp connection to afefc2d63016a48a7b3bc98b036aee43-752635f0a1cd7f42.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T17:25:04Z"
    - latency: 7.963482ms
      message: 'load-balancer-api-internal: resolved host name afefc2d63016a48a7b3bc98b036aee43-752635f0a1cd7f42.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-24T17:25:04Z"
    - latency: 4.535296ms
      message: 'load-balancer-api-internal: tcp connection to afefc2d63016a48a7b3bc98b036aee43-752635f0a1cd7f42.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T17:24:04Z"
    - latency: 7.074227ms
      message: 'load-balancer-api-internal: resolved host name afefc2d63016a48a7b3bc98b036aee43-752635f0a1cd7f42.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-24T17:24:04Z"
    - latency: 4.051971ms
      message: 'load-balancer-api-internal: tcp connection to afefc2d63016a48a7b3bc98b036aee43-752635f0a1cd7f42.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T17:23:04Z"
    - latency: 6.863378ms
      message: 'load-balancer-api-internal: resolved host name afefc2d63016a48a7b3bc98b036aee43-752635f0a1cd7f42.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-24T17:23:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-24T16:45:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-227-to-network-check-target-ip-10-0-129-227
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-227.ec2.internal
      uid: 1e1a213b-9de6-4159-9a13-7c26460ce701
    resourceVersion: "48327"
    uid: 7d9e4730-33f4-43ff-88bf-0ba12fa455fe
  spec:
    sourcePod: network-check-source-8894fc9bd-nfd4n
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-24T16:52:04Z"
      message: 'network-check-target-ip-10-0-129-227: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.139364ms
      message: 'network-check-target-ip-10-0-129-227: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T17:27:04Z"
    - latency: 808.258µs
      message: 'network-check-target-ip-10-0-129-227: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T17:26:04Z"
    - latency: 1.125938ms
      message: 'network-check-target-ip-10-0-129-227: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T17:25:04Z"
    - latency: 912.529µs
      message: 'network-check-target-ip-10-0-129-227: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T17:24:04Z"
    - latency: 939.871µs
      message: 'network-check-target-ip-10-0-129-227: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T17:23:04Z"
    - latency: 832.364µs
      message: 'network-check-target-ip-10-0-129-227: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T17:22:04Z"
    - latency: 892.651µs
      message: 'network-check-target-ip-10-0-129-227: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T17:21:04Z"
    - latency: 739.216µs
      message: 'network-check-target-ip-10-0-129-227: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T17:20:04Z"
    - latency: 821.253µs
      message: 'network-check-target-ip-10-0-129-227: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T17:19:04Z"
    - latency: 833.699µs
      message: 'network-check-target-ip-10-0-129-227: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T17:18:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-24T16:45:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-227-to-network-check-target-ip-10-0-137-69
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-227.ec2.internal
      uid: 1e1a213b-9de6-4159-9a13-7c26460ce701
    resourceVersion: "48329"
    uid: 5789c85d-d126-4eef-b944-35237fc85a4e
  spec:
    sourcePod: network-check-source-8894fc9bd-nfd4n
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-24T16:52:04Z"
      message: 'network-check-target-ip-10-0-137-69: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.047595ms
      message: 'network-check-target-ip-10-0-137-69: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T17:27:04Z"
    - latency: 1.711396ms
      message: 'network-check-target-ip-10-0-137-69: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T17:26:04Z"
    - latency: 2.003992ms
      message: 'network-check-target-ip-10-0-137-69: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T17:25:04Z"
    - latency: 2.079771ms
      message: 'network-check-target-ip-10-0-137-69: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T17:24:04Z"
    - latency: 2.047869ms
      message: 'network-check-target-ip-10-0-137-69: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T17:23:04Z"
    - latency: 2.209914ms
      message: 'network-check-target-ip-10-0-137-69: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T17:22:04Z"
    - latency: 2.207079ms
      message: 'network-check-target-ip-10-0-137-69: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T17:21:04Z"
    - latency: 2.266528ms
      message: 'network-check-target-ip-10-0-137-69: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T17:20:04Z"
    - latency: 1.805826ms
      message: 'network-check-target-ip-10-0-137-69: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T17:19:04Z"
    - latency: 1.90172ms
      message: 'network-check-target-ip-10-0-137-69: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T17:18:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-24T16:45:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-227-to-network-check-target-ip-10-0-139-51
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-227.ec2.internal
      uid: 1e1a213b-9de6-4159-9a13-7c26460ce701
    resourceVersion: "48328"
    uid: fed2276d-0d8f-4f65-a3f5-d414fd61f89b
  spec:
    sourcePod: network-check-source-8894fc9bd-nfd4n
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-24T16:52:04Z"
      message: 'network-check-target-ip-10-0-139-51: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.606675ms
      message: 'network-check-target-ip-10-0-139-51: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T17:27:04Z"
    - latency: 2.07586ms
      message: 'network-check-target-ip-10-0-139-51: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T17:26:04Z"
    - latency: 1.90712ms
      message: 'network-check-target-ip-10-0-139-51: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T17:25:04Z"
    - latency: 2.078491ms
      message: 'network-check-target-ip-10-0-139-51: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T17:24:04Z"
    - latency: 2.144408ms
      message: 'network-check-target-ip-10-0-139-51: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T17:23:04Z"
    - latency: 1.953679ms
      message: 'network-check-target-ip-10-0-139-51: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T17:22:04Z"
    - latency: 1.955147ms
      message: 'network-check-target-ip-10-0-139-51: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T17:21:04Z"
    - latency: 1.975697ms
      message: 'network-check-target-ip-10-0-139-51: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T17:20:04Z"
    - latency: 1.934963ms
      message: 'network-check-target-ip-10-0-139-51: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T17:19:04Z"
    - latency: 1.850698ms
      message: 'network-check-target-ip-10-0-139-51: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T17:18:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-24T16:45:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-227-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-227.ec2.internal
      uid: 1e1a213b-9de6-4159-9a13-7c26460ce701
    resourceVersion: "48330"
    uid: cdac437e-88ed-4c21-9b67-e478878e7688
  spec:
    sourcePod: network-check-source-8894fc9bd-nfd4n
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-04-24T16:51:04Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 784.383µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T17:27:04Z"
    - latency: 1.981191ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-24T17:27:04Z"
    - latency: 841.643µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T17:26:04Z"
    - latency: 1.943293ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-24T17:26:04Z"
    - latency: 801.527µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T17:25:04Z"
    - latency: 1.933201ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-24T17:25:04Z"
    - latency: 827.988µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T17:24:04Z"
    - latency: 1.680879ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-24T17:24:04Z"
    - latency: 1.301211ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T17:23:04Z"
    - latency: 1.687551ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-24T17:23:04Z"
kind: List
metadata:
  resourceVersion: ""