apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-19T01:15:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-76-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-76.ec2.internal
      uid: 621158ab-357d-486a-bb63-3847ffecd8cf
    resourceVersion: "67035"
    uid: b38badda-8964-461f-b303-9bdd26ec306c
  spec:
    sourcePod: network-check-source-7cbc45fddc-qxlvd
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-19T01:22:39Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.326907ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T01:50:39Z"
    - latency: 951.659µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T01:49:39Z"
    - latency: 995.995µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T01:48:39Z"
    - latency: 1.421538ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T01:47:39Z"
    - latency: 1.278295ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T01:46:39Z"
    - latency: 1.009229ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T01:45:39Z"
    - latency: 1.230319ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T01:44:39Z"
    - latency: 1.834678ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T01:43:39Z"
    - latency: 1.748813ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T01:42:39Z"
    - latency: 1.29044ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T01:41:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-19T01:15:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-76-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-76.ec2.internal
      uid: 621158ab-357d-486a-bb63-3847ffecd8cf
    resourceVersion: "68005"
    uid: 4fb170c4-7e20-46f1-b037-aed71a3e42b1
  spec:
    sourcePod: network-check-source-7cbc45fddc-qxlvd
    targetEndpoint: aab14d1037c374fd0a5fbd9790b47334-23caf9c043fe6cd3.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-19T01:21:39Z"
      message: 'load-balancer-api-external: tcp connection to aab14d1037c374fd0a5fbd9790b47334-23caf9c043fe6cd3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.159336ms
      message: 'load-balancer-api-external: tcp connection to aab14d1037c374fd0a5fbd9790b47334-23caf9c043fe6cd3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T01:51:39Z"
    - latency: 8.6167ms
      message: 'load-balancer-api-external: resolved host name aab14d1037c374fd0a5fbd9790b47334-23caf9c043fe6cd3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T01:51:39Z"
    - latency: 6.883118ms
      message: 'load-balancer-api-external: tcp connection to aab14d1037c374fd0a5fbd9790b47334-23caf9c043fe6cd3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T01:50:39Z"
    - latency: 7.134494ms
      message: 'load-balancer-api-external: resolved host name aab14d1037c374fd0a5fbd9790b47334-23caf9c043fe6cd3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T01:50:39Z"
    - latency: 6.429931ms
      message: 'load-balancer-api-external: tcp connection to aab14d1037c374fd0a5fbd9790b47334-23caf9c043fe6cd3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T01:49:39Z"
    - latency: 9.606893ms
      message: 'load-balancer-api-external: resolved host name aab14d1037c374fd0a5fbd9790b47334-23caf9c043fe6cd3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T01:49:39Z"
    - latency: 5.349257ms
      message: 'load-balancer-api-external: tcp connection to aab14d1037c374fd0a5fbd9790b47334-23caf9c043fe6cd3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T01:48:39Z"
    - latency: 8.412872ms
      message: 'load-balancer-api-external: resolved host name aab14d1037c374fd0a5fbd9790b47334-23caf9c043fe6cd3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T01:48:39Z"
    - latency: 5.872784ms
      message: 'load-balancer-api-external: tcp connection to aab14d1037c374fd0a5fbd9790b47334-23caf9c043fe6cd3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T01:47:39Z"
    - latency: 7.833434ms
      message: 'load-balancer-api-external: resolved host name aab14d1037c374fd0a5fbd9790b47334-23caf9c043fe6cd3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T01:47:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-19T01:15:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-76-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-76.ec2.internal
      uid: 621158ab-357d-486a-bb63-3847ffecd8cf
    resourceVersion: "68004"
    uid: fac8510d-6c5a-48ee-b0c1-0c53c7fc4a4c
  spec:
    sourcePod: network-check-source-7cbc45fddc-qxlvd
    targetEndpoint: aab14d1037c374fd0a5fbd9790b47334-23caf9c043fe6cd3.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-19T01:21:39Z"
      message: 'load-balancer-api-internal: tcp connection to aab14d1037c374fd0a5fbd9790b47334-23caf9c043fe6cd3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.062297ms
      message: 'load-balancer-api-internal: tcp connection to aab14d1037c374fd0a5fbd9790b47334-23caf9c043fe6cd3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T01:51:39Z"
    - latency: 8.542635ms
      message: 'load-balancer-api-internal: resolved host name aab14d1037c374fd0a5fbd9790b47334-23caf9c043fe6cd3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T01:51:39Z"
    - latency: 5.890998ms
      message: 'load-balancer-api-internal: tcp connection to aab14d1037c374fd0a5fbd9790b47334-23caf9c043fe6cd3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T01:50:39Z"
    - latency: 7.209722ms
      message: 'load-balancer-api-internal: resolved host name aab14d1037c374fd0a5fbd9790b47334-23caf9c043fe6cd3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T01:50:39Z"
    - latency: 6.495005ms
      message: 'load-balancer-api-internal: tcp connection to aab14d1037c374fd0a5fbd9790b47334-23caf9c043fe6cd3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T01:49:39Z"
    - latency: 9.719255ms
      message: 'load-balancer-api-internal: resolved host name aab14d1037c374fd0a5fbd9790b47334-23caf9c043fe6cd3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T01:49:39Z"
    - latency: 5.378619ms
      message: 'load-balancer-api-internal: tcp connection to aab14d1037c374fd0a5fbd9790b47334-23caf9c043fe6cd3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T01:48:39Z"
    - latency: 8.340757ms
      message: 'load-balancer-api-internal: resolved host name aab14d1037c374fd0a5fbd9790b47334-23caf9c043fe6cd3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T01:48:39Z"
    - latency: 4.740627ms
      message: 'load-balancer-api-internal: tcp connection to aab14d1037c374fd0a5fbd9790b47334-23caf9c043fe6cd3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T01:47:39Z"
    - latency: 7.91646ms
      message: 'load-balancer-api-internal: resolved host name aab14d1037c374fd0a5fbd9790b47334-23caf9c043fe6cd3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T01:47:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-19T01:15:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-76-to-network-check-target-ip-10-0-129-113
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-76.ec2.internal
      uid: 621158ab-357d-486a-bb63-3847ffecd8cf
    resourceVersion: "67036"
    uid: dacd6556-74c6-46e6-902c-2b1348b3a8b1
  spec:
    sourcePod: network-check-source-7cbc45fddc-qxlvd
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-19T01:22:39Z"
      message: 'network-check-target-ip-10-0-129-113: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.16314ms
      message: 'network-check-target-ip-10-0-129-113: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T01:50:39Z"
    - latency: 2.142532ms
      message: 'network-check-target-ip-10-0-129-113: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T01:49:39Z"
    - latency: 2.195544ms
      message: 'network-check-target-ip-10-0-129-113: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T01:48:39Z"
    - latency: 2.535638ms
      message: 'network-check-target-ip-10-0-129-113: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T01:47:39Z"
    - latency: 2.19363ms
      message: 'network-check-target-ip-10-0-129-113: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T01:46:39Z"
    - latency: 2.277546ms
      message: 'network-check-target-ip-10-0-129-113: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T01:45:39Z"
    - latency: 2.629098ms
      message: 'network-check-target-ip-10-0-129-113: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T01:44:39Z"
    - latency: 2.339405ms
      message: 'network-check-target-ip-10-0-129-113: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T01:43:39Z"
    - latency: 2.131439ms
      message: 'network-check-target-ip-10-0-129-113: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T01:42:39Z"
    - latency: 2.389855ms
      message: 'network-check-target-ip-10-0-129-113: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T01:41:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-19T01:15:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-76-to-network-check-target-ip-10-0-131-76
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-76.ec2.internal
      uid: 621158ab-357d-486a-bb63-3847ffecd8cf
    resourceVersion: "67034"
    uid: 7819cd61-2380-484f-8f0a-e4fc3cba1bda
  spec:
    sourcePod: network-check-source-7cbc45fddc-qxlvd
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-19T01:22:39Z"
      message: 'network-check-target-ip-10-0-131-76: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 947.603µs
      message: 'network-check-target-ip-10-0-131-76: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T01:50:39Z"
    - latency: 1.145548ms
      message: 'network-check-target-ip-10-0-131-76: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T01:49:39Z"
    - latency: 1.036256ms
      message: 'network-check-target-ip-10-0-131-76: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T01:48:39Z"
    - latency: 1.132573ms
      message: 'network-check-target-ip-10-0-131-76: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T01:47:39Z"
    - latency: 921.036µs
      message: 'network-check-target-ip-10-0-131-76: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T01:46:39Z"
    - latency: 1.054949ms
      message: 'network-check-target-ip-10-0-131-76: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T01:45:39Z"
    - latency: 1.172388ms
      message: 'network-check-target-ip-10-0-131-76: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T01:44:39Z"
    - latency: 939.708µs
      message: 'network-check-target-ip-10-0-131-76: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T01:43:39Z"
    - latency: 1.049965ms
      message: 'network-check-target-ip-10-0-131-76: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T01:42:39Z"
    - latency: 1.119859ms
      message: 'network-check-target-ip-10-0-131-76: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T01:41:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-19T01:15:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-76-to-network-check-target-ip-10-0-143-9
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-76.ec2.internal
      uid: 621158ab-357d-486a-bb63-3847ffecd8cf
    resourceVersion: "67037"
    uid: 8e48871f-c8b9-414d-bc8c-73cf1110b65a
  spec:
    sourcePod: network-check-source-7cbc45fddc-qxlvd
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-19T01:22:39Z"
      message: 'network-check-target-ip-10-0-143-9: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.931148ms
      message: 'network-check-target-ip-10-0-143-9: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T01:50:39Z"
    - latency: 2.224279ms
      message: 'network-check-target-ip-10-0-143-9: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T01:49:39Z"
    - latency: 2.050097ms
      message: 'network-check-target-ip-10-0-143-9: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T01:48:39Z"
    - latency: 2.390971ms
      message: 'network-check-target-ip-10-0-143-9: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T01:47:39Z"
    - latency: 2.215229ms
      message: 'network-check-target-ip-10-0-143-9: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T01:46:39Z"
    - latency: 1.993295ms
      message: 'network-check-target-ip-10-0-143-9: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T01:45:39Z"
    - latency: 1.999853ms
      message: 'network-check-target-ip-10-0-143-9: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T01:44:39Z"
    - latency: 2.143687ms
      message: 'network-check-target-ip-10-0-143-9: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T01:43:39Z"
    - latency: 2.363391ms
      message: 'network-check-target-ip-10-0-143-9: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T01:42:39Z"
    - latency: 2.395306ms
      message: 'network-check-target-ip-10-0-143-9: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T01:41:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-19T01:15:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-76-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-76.ec2.internal
      uid: 621158ab-357d-486a-bb63-3847ffecd8cf
    resourceVersion: "68003"
    uid: dc48e81c-85f8-4926-9625-d0d708a30398
  spec:
    sourcePod: network-check-source-7cbc45fddc-qxlvd
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-19T01:21:39Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 923.514µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T01:51:39Z"
    - latency: 2.166528ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T01:51:39Z"
    - latency: 944.002µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T01:50:39Z"
    - latency: 2.03336ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T01:50:39Z"
    - latency: 974.245µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T01:49:39Z"
    - latency: 1.778243ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T01:49:39Z"
    - latency: 1.060792ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T01:48:39Z"
    - latency: 1.768548ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T01:48:39Z"
    - latency: 1.065355ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T01:47:39Z"
    - latency: 2.378097ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T01:47:39Z"
kind: List
metadata:
  resourceVersion: ""