apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T13:22:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-48-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-48.ec2.internal
      uid: c5af0b70-1a55-43e1-8d5e-3a41331d13e9
    resourceVersion: "17952"
    uid: 7fb4e2be-29d3-4e7c-b63b-c145ffb3d1c8
  spec:
    sourcePod: network-check-source-7cbc45fddc-9kbhk
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T13:29:52Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.22495ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:36:52Z"
    - latency: 1.069201ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:35:52Z"
    - latency: 930.76µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:34:52Z"
    - latency: 1.228654ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:33:52Z"
    - latency: 889.708µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:32:52Z"
    - latency: 909.525µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:31:52Z"
    - latency: 966.336µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:30:52Z"
    - latency: 1.284ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:29:52Z"
    - latency: 1.208981ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:28:52Z"
    - latency: 994.158µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:27:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T13:22:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-48-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-48.ec2.internal
      uid: c5af0b70-1a55-43e1-8d5e-3a41331d13e9
    resourceVersion: "17055"
    uid: f5a00438-57e0-42ea-9887-909dfff0ccda
  spec:
    sourcePod: network-check-source-7cbc45fddc-9kbhk
    targetEndpoint: adc59ba419ec2463a9c9d475378404b7-51246ca02a0cb872.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T13:28:52Z"
      message: 'load-balancer-api-external: tcp connection to adc59ba419ec2463a9c9d475378404b7-51246ca02a0cb872.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.386129ms
      message: 'load-balancer-api-external: tcp connection to adc59ba419ec2463a9c9d475378404b7-51246ca02a0cb872.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:34:52Z"
    - latency: 6.729381ms
      message: 'load-balancer-api-external: resolved host name adc59ba419ec2463a9c9d475378404b7-51246ca02a0cb872.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T13:34:52Z"
    - latency: 5.479692ms
      message: 'load-balancer-api-external: tcp connection to adc59ba419ec2463a9c9d475378404b7-51246ca02a0cb872.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:33:52Z"
    - latency: 9.00379ms
      message: 'load-balancer-api-external: resolved host name adc59ba419ec2463a9c9d475378404b7-51246ca02a0cb872.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T13:33:52Z"
    - latency: 4.844345ms
      message: 'load-balancer-api-external: tcp connection to adc59ba419ec2463a9c9d475378404b7-51246ca02a0cb872.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:32:52Z"
    - latency: 6.143437ms
      message: 'load-balancer-api-external: resolved host name adc59ba419ec2463a9c9d475378404b7-51246ca02a0cb872.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T13:32:52Z"
    - latency: 5.035736ms
      message: 'load-balancer-api-external: tcp connection to adc59ba419ec2463a9c9d475378404b7-51246ca02a0cb872.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:31:52Z"
    - latency: 6.546405ms
      message: 'load-balancer-api-external: resolved host name adc59ba419ec2463a9c9d475378404b7-51246ca02a0cb872.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T13:31:52Z"
    - latency: 5.012568ms
      message: 'load-balancer-api-external: tcp connection to adc59ba419ec2463a9c9d475378404b7-51246ca02a0cb872.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:30:52Z"
    - latency: 6.629778ms
      message: 'load-balancer-api-external: resolved host name adc59ba419ec2463a9c9d475378404b7-51246ca02a0cb872.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T13:30:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T13:22:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-48-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-48.ec2.internal
      uid: c5af0b70-1a55-43e1-8d5e-3a41331d13e9
    resourceVersion: "17056"
    uid: 6d23992c-e613-4e36-bbb9-eef5984d4f16
  spec:
    sourcePod: network-check-source-7cbc45fddc-9kbhk
    targetEndpoint: adc59ba419ec2463a9c9d475378404b7-51246ca02a0cb872.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T13:28:52Z"
      message: 'load-balancer-api-internal: tcp connection to adc59ba419ec2463a9c9d475378404b7-51246ca02a0cb872.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.760182ms
      message: 'load-balancer-api-internal: tcp connection to adc59ba419ec2463a9c9d475378404b7-51246ca02a0cb872.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:34:52Z"
    - latency: 6.754272ms
      message: 'load-balancer-api-internal: resolved host name adc59ba419ec2463a9c9d475378404b7-51246ca02a0cb872.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T13:34:52Z"
    - latency: 5.505519ms
      message: 'load-balancer-api-internal: tcp connection to adc59ba419ec2463a9c9d475378404b7-51246ca02a0cb872.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:33:52Z"
    - latency: 8.937502ms
      message: 'load-balancer-api-internal: resolved host name adc59ba419ec2463a9c9d475378404b7-51246ca02a0cb872.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T13:33:52Z"
    - latency: 4.986593ms
      message: 'load-balancer-api-internal: tcp connection to adc59ba419ec2463a9c9d475378404b7-51246ca02a0cb872.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:32:52Z"
    - latency: 5.962793ms
      message: 'load-balancer-api-internal: resolved host name adc59ba419ec2463a9c9d475378404b7-51246ca02a0cb872.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T13:32:52Z"
    - latency: 5.019188ms
      message: 'load-balancer-api-internal: tcp connection to adc59ba419ec2463a9c9d475378404b7-51246ca02a0cb872.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:31:52Z"
    - latency: 6.455345ms
      message: 'load-balancer-api-internal: resolved host name adc59ba419ec2463a9c9d475378404b7-51246ca02a0cb872.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T13:31:52Z"
    - latency: 4.886106ms
      message: 'load-balancer-api-internal: tcp connection to adc59ba419ec2463a9c9d475378404b7-51246ca02a0cb872.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:30:52Z"
    - latency: 6.554845ms
      message: 'load-balancer-api-internal: resolved host name adc59ba419ec2463a9c9d475378404b7-51246ca02a0cb872.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T13:30:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T13:22:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-48-to-network-check-target-ip-10-0-129-232
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-48.ec2.internal
      uid: c5af0b70-1a55-43e1-8d5e-3a41331d13e9
    resourceVersion: "17949"
    uid: f96c0b06-d7de-4997-bdca-692a1e8ab23f
  spec:
    sourcePod: network-check-source-7cbc45fddc-9kbhk
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T13:29:52Z"
      message: 'network-check-target-ip-10-0-129-232: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.560513ms
      message: 'network-check-target-ip-10-0-129-232: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:36:52Z"
    - latency: 2.220761ms
      message: 'network-check-target-ip-10-0-129-232: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:35:52Z"
    - latency: 2.562271ms
      message: 'network-check-target-ip-10-0-129-232: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:34:52Z"
    - latency: 2.314283ms
      message: 'network-check-target-ip-10-0-129-232: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:33:52Z"
    - latency: 2.134572ms
      message: 'network-check-target-ip-10-0-129-232: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:32:52Z"
    - latency: 2.397829ms
      message: 'network-check-target-ip-10-0-129-232: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:31:52Z"
    - latency: 2.488039ms
      message: 'network-check-target-ip-10-0-129-232: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:30:52Z"
    - latency: 2.256728ms
      message: 'network-check-target-ip-10-0-129-232: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:29:52Z"
    - latency: 2.516084ms
      message: 'network-check-target-ip-10-0-129-232: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:28:52Z"
    - latency: 2.680117ms
      message: 'network-check-target-ip-10-0-129-232: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:27:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T13:22:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-48-to-network-check-target-ip-10-0-136-52
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-48.ec2.internal
      uid: c5af0b70-1a55-43e1-8d5e-3a41331d13e9
    resourceVersion: "17951"
    uid: 4788588b-2c98-4996-bb27-c951279d3dc2
  spec:
    sourcePod: network-check-source-7cbc45fddc-9kbhk
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T13:29:52Z"
      message: 'network-check-target-ip-10-0-136-52: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 8.234113ms
      message: 'network-check-target-ip-10-0-136-52: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:36:52Z"
    - latency: 2.640842ms
      message: 'network-check-target-ip-10-0-136-52: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:35:52Z"
    - latency: 2.413697ms
      message: 'network-check-target-ip-10-0-136-52: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:34:52Z"
    - latency: 2.316028ms
      message: 'network-check-target-ip-10-0-136-52: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:33:52Z"
    - latency: 1.923257ms
      message: 'network-check-target-ip-10-0-136-52: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:32:52Z"
    - latency: 2.223447ms
      message: 'network-check-target-ip-10-0-136-52: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:31:52Z"
    - latency: 2.509813ms
      message: 'network-check-target-ip-10-0-136-52: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:30:52Z"
    - latency: 2.318875ms
      message: 'network-check-target-ip-10-0-136-52: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:29:52Z"
    - latency: 2.159039ms
      message: 'network-check-target-ip-10-0-136-52: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:28:52Z"
    - latency: 1.91753ms
      message: 'network-check-target-ip-10-0-136-52: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:27:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T13:22:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-48-to-network-check-target-ip-10-0-139-48
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-48.ec2.internal
      uid: c5af0b70-1a55-43e1-8d5e-3a41331d13e9
    resourceVersion: "17950"
    uid: 7b50e2fd-c0f0-476e-b7d4-262d4625626d
  spec:
    sourcePod: network-check-source-7cbc45fddc-9kbhk
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T13:29:52Z"
      message: 'network-check-target-ip-10-0-139-48: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 9.686824ms
      message: 'network-check-target-ip-10-0-139-48: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:36:52Z"
    - latency: 1.507525ms
      message: 'network-check-target-ip-10-0-139-48: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:35:52Z"
    - latency: 1.119346ms
      message: 'network-check-target-ip-10-0-139-48: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:34:52Z"
    - latency: 1.513102ms
      message: 'network-check-target-ip-10-0-139-48: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:33:52Z"
    - latency: 987.965µs
      message: 'network-check-target-ip-10-0-139-48: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:32:52Z"
    - latency: 1.57751ms
      message: 'network-check-target-ip-10-0-139-48: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:31:52Z"
    - latency: 1.317622ms
      message: 'network-check-target-ip-10-0-139-48: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:30:52Z"
    - latency: 975.499µs
      message: 'network-check-target-ip-10-0-139-48: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:29:52Z"
    - latency: 912.771µs
      message: 'network-check-target-ip-10-0-139-48: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:28:52Z"
    - latency: 924.362µs
      message: 'network-check-target-ip-10-0-139-48: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:27:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T13:22:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-48-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-48.ec2.internal
      uid: c5af0b70-1a55-43e1-8d5e-3a41331d13e9
    resourceVersion: "17054"
    uid: e99cd514-8e74-4333-8543-b2054b425a37
  spec:
    sourcePod: network-check-source-7cbc45fddc-9kbhk
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T13:28:52Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 861.268µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:34:52Z"
    - latency: 1.845564ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T13:34:52Z"
    - latency: 779.737µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:33:52Z"
    - latency: 2.021213ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T13:33:52Z"
    - latency: 881.002µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:32:52Z"
    - latency: 1.596821ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T13:32:52Z"
    - latency: 1.155742ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:31:52Z"
    - latency: 1.626596ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T13:31:52Z"
    - latency: 1.186017ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:30:52Z"
    - latency: 1.602744ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T13:30:52Z"
kind: List
metadata:
  resourceVersion: ""