apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T13:17:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-62-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-62.ec2.internal
      uid: 3777ab65-b81e-4ec7-bd5d-2ec753032c26
    resourceVersion: "21759"
    uid: 10456ecb-7643-4e41-bef3-262b691156a4
  spec:
    sourcePod: network-check-source-6f8b768455-chjw7
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T13:24:09Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.648215ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T13:45:09Z"
    - latency: 1.234101ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T13:44:09Z"
    - latency: 814.87µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T13:43:09Z"
    - latency: 1.009976ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T13:42:09Z"
    - latency: 882.6µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T13:41:09Z"
    - latency: 1.205735ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T13:40:09Z"
    - latency: 902.187µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T13:39:09Z"
    - latency: 865.769µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T13:38:09Z"
    - latency: 917.183µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T13:37:09Z"
    - latency: 1.353243ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T13:36:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T13:17:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-62-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-62.ec2.internal
      uid: 3777ab65-b81e-4ec7-bd5d-2ec753032c26
    resourceVersion: "20215"
    uid: d7bc21ca-3043-4986-afdb-b9b76b8d96ce
  spec:
    sourcePod: network-check-source-6f8b768455-chjw7
    targetEndpoint: a9a41377d09754050b5ced07b667c9ec-4c48eb74148e30ab.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T13:23:09Z"
      message: 'load-balancer-api-external: tcp connection to a9a41377d09754050b5ced07b667c9ec-4c48eb74148e30ab.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.732374ms
      message: 'load-balancer-api-external: tcp connection to a9a41377d09754050b5ced07b667c9ec-4c48eb74148e30ab.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T13:41:09Z"
    - latency: 6.762445ms
      message: 'load-balancer-api-external: resolved host name a9a41377d09754050b5ced07b667c9ec-4c48eb74148e30ab.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T13:41:09Z"
    - latency: 5.46602ms
      message: 'load-balancer-api-external: tcp connection to a9a41377d09754050b5ced07b667c9ec-4c48eb74148e30ab.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T13:40:09Z"
    - latency: 6.842598ms
      message: 'load-balancer-api-external: resolved host name a9a41377d09754050b5ced07b667c9ec-4c48eb74148e30ab.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T13:40:09Z"
    - latency: 5.090999ms
      message: 'load-balancer-api-external: tcp connection to a9a41377d09754050b5ced07b667c9ec-4c48eb74148e30ab.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T13:39:09Z"
    - latency: 6.496272ms
      message: 'load-balancer-api-external: resolved host name a9a41377d09754050b5ced07b667c9ec-4c48eb74148e30ab.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T13:39:09Z"
    - latency: 5.467915ms
      message: 'load-balancer-api-external: tcp connection to a9a41377d09754050b5ced07b667c9ec-4c48eb74148e30ab.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T13:38:09Z"
    - latency: 7.251196ms
      message: 'load-balancer-api-external: resolved host name a9a41377d09754050b5ced07b667c9ec-4c48eb74148e30ab.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T13:38:09Z"
    - latency: 4.305248ms
      message: 'load-balancer-api-external: tcp connection to a9a41377d09754050b5ced07b667c9ec-4c48eb74148e30ab.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T13:37:09Z"
    - latency: 6.110902ms
      message: 'load-balancer-api-external: resolved host name a9a41377d09754050b5ced07b667c9ec-4c48eb74148e30ab.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T13:37:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T13:17:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-62-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-62.ec2.internal
      uid: 3777ab65-b81e-4ec7-bd5d-2ec753032c26
    resourceVersion: "20216"
    uid: 4599f822-a877-460d-bfc2-266d943f628c
  spec:
    sourcePod: network-check-source-6f8b768455-chjw7
    targetEndpoint: a9a41377d09754050b5ced07b667c9ec-4c48eb74148e30ab.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T13:23:09Z"
      message: 'load-balancer-api-internal: tcp connection to a9a41377d09754050b5ced07b667c9ec-4c48eb74148e30ab.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.952355ms
      message: 'load-balancer-api-internal: tcp connection to a9a41377d09754050b5ced07b667c9ec-4c48eb74148e30ab.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T13:41:09Z"
    - latency: 6.800632ms
      message: 'load-balancer-api-internal: resolved host name a9a41377d09754050b5ced07b667c9ec-4c48eb74148e30ab.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T13:41:09Z"
    - latency: 5.470629ms
      message: 'load-balancer-api-internal: tcp connection to a9a41377d09754050b5ced07b667c9ec-4c48eb74148e30ab.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T13:40:09Z"
    - latency: 6.796674ms
      message: 'load-balancer-api-internal: resolved host name a9a41377d09754050b5ced07b667c9ec-4c48eb74148e30ab.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T13:40:09Z"
    - latency: 5.084804ms
      message: 'load-balancer-api-internal: tcp connection to a9a41377d09754050b5ced07b667c9ec-4c48eb74148e30ab.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T13:39:09Z"
    - latency: 6.390911ms
      message: 'load-balancer-api-internal: resolved host name a9a41377d09754050b5ced07b667c9ec-4c48eb74148e30ab.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T13:39:09Z"
    - latency: 5.495235ms
      message: 'load-balancer-api-internal: tcp connection to a9a41377d09754050b5ced07b667c9ec-4c48eb74148e30ab.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T13:38:09Z"
    - latency: 7.210669ms
      message: 'load-balancer-api-internal: resolved host name a9a41377d09754050b5ced07b667c9ec-4c48eb74148e30ab.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T13:38:09Z"
    - latency: 4.795378ms
      message: 'load-balancer-api-internal: tcp connection to a9a41377d09754050b5ced07b667c9ec-4c48eb74148e30ab.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T13:37:09Z"
    - latency: 6.08715ms
      message: 'load-balancer-api-internal: resolved host name a9a41377d09754050b5ced07b667c9ec-4c48eb74148e30ab.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T13:37:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T13:17:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-62-to-network-check-target-ip-10-0-133-247
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-62.ec2.internal
      uid: 3777ab65-b81e-4ec7-bd5d-2ec753032c26
    resourceVersion: "21758"
    uid: 74b69a0b-dfa0-4194-8b0c-c475abca4bc6
  spec:
    sourcePod: network-check-source-6f8b768455-chjw7
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T13:24:09Z"
      message: 'network-check-target-ip-10-0-133-247: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.490704ms
      message: 'network-check-target-ip-10-0-133-247: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T13:45:09Z"
    - latency: 2.050885ms
      message: 'network-check-target-ip-10-0-133-247: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T13:44:09Z"
    - latency: 2.137286ms
      message: 'network-check-target-ip-10-0-133-247: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T13:43:09Z"
    - latency: 2.139558ms
      message: 'network-check-target-ip-10-0-133-247: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T13:42:09Z"
    - latency: 2.035935ms
      message: 'network-check-target-ip-10-0-133-247: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T13:41:09Z"
    - latency: 2.190179ms
      message: 'network-check-target-ip-10-0-133-247: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T13:40:09Z"
    - latency: 2.234914ms
      message: 'network-check-target-ip-10-0-133-247: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T13:39:09Z"
    - latency: 1.920332ms
      message: 'network-check-target-ip-10-0-133-247: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T13:38:09Z"
    - latency: 1.959096ms
      message: 'network-check-target-ip-10-0-133-247: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T13:37:09Z"
    - latency: 2.035856ms
      message: 'network-check-target-ip-10-0-133-247: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T13:36:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T13:17:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-62-to-network-check-target-ip-10-0-133-79
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-62.ec2.internal
      uid: 3777ab65-b81e-4ec7-bd5d-2ec753032c26
    resourceVersion: "21757"
    uid: cc486542-2c75-4a02-81d5-4be88d690855
  spec:
    sourcePod: network-check-source-6f8b768455-chjw7
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T13:24:09Z"
      message: 'network-check-target-ip-10-0-133-79: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.837193ms
      message: 'network-check-target-ip-10-0-133-79: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T13:45:09Z"
    - latency: 1.772127ms
      message: 'network-check-target-ip-10-0-133-79: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T13:44:09Z"
    - latency: 1.664048ms
      message: 'network-check-target-ip-10-0-133-79: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T13:43:09Z"
    - latency: 2.109264ms
      message: 'network-check-target-ip-10-0-133-79: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T13:42:09Z"
    - latency: 1.877645ms
      message: 'network-check-target-ip-10-0-133-79: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T13:41:09Z"
    - latency: 1.920444ms
      message: 'network-check-target-ip-10-0-133-79: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T13:40:09Z"
    - latency: 1.875669ms
      message: 'network-check-target-ip-10-0-133-79: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T13:39:09Z"
    - latency: 1.915126ms
      message: 'network-check-target-ip-10-0-133-79: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T13:38:09Z"
    - latency: 1.82549ms
      message: 'network-check-target-ip-10-0-133-79: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T13:37:09Z"
    - latency: 2.429199ms
      message: 'network-check-target-ip-10-0-133-79: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T13:36:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T13:17:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-62-to-network-check-target-ip-10-0-139-62
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-62.ec2.internal
      uid: 3777ab65-b81e-4ec7-bd5d-2ec753032c26
    resourceVersion: "21756"
    uid: 49060da2-afa5-486f-a484-15725f21cc00
  spec:
    sourcePod: network-check-source-6f8b768455-chjw7
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T13:24:09Z"
      message: 'network-check-target-ip-10-0-139-62: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 865.534µs
      message: 'network-check-target-ip-10-0-139-62: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T13:45:09Z"
    - latency: 995.761µs
      message: 'network-check-target-ip-10-0-139-62: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T13:44:09Z"
    - latency: 1.127271ms
      message: 'network-check-target-ip-10-0-139-62: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T13:43:09Z"
    - latency: 794.75µs
      message: 'network-check-target-ip-10-0-139-62: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T13:42:09Z"
    - latency: 820.556µs
      message: 'network-check-target-ip-10-0-139-62: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T13:41:09Z"
    - latency: 1.44652ms
      message: 'network-check-target-ip-10-0-139-62: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T13:40:09Z"
    - latency: 816.621µs
      message: 'network-check-target-ip-10-0-139-62: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T13:39:09Z"
    - latency: 1.115725ms
      message: 'network-check-target-ip-10-0-139-62: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T13:38:09Z"
    - latency: 857.873µs
      message: 'network-check-target-ip-10-0-139-62: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T13:37:09Z"
    - latency: 775.226µs
      message: 'network-check-target-ip-10-0-139-62: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T13:36:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T13:17:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-62-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-62.ec2.internal
      uid: 3777ab65-b81e-4ec7-bd5d-2ec753032c26
    resourceVersion: "20214"
    uid: 24c95ec3-0a32-42bb-b5b8-7058b4cd4c63
  spec:
    sourcePod: network-check-source-6f8b768455-chjw7
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T13:23:09Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 880.102µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T13:41:09Z"
    - latency: 1.640641ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T13:41:09Z"
    - latency: 1.145584ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T13:40:09Z"
    - latency: 1.853085ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T13:40:09Z"
    - latency: 1.030506ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T13:39:09Z"
    - latency: 1.67479ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T13:39:09Z"
    - latency: 974.019µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T13:38:09Z"
    - latency: 1.855842ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T13:38:09Z"
    - latency: 888.052µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T13:37:09Z"
    - latency: 1.485381ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T13:37:09Z"
kind: List
metadata:
  resourceVersion: ""