apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-02T10:41:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-208-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-208.ec2.internal
      uid: c8aef33c-0a3d-422b-8b93-98d1c8c04036
    resourceVersion: "76872"
    uid: e3b1a855-ef58-47fc-a267-30792b8dddd0
  spec:
    sourcePod: network-check-source-65bdbbff45-xhwxb
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-08-02T10:48:10Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 904.964µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-02T11:37:10Z"
    - latency: 965.004µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-02T11:36:10Z"
    - latency: 1.054453ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-02T11:35:10Z"
    - latency: 855.233µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-02T11:34:10Z"
    - latency: 984.703µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-02T11:33:10Z"
    - latency: 1.105383ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-02T11:32:10Z"
    - latency: 1.226701ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-02T11:31:10Z"
    - latency: 1.025376ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-02T11:30:10Z"
    - latency: 1.201205ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-02T11:29:10Z"
    - latency: 1.417104ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-02T11:28:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-02T10:41:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-208-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-208.ec2.internal
      uid: c8aef33c-0a3d-422b-8b93-98d1c8c04036
    resourceVersion: "74867"
    uid: 0e1b33fb-1c6d-4f62-b08f-60ba7fe00f28
  spec:
    sourcePod: network-check-source-65bdbbff45-xhwxb
    targetEndpoint: adba7fa578e30452285aa2dcd1ea8929-940aea7610e447ae.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-08-02T10:47:10Z"
      message: 'load-balancer-api-external: tcp connection to adba7fa578e30452285aa2dcd1ea8929-940aea7610e447ae.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.864117ms
      message: 'load-balancer-api-external: tcp connection to adba7fa578e30452285aa2dcd1ea8929-940aea7610e447ae.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-02T11:35:10Z"
    - latency: 8.683754ms
      message: 'load-balancer-api-external: resolved host name adba7fa578e30452285aa2dcd1ea8929-940aea7610e447ae.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-02T11:35:10Z"
    - latency: 4.422879ms
      message: 'load-balancer-api-external: tcp connection to adba7fa578e30452285aa2dcd1ea8929-940aea7610e447ae.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-02T11:34:10Z"
    - latency: 8.1416ms
      message: 'load-balancer-api-external: resolved host name adba7fa578e30452285aa2dcd1ea8929-940aea7610e447ae.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-02T11:34:10Z"
    - latency: 5.165638ms
      message: 'load-balancer-api-external: tcp connection to adba7fa578e30452285aa2dcd1ea8929-940aea7610e447ae.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-02T11:33:10Z"
    - latency: 8.127861ms
      message: 'load-balancer-api-external: resolved host name adba7fa578e30452285aa2dcd1ea8929-940aea7610e447ae.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-02T11:33:10Z"
    - latency: 4.798998ms
      message: 'load-balancer-api-external: tcp connection to adba7fa578e30452285aa2dcd1ea8929-940aea7610e447ae.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-02T11:32:10Z"
    - latency: 9.312178ms
      message: 'load-balancer-api-external: resolved host name adba7fa578e30452285aa2dcd1ea8929-940aea7610e447ae.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-02T11:32:10Z"
    - latency: 4.820466ms
      message: 'load-balancer-api-external: tcp connection to adba7fa578e30452285aa2dcd1ea8929-940aea7610e447ae.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-02T11:31:10Z"
    - latency: 9.789355ms
      message: 'load-balancer-api-external: resolved host name adba7fa578e30452285aa2dcd1ea8929-940aea7610e447ae.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-02T11:31:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-02T10:41:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-208-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-208.ec2.internal
      uid: c8aef33c-0a3d-422b-8b93-98d1c8c04036
    resourceVersion: "74868"
    uid: ac10c8c9-5fc3-4dc1-9aeb-2255924f5f7b
  spec:
    sourcePod: network-check-source-65bdbbff45-xhwxb
    targetEndpoint: adba7fa578e30452285aa2dcd1ea8929-940aea7610e447ae.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-08-02T10:47:10Z"
      message: 'load-balancer-api-internal: tcp connection to adba7fa578e30452285aa2dcd1ea8929-940aea7610e447ae.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.853862ms
      message: 'load-balancer-api-internal: tcp connection to adba7fa578e30452285aa2dcd1ea8929-940aea7610e447ae.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-02T11:35:10Z"
    - latency: 8.741243ms
      message: 'load-balancer-api-internal: resolved host name adba7fa578e30452285aa2dcd1ea8929-940aea7610e447ae.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-02T11:35:10Z"
    - latency: 4.425882ms
      message: 'load-balancer-api-internal: tcp connection to adba7fa578e30452285aa2dcd1ea8929-940aea7610e447ae.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-02T11:34:10Z"
    - latency: 8.218855ms
      message: 'load-balancer-api-internal: resolved host name adba7fa578e30452285aa2dcd1ea8929-940aea7610e447ae.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-02T11:34:10Z"
    - latency: 5.228841ms
      message: 'load-balancer-api-internal: tcp connection to adba7fa578e30452285aa2dcd1ea8929-940aea7610e447ae.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-02T11:33:10Z"
    - latency: 8.138583ms
      message: 'load-balancer-api-internal: resolved host name adba7fa578e30452285aa2dcd1ea8929-940aea7610e447ae.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-02T11:33:10Z"
    - latency: 4.811709ms
      message: 'load-balancer-api-internal: tcp connection to adba7fa578e30452285aa2dcd1ea8929-940aea7610e447ae.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-02T11:32:10Z"
    - latency: 9.421694ms
      message: 'load-balancer-api-internal: resolved host name adba7fa578e30452285aa2dcd1ea8929-940aea7610e447ae.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-02T11:32:10Z"
    - latency: 4.966452ms
      message: 'load-balancer-api-internal: tcp connection to adba7fa578e30452285aa2dcd1ea8929-940aea7610e447ae.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-02T11:31:10Z"
    - latency: 9.733651ms
      message: 'load-balancer-api-internal: resolved host name adba7fa578e30452285aa2dcd1ea8929-940aea7610e447ae.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-02T11:31:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-02T10:41:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-208-to-network-check-target-ip-10-0-130-84
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-208.ec2.internal
      uid: c8aef33c-0a3d-422b-8b93-98d1c8c04036
    resourceVersion: "76870"
    uid: 78f04dd2-ae63-40b5-96c0-fd7485b2f6ad
  spec:
    sourcePod: network-check-source-65bdbbff45-xhwxb
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-08-02T10:48:10Z"
      message: 'network-check-target-ip-10-0-130-84: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.3546ms
      message: 'network-check-target-ip-10-0-130-84: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-02T11:37:10Z"
    - latency: 2.709754ms
      message: 'network-check-target-ip-10-0-130-84: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-02T11:36:10Z"
    - latency: 2.367821ms
      message: 'network-check-target-ip-10-0-130-84: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-02T11:35:10Z"
    - latency: 2.485808ms
      message: 'network-check-target-ip-10-0-130-84: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-02T11:34:10Z"
    - latency: 2.514344ms
      message: 'network-check-target-ip-10-0-130-84: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-02T11:33:10Z"
    - latency: 2.380725ms
      message: 'network-check-target-ip-10-0-130-84: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-02T11:32:10Z"
    - latency: 2.18767ms
      message: 'network-check-target-ip-10-0-130-84: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-02T11:31:10Z"
    - latency: 2.258595ms
      message: 'network-check-target-ip-10-0-130-84: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-02T11:30:10Z"
    - latency: 2.493309ms
      message: 'network-check-target-ip-10-0-130-84: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-02T11:29:10Z"
    - latency: 2.311697ms
      message: 'network-check-target-ip-10-0-130-84: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-02T11:28:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-02T10:41:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-208-to-network-check-target-ip-10-0-135-193
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-208.ec2.internal
      uid: c8aef33c-0a3d-422b-8b93-98d1c8c04036
    resourceVersion: "76871"
    uid: 2e0b26f2-8348-4cad-b2c4-7aefdb7a1225
  spec:
    sourcePod: network-check-source-65bdbbff45-xhwxb
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-08-02T10:48:10Z"
      message: 'network-check-target-ip-10-0-135-193: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.62277ms
      message: 'network-check-target-ip-10-0-135-193: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-02T11:37:10Z"
    - latency: 2.457023ms
      message: 'network-check-target-ip-10-0-135-193: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-02T11:36:10Z"
    - latency: 2.419623ms
      message: 'network-check-target-ip-10-0-135-193: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-02T11:35:10Z"
    - latency: 2.143329ms
      message: 'network-check-target-ip-10-0-135-193: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-02T11:34:10Z"
    - latency: 2.456168ms
      message: 'network-check-target-ip-10-0-135-193: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-02T11:33:10Z"
    - latency: 2.567934ms
      message: 'network-check-target-ip-10-0-135-193: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-02T11:32:10Z"
    - latency: 2.33768ms
      message: 'network-check-target-ip-10-0-135-193: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-02T11:31:10Z"
    - latency: 2.481173ms
      message: 'network-check-target-ip-10-0-135-193: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-02T11:30:10Z"
    - latency: 1.952441ms
      message: 'network-check-target-ip-10-0-135-193: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-02T11:29:10Z"
    - latency: 2.393558ms
      message: 'network-check-target-ip-10-0-135-193: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-02T11:28:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-02T10:41:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-208-to-network-check-target-ip-10-0-141-208
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-208.ec2.internal
      uid: c8aef33c-0a3d-422b-8b93-98d1c8c04036
    resourceVersion: "76869"
    uid: 88a1f7a0-6e3d-480f-897a-9c0ddaa59118
  spec:
    sourcePod: network-check-source-65bdbbff45-xhwxb
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-08-02T10:48:10Z"
      message: 'network-check-target-ip-10-0-141-208: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.441355ms
      message: 'network-check-target-ip-10-0-141-208: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-02T11:37:10Z"
    - latency: 1.054264ms
      message: 'network-check-target-ip-10-0-141-208: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-02T11:36:10Z"
    - latency: 1.066703ms
      message: 'network-check-target-ip-10-0-141-208: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-02T11:35:10Z"
    - latency: 912.677µs
      message: 'network-check-target-ip-10-0-141-208: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-02T11:34:10Z"
    - latency: 1.054439ms
      message: 'network-check-target-ip-10-0-141-208: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-02T11:33:10Z"
    - latency: 1.062187ms
      message: 'network-check-target-ip-10-0-141-208: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-02T11:32:10Z"
    - latency: 854.459µs
      message: 'network-check-target-ip-10-0-141-208: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-02T11:31:10Z"
    - latency: 944.838µs
      message: 'network-check-target-ip-10-0-141-208: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-02T11:30:10Z"
    - latency: 1.336878ms
      message: 'network-check-target-ip-10-0-141-208: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-02T11:29:10Z"
    - latency: 777.341µs
      message: 'network-check-target-ip-10-0-141-208: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-02T11:28:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-02T10:41:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-208-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-208.ec2.internal
      uid: c8aef33c-0a3d-422b-8b93-98d1c8c04036
    resourceVersion: "74866"
    uid: 9014d6b3-3027-4847-8b29-f804e5700874
  spec:
    sourcePod: network-check-source-65bdbbff45-xhwxb
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-08-02T10:47:10Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 876.252µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-02T11:35:10Z"
    - latency: 1.741765ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-02T11:35:10Z"
    - latency: 966.976µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-02T11:34:10Z"
    - latency: 1.873849ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-02T11:34:10Z"
    - latency: 915.733µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-02T11:33:10Z"
    - latency: 1.752092ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-02T11:33:10Z"
    - latency: 1.156525ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-02T11:32:10Z"
    - latency: 1.909931ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-02T11:32:10Z"
    - latency: 1.106745ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-02T11:31:10Z"
    - latency: 1.546177ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-02T11:31:10Z"
kind: List
metadata:
  resourceVersion: ""