apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T17:44:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-161-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-161.ec2.internal
      uid: 976ec2b5-cbfd-4f17-8e55-69df6d558271
    resourceVersion: "65565"
    uid: c9ea3bcb-de34-4805-b215-619748da0613
  spec:
    sourcePod: network-check-source-7d88cb55d8-djj62
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T17:51:11Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.083383ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:26:11Z"
    - latency: 958.564µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:25:11Z"
    - latency: 1.262776ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:24:11Z"
    - latency: 1.143919ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:23:11Z"
    - latency: 1.021705ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:22:11Z"
    - latency: 1.683696ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:21:11Z"
    - latency: 1.225351ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:20:11Z"
    - latency: 1.552564ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:19:11Z"
    - latency: 1.08296ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:18:11Z"
    - latency: 1.460261ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:17:11Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T17:44:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-161-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-161.ec2.internal
      uid: 976ec2b5-cbfd-4f17-8e55-69df6d558271
    resourceVersion: "65568"
    uid: 84bbaa1b-b151-4bd7-8b75-d9333f8facea
  spec:
    sourcePod: network-check-source-7d88cb55d8-djj62
    targetEndpoint: a07bb7dda2c11402ca05d038e3941a55-8ed18230c20ad231.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T17:50:11Z"
      message: 'load-balancer-api-external: tcp connection to a07bb7dda2c11402ca05d038e3941a55-8ed18230c20ad231.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.20565ms
      message: 'load-balancer-api-external: tcp connection to a07bb7dda2c11402ca05d038e3941a55-8ed18230c20ad231.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:26:11Z"
    - latency: 8.787954ms
      message: 'load-balancer-api-external: resolved host name a07bb7dda2c11402ca05d038e3941a55-8ed18230c20ad231.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T18:26:11Z"
    - latency: 4.894246ms
      message: 'load-balancer-api-external: tcp connection to a07bb7dda2c11402ca05d038e3941a55-8ed18230c20ad231.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:25:11Z"
    - latency: 7.217007ms
      message: 'load-balancer-api-external: resolved host name a07bb7dda2c11402ca05d038e3941a55-8ed18230c20ad231.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T18:25:11Z"
    - latency: 4.875503ms
      message: 'load-balancer-api-external: tcp connection to a07bb7dda2c11402ca05d038e3941a55-8ed18230c20ad231.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:24:11Z"
    - latency: 8.003146ms
      message: 'load-balancer-api-external: resolved host name a07bb7dda2c11402ca05d038e3941a55-8ed18230c20ad231.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T18:24:11Z"
    - latency: 5.20287ms
      message: 'load-balancer-api-external: tcp connection to a07bb7dda2c11402ca05d038e3941a55-8ed18230c20ad231.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:23:11Z"
    - latency: 8.12038ms
      message: 'load-balancer-api-external: resolved host name a07bb7dda2c11402ca05d038e3941a55-8ed18230c20ad231.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T18:23:11Z"
    - latency: 3.750084ms
      message: 'load-balancer-api-external: tcp connection to a07bb7dda2c11402ca05d038e3941a55-8ed18230c20ad231.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:22:11Z"
    - latency: 7.995048ms
      message: 'load-balancer-api-external: resolved host name a07bb7dda2c11402ca05d038e3941a55-8ed18230c20ad231.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T18:22:11Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T17:44:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-161-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-161.ec2.internal
      uid: 976ec2b5-cbfd-4f17-8e55-69df6d558271
    resourceVersion: "65567"
    uid: 7be5f037-ac6c-45c1-a025-56b2b2783b0d
  spec:
    sourcePod: network-check-source-7d88cb55d8-djj62
    targetEndpoint: a07bb7dda2c11402ca05d038e3941a55-8ed18230c20ad231.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T17:50:11Z"
      message: 'load-balancer-api-internal: tcp connection to a07bb7dda2c11402ca05d038e3941a55-8ed18230c20ad231.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.958592ms
      message: 'load-balancer-api-internal: tcp connection to a07bb7dda2c11402ca05d038e3941a55-8ed18230c20ad231.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:26:11Z"
    - latency: 8.701669ms
      message: 'load-balancer-api-internal: resolved host name a07bb7dda2c11402ca05d038e3941a55-8ed18230c20ad231.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T18:26:11Z"
    - latency: 4.911426ms
      message: 'load-balancer-api-internal: tcp connection to a07bb7dda2c11402ca05d038e3941a55-8ed18230c20ad231.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:25:11Z"
    - latency: 7.157606ms
      message: 'load-balancer-api-internal: resolved host name a07bb7dda2c11402ca05d038e3941a55-8ed18230c20ad231.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T18:25:11Z"
    - latency: 5.675344ms
      message: 'load-balancer-api-internal: tcp connection to a07bb7dda2c11402ca05d038e3941a55-8ed18230c20ad231.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:24:11Z"
    - latency: 7.947972ms
      message: 'load-balancer-api-internal: resolved host name a07bb7dda2c11402ca05d038e3941a55-8ed18230c20ad231.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T18:24:11Z"
    - latency: 5.156028ms
      message: 'load-balancer-api-internal: tcp connection to a07bb7dda2c11402ca05d038e3941a55-8ed18230c20ad231.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:23:11Z"
    - latency: 8.160646ms
      message: 'load-balancer-api-internal: resolved host name a07bb7dda2c11402ca05d038e3941a55-8ed18230c20ad231.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T18:23:11Z"
    - latency: 3.648073ms
      message: 'load-balancer-api-internal: tcp connection to a07bb7dda2c11402ca05d038e3941a55-8ed18230c20ad231.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:22:11Z"
    - latency: 7.953451ms
      message: 'load-balancer-api-internal: resolved host name a07bb7dda2c11402ca05d038e3941a55-8ed18230c20ad231.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T18:22:11Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T17:44:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-161-to-network-check-target-ip-10-0-139-114
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-161.ec2.internal
      uid: 976ec2b5-cbfd-4f17-8e55-69df6d558271
    resourceVersion: "65563"
    uid: 23f0ac39-77f7-45e0-90c0-26aab4907026
  spec:
    sourcePod: network-check-source-7d88cb55d8-djj62
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T17:51:11Z"
      message: 'network-check-target-ip-10-0-139-114: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.553335ms
      message: 'network-check-target-ip-10-0-139-114: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:26:11Z"
    - latency: 2.910934ms
      message: 'network-check-target-ip-10-0-139-114: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:25:11Z"
    - latency: 2.252035ms
      message: 'network-check-target-ip-10-0-139-114: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:24:11Z"
    - latency: 2.304454ms
      message: 'network-check-target-ip-10-0-139-114: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:23:11Z"
    - latency: 2.603513ms
      message: 'network-check-target-ip-10-0-139-114: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:22:11Z"
    - latency: 2.469978ms
      message: 'network-check-target-ip-10-0-139-114: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:21:11Z"
    - latency: 2.701074ms
      message: 'network-check-target-ip-10-0-139-114: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:20:11Z"
    - latency: 2.188478ms
      message: 'network-check-target-ip-10-0-139-114: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:19:11Z"
    - latency: 2.351899ms
      message: 'network-check-target-ip-10-0-139-114: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:18:11Z"
    - latency: 3.101175ms
      message: 'network-check-target-ip-10-0-139-114: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:17:11Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T17:44:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-161-to-network-check-target-ip-10-0-140-161
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-161.ec2.internal
      uid: 976ec2b5-cbfd-4f17-8e55-69df6d558271
    resourceVersion: "65561"
    uid: 46847cb8-8fd2-4af4-b49f-f1f469eb36ae
  spec:
    sourcePod: network-check-source-7d88cb55d8-djj62
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T17:51:11Z"
      message: 'network-check-target-ip-10-0-140-161: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 964.234µs
      message: 'network-check-target-ip-10-0-140-161: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:26:11Z"
    - latency: 970.681µs
      message: 'network-check-target-ip-10-0-140-161: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:25:11Z"
    - latency: 886.932µs
      message: 'network-check-target-ip-10-0-140-161: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:24:11Z"
    - latency: 903.147µs
      message: 'network-check-target-ip-10-0-140-161: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:23:11Z"
    - latency: 1.434267ms
      message: 'network-check-target-ip-10-0-140-161: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:22:11Z"
    - latency: 1.645684ms
      message: 'network-check-target-ip-10-0-140-161: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:21:11Z"
    - latency: 1.1398ms
      message: 'network-check-target-ip-10-0-140-161: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:20:11Z"
    - latency: 1.442199ms
      message: 'network-check-target-ip-10-0-140-161: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:19:11Z"
    - latency: 1.154562ms
      message: 'network-check-target-ip-10-0-140-161: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:18:11Z"
    - latency: 1.862341ms
      message: 'network-check-target-ip-10-0-140-161: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:17:11Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T17:44:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-161-to-network-check-target-ip-10-0-141-44
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-161.ec2.internal
      uid: 976ec2b5-cbfd-4f17-8e55-69df6d558271
    resourceVersion: "65562"
    uid: 67dc1205-dbde-4cf4-a376-8bb2d277c4f3
  spec:
    sourcePod: network-check-source-7d88cb55d8-djj62
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T17:51:11Z"
      message: 'network-check-target-ip-10-0-141-44: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.561932ms
      message: 'network-check-target-ip-10-0-141-44: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:26:11Z"
    - latency: 2.504972ms
      message: 'network-check-target-ip-10-0-141-44: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:25:11Z"
    - latency: 2.407811ms
      message: 'network-check-target-ip-10-0-141-44: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:24:11Z"
    - latency: 2.700931ms
      message: 'network-check-target-ip-10-0-141-44: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:23:11Z"
    - latency: 2.247166ms
      message: 'network-check-target-ip-10-0-141-44: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:22:11Z"
    - latency: 2.573734ms
      message: 'network-check-target-ip-10-0-141-44: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:21:11Z"
    - latency: 2.748462ms
      message: 'network-check-target-ip-10-0-141-44: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:20:11Z"
    - latency: 2.895485ms
      message: 'network-check-target-ip-10-0-141-44: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:19:11Z"
    - latency: 2.556815ms
      message: 'network-check-target-ip-10-0-141-44: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:18:11Z"
    - latency: 2.525643ms
      message: 'network-check-target-ip-10-0-141-44: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:17:11Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T17:44:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-161-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-161.ec2.internal
      uid: 976ec2b5-cbfd-4f17-8e55-69df6d558271
    resourceVersion: "65564"
    uid: 5f454954-924b-4622-b5fa-d7231e291975
  spec:
    sourcePod: network-check-source-7d88cb55d8-djj62
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T17:50:11Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 825.585µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:26:11Z"
    - latency: 1.969249ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T18:26:11Z"
    - latency: 1.224676ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:25:11Z"
    - latency: 2.022836ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T18:25:11Z"
    - latency: 781.094µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:24:11Z"
    - latency: 2.465095ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T18:24:11Z"
    - latency: 1.204058ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:23:11Z"
    - latency: 1.895917ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T18:23:11Z"
    - latency: 804.315µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:22:11Z"
    - latency: 1.930966ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T18:22:11Z"
kind: List
metadata:
  resourceVersion: ""