apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T04:23:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-6-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-6.ec2.internal
      uid: 748c63a2-2357-48c9-b19f-686de08f9219
    resourceVersion: "26950"
    uid: e6f24d54-9ebe-46cf-9469-b593914e8abd
  spec:
    sourcePod: network-check-source-7cbc45fddc-wcgqn
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T04:30:44Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.064043ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T04:37:44Z"
    - latency: 1.142409ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T04:36:44Z"
    - latency: 1.170803ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T04:35:44Z"
    - latency: 1.190406ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T04:34:44Z"
    - latency: 923.081µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T04:33:44Z"
    - latency: 1.028749ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T04:32:44Z"
    - latency: 1.65337ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T04:31:44Z"
    - latency: 1.012065ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T04:30:44Z"
    - latency: 1.040068ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T04:29:44Z"
    - latency: 1.070077ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T04:28:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T04:23:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-6-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-6.ec2.internal
      uid: 748c63a2-2357-48c9-b19f-686de08f9219
    resourceVersion: "25414"
    uid: 4f04300b-db84-48fc-9cfc-2431b788d799
  spec:
    sourcePod: network-check-source-7cbc45fddc-wcgqn
    targetEndpoint: ada32b366948748e093dc56b1d70c6ec-1b68452e06fe55ff.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T04:29:44Z"
      message: 'load-balancer-api-external: tcp connection to ada32b366948748e093dc56b1d70c6ec-1b68452e06fe55ff.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.379441ms
      message: 'load-balancer-api-external: tcp connection to ada32b366948748e093dc56b1d70c6ec-1b68452e06fe55ff.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T04:35:44Z"
    - latency: 15.323983ms
      message: 'load-balancer-api-external: resolved host name ada32b366948748e093dc56b1d70c6ec-1b68452e06fe55ff.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T04:35:44Z"
    - latency: 4.466582ms
      message: 'load-balancer-api-external: tcp connection to ada32b366948748e093dc56b1d70c6ec-1b68452e06fe55ff.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T04:34:44Z"
    - latency: 9.59638ms
      message: 'load-balancer-api-external: resolved host name ada32b366948748e093dc56b1d70c6ec-1b68452e06fe55ff.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T04:34:44Z"
    - latency: 3.794479ms
      message: 'load-balancer-api-external: tcp connection to ada32b366948748e093dc56b1d70c6ec-1b68452e06fe55ff.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T04:33:44Z"
    - latency: 9.795462ms
      message: 'load-balancer-api-external: resolved host name ada32b366948748e093dc56b1d70c6ec-1b68452e06fe55ff.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T04:33:44Z"
    - latency: 5.409638ms
      message: 'load-balancer-api-external: tcp connection to ada32b366948748e093dc56b1d70c6ec-1b68452e06fe55ff.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T04:32:44Z"
    - latency: 8.635793ms
      message: 'load-balancer-api-external: resolved host name ada32b366948748e093dc56b1d70c6ec-1b68452e06fe55ff.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T04:32:44Z"
    - latency: 4.967388ms
      message: 'load-balancer-api-external: tcp connection to ada32b366948748e093dc56b1d70c6ec-1b68452e06fe55ff.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T04:31:44Z"
    - latency: 8.701014ms
      message: 'load-balancer-api-external: resolved host name ada32b366948748e093dc56b1d70c6ec-1b68452e06fe55ff.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T04:31:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T04:23:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-6-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-6.ec2.internal
      uid: 748c63a2-2357-48c9-b19f-686de08f9219
    resourceVersion: "25415"
    uid: a4dfe682-8322-49f0-8fa3-e9c7ad01d793
  spec:
    sourcePod: network-check-source-7cbc45fddc-wcgqn
    targetEndpoint: ada32b366948748e093dc56b1d70c6ec-1b68452e06fe55ff.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T04:29:44Z"
      message: 'load-balancer-api-internal: tcp connection to ada32b366948748e093dc56b1d70c6ec-1b68452e06fe55ff.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.407146ms
      message: 'load-balancer-api-internal: tcp connection to ada32b366948748e093dc56b1d70c6ec-1b68452e06fe55ff.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T04:35:44Z"
    - latency: 15.296733ms
      message: 'load-balancer-api-internal: resolved host name ada32b366948748e093dc56b1d70c6ec-1b68452e06fe55ff.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T04:35:44Z"
    - latency: 4.533521ms
      message: 'load-balancer-api-internal: tcp connection to ada32b366948748e093dc56b1d70c6ec-1b68452e06fe55ff.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T04:34:44Z"
    - latency: 9.547899ms
      message: 'load-balancer-api-internal: resolved host name ada32b366948748e093dc56b1d70c6ec-1b68452e06fe55ff.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T04:34:44Z"
    - latency: 3.785597ms
      message: 'load-balancer-api-internal: tcp connection to ada32b366948748e093dc56b1d70c6ec-1b68452e06fe55ff.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T04:33:44Z"
    - latency: 9.894769ms
      message: 'load-balancer-api-internal: resolved host name ada32b366948748e093dc56b1d70c6ec-1b68452e06fe55ff.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T04:33:44Z"
    - latency: 5.360725ms
      message: 'load-balancer-api-internal: tcp connection to ada32b366948748e093dc56b1d70c6ec-1b68452e06fe55ff.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T04:32:44Z"
    - latency: 8.705043ms
      message: 'load-balancer-api-internal: resolved host name ada32b366948748e093dc56b1d70c6ec-1b68452e06fe55ff.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T04:32:44Z"
    - latency: 5.018299ms
      message: 'load-balancer-api-internal: tcp connection to ada32b366948748e093dc56b1d70c6ec-1b68452e06fe55ff.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T04:31:44Z"
    - latency: 8.680889ms
      message: 'load-balancer-api-internal: resolved host name ada32b366948748e093dc56b1d70c6ec-1b68452e06fe55ff.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T04:31:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T04:23:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-6-to-network-check-target-ip-10-0-132-31
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-6.ec2.internal
      uid: 748c63a2-2357-48c9-b19f-686de08f9219
    resourceVersion: "26949"
    uid: 596fa042-fa2b-42c5-86f2-e0f2d7317ffe
  spec:
    sourcePod: network-check-source-7cbc45fddc-wcgqn
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T04:30:44Z"
      message: 'network-check-target-ip-10-0-132-31: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.286911ms
      message: 'network-check-target-ip-10-0-132-31: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T04:37:44Z"
    - latency: 2.333856ms
      message: 'network-check-target-ip-10-0-132-31: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T04:36:44Z"
    - latency: 2.405312ms
      message: 'network-check-target-ip-10-0-132-31: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T04:35:44Z"
    - latency: 2.588854ms
      message: 'network-check-target-ip-10-0-132-31: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T04:34:44Z"
    - latency: 2.131166ms
      message: 'network-check-target-ip-10-0-132-31: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T04:33:44Z"
    - latency: 2.467947ms
      message: 'network-check-target-ip-10-0-132-31: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T04:32:44Z"
    - latency: 2.140949ms
      message: 'network-check-target-ip-10-0-132-31: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T04:31:44Z"
    - latency: 2.32129ms
      message: 'network-check-target-ip-10-0-132-31: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T04:30:44Z"
    - latency: 2.231538ms
      message: 'network-check-target-ip-10-0-132-31: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T04:29:44Z"
    - latency: 2.315753ms
      message: 'network-check-target-ip-10-0-132-31: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T04:28:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T04:23:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-6-to-network-check-target-ip-10-0-134-127
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-6.ec2.internal
      uid: 748c63a2-2357-48c9-b19f-686de08f9219
    resourceVersion: "26948"
    uid: fe4bef6e-28d6-4f1a-baac-4f3071c94753
  spec:
    sourcePod: network-check-source-7cbc45fddc-wcgqn
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T04:30:44Z"
      message: 'network-check-target-ip-10-0-134-127: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.406929ms
      message: 'network-check-target-ip-10-0-134-127: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T04:37:44Z"
    - latency: 2.474756ms
      message: 'network-check-target-ip-10-0-134-127: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T04:36:44Z"
    - latency: 2.309946ms
      message: 'network-check-target-ip-10-0-134-127: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T04:35:44Z"
    - latency: 2.541071ms
      message: 'network-check-target-ip-10-0-134-127: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T04:34:44Z"
    - latency: 1.878202ms
      message: 'network-check-target-ip-10-0-134-127: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T04:33:44Z"
    - latency: 2.16257ms
      message: 'network-check-target-ip-10-0-134-127: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T04:32:44Z"
    - latency: 2.407263ms
      message: 'network-check-target-ip-10-0-134-127: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T04:31:44Z"
    - latency: 2.332715ms
      message: 'network-check-target-ip-10-0-134-127: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T04:30:44Z"
    - latency: 2.127457ms
      message: 'network-check-target-ip-10-0-134-127: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T04:29:44Z"
    - latency: 3.070881ms
      message: 'network-check-target-ip-10-0-134-127: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T04:28:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T04:23:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-6-to-network-check-target-ip-10-0-138-6
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-6.ec2.internal
      uid: 748c63a2-2357-48c9-b19f-686de08f9219
    resourceVersion: "26947"
    uid: 31bebb46-ca63-4e12-9f71-d7dcc9e5caf1
  spec:
    sourcePod: network-check-source-7cbc45fddc-wcgqn
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T04:30:44Z"
      message: 'network-check-target-ip-10-0-138-6: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.276737ms
      message: 'network-check-target-ip-10-0-138-6: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T04:37:44Z"
    - latency: 982.744µs
      message: 'network-check-target-ip-10-0-138-6: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T04:36:44Z"
    - latency: 971.511µs
      message: 'network-check-target-ip-10-0-138-6: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T04:35:44Z"
    - latency: 1.232044ms
      message: 'network-check-target-ip-10-0-138-6: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T04:34:44Z"
    - latency: 1.642556ms
      message: 'network-check-target-ip-10-0-138-6: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T04:33:44Z"
    - latency: 1.125237ms
      message: 'network-check-target-ip-10-0-138-6: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T04:32:44Z"
    - latency: 1.256022ms
      message: 'network-check-target-ip-10-0-138-6: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T04:31:44Z"
    - latency: 1.234111ms
      message: 'network-check-target-ip-10-0-138-6: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T04:30:44Z"
    - latency: 1.314795ms
      message: 'network-check-target-ip-10-0-138-6: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T04:29:44Z"
    - latency: 1.936771ms
      message: 'network-check-target-ip-10-0-138-6: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T04:28:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T04:23:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-6-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-6.ec2.internal
      uid: 748c63a2-2357-48c9-b19f-686de08f9219
    resourceVersion: "25413"
    uid: 53973f54-bc01-4b5c-ae5c-04ef8f213443
  spec:
    sourcePod: network-check-source-7cbc45fddc-wcgqn
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T04:29:44Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.323078ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T04:35:44Z"
    - latency: 1.757438ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T04:35:44Z"
    - latency: 891.738µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T04:34:44Z"
    - latency: 2.373112ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T04:34:44Z"
    - latency: 923.541µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T04:33:44Z"
    - latency: 1.728859ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T04:33:44Z"
    - latency: 3.371312ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T04:32:44Z"
    - latency: 1.751374ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T04:32:44Z"
    - latency: 1.072957ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T04:31:44Z"
    - latency: 2.106695ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T04:31:44Z"
kind: List
metadata:
  resourceVersion: ""