apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T16:19:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-77-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-77.ec2.internal
      uid: f09557f2-9a82-4b36-b37d-363bc9fc5467
    resourceVersion: "22998"
    uid: 4ed19e03-a08d-4c2d-a04d-1cf889ab28a5
  spec:
    sourcePod: network-check-source-6f8b768455-ckmh7
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T16:27:00Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 844.809µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:41:00Z"
    - latency: 1.336117ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:40:00Z"
    - latency: 962.902µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:39:00Z"
    - latency: 926.751µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:38:00Z"
    - latency: 1.072836ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:37:00Z"
    - latency: 978.998µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:36:00Z"
    - latency: 1.079968ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:35:00Z"
    - latency: 931.601µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:34:00Z"
    - latency: 933.313µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:33:00Z"
    - latency: 1.099809ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:32:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T16:19:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-77-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-77.ec2.internal
      uid: f09557f2-9a82-4b36-b37d-363bc9fc5467
    resourceVersion: "21437"
    uid: 1c93543c-d17f-4b86-90f7-7ffb776e876e
  spec:
    sourcePod: network-check-source-6f8b768455-ckmh7
    targetEndpoint: aa769c863b03c43dbbf1c3e793cbd587-a5b214b09e12d0a8.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T16:26:00Z"
      message: 'load-balancer-api-external: tcp connection to aa769c863b03c43dbbf1c3e793cbd587-a5b214b09e12d0a8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.192143ms
      message: 'load-balancer-api-external: tcp connection to aa769c863b03c43dbbf1c3e793cbd587-a5b214b09e12d0a8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:38:00Z"
    - latency: 7.435731ms
      message: 'load-balancer-api-external: resolved host name aa769c863b03c43dbbf1c3e793cbd587-a5b214b09e12d0a8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T16:38:00Z"
    - latency: 5.921231ms
      message: 'load-balancer-api-external: tcp connection to aa769c863b03c43dbbf1c3e793cbd587-a5b214b09e12d0a8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:37:00Z"
    - latency: 7.004204ms
      message: 'load-balancer-api-external: resolved host name aa769c863b03c43dbbf1c3e793cbd587-a5b214b09e12d0a8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T16:37:00Z"
    - latency: 6.410416ms
      message: 'load-balancer-api-external: tcp connection to aa769c863b03c43dbbf1c3e793cbd587-a5b214b09e12d0a8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:36:00Z"
    - latency: 8.642648ms
      message: 'load-balancer-api-external: resolved host name aa769c863b03c43dbbf1c3e793cbd587-a5b214b09e12d0a8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T16:36:00Z"
    - latency: 7.219771ms
      message: 'load-balancer-api-external: tcp connection to aa769c863b03c43dbbf1c3e793cbd587-a5b214b09e12d0a8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:35:00Z"
    - latency: 8.214903ms
      message: 'load-balancer-api-external: resolved host name aa769c863b03c43dbbf1c3e793cbd587-a5b214b09e12d0a8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T16:35:00Z"
    - latency: 5.84762ms
      message: 'load-balancer-api-external: tcp connection to aa769c863b03c43dbbf1c3e793cbd587-a5b214b09e12d0a8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:34:00Z"
    - latency: 8.829648ms
      message: 'load-balancer-api-external: resolved host name aa769c863b03c43dbbf1c3e793cbd587-a5b214b09e12d0a8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T16:34:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T16:19:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-77-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-77.ec2.internal
      uid: f09557f2-9a82-4b36-b37d-363bc9fc5467
    resourceVersion: "21438"
    uid: ff56f9e0-3935-4f1e-81d2-615e76642ba9
  spec:
    sourcePod: network-check-source-6f8b768455-ckmh7
    targetEndpoint: aa769c863b03c43dbbf1c3e793cbd587-a5b214b09e12d0a8.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T16:26:00Z"
      message: 'load-balancer-api-internal: tcp connection to aa769c863b03c43dbbf1c3e793cbd587-a5b214b09e12d0a8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.929971ms
      message: 'load-balancer-api-internal: tcp connection to aa769c863b03c43dbbf1c3e793cbd587-a5b214b09e12d0a8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:38:00Z"
    - latency: 7.479105ms
      message: 'load-balancer-api-internal: resolved host name aa769c863b03c43dbbf1c3e793cbd587-a5b214b09e12d0a8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T16:38:00Z"
    - latency: 5.975649ms
      message: 'load-balancer-api-internal: tcp connection to aa769c863b03c43dbbf1c3e793cbd587-a5b214b09e12d0a8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:37:00Z"
    - latency: 6.937231ms
      message: 'load-balancer-api-internal: resolved host name aa769c863b03c43dbbf1c3e793cbd587-a5b214b09e12d0a8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T16:37:00Z"
    - latency: 6.414323ms
      message: 'load-balancer-api-internal: tcp connection to aa769c863b03c43dbbf1c3e793cbd587-a5b214b09e12d0a8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:36:00Z"
    - latency: 8.691136ms
      message: 'load-balancer-api-internal: resolved host name aa769c863b03c43dbbf1c3e793cbd587-a5b214b09e12d0a8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T16:36:00Z"
    - latency: 5.393719ms
      message: 'load-balancer-api-internal: tcp connection to aa769c863b03c43dbbf1c3e793cbd587-a5b214b09e12d0a8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:35:00Z"
    - latency: 8.20468ms
      message: 'load-balancer-api-internal: resolved host name aa769c863b03c43dbbf1c3e793cbd587-a5b214b09e12d0a8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T16:35:00Z"
    - latency: 5.863097ms
      message: 'load-balancer-api-internal: tcp connection to aa769c863b03c43dbbf1c3e793cbd587-a5b214b09e12d0a8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:34:00Z"
    - latency: 8.748558ms
      message: 'load-balancer-api-internal: resolved host name aa769c863b03c43dbbf1c3e793cbd587-a5b214b09e12d0a8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T16:34:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T16:19:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-77-to-network-check-target-ip-10-0-135-5
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-77.ec2.internal
      uid: f09557f2-9a82-4b36-b37d-363bc9fc5467
    resourceVersion: "22996"
    uid: bbbe8ce0-d0ff-45af-9efe-0d8f3a10d22d
  spec:
    sourcePod: network-check-source-6f8b768455-ckmh7
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T16:27:00Z"
      message: 'network-check-target-ip-10-0-135-5: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.096637ms
      message: 'network-check-target-ip-10-0-135-5: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:41:00Z"
    - latency: 2.780348ms
      message: 'network-check-target-ip-10-0-135-5: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:40:00Z"
    - latency: 2.313493ms
      message: 'network-check-target-ip-10-0-135-5: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:39:00Z"
    - latency: 2.118115ms
      message: 'network-check-target-ip-10-0-135-5: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:38:00Z"
    - latency: 2.264441ms
      message: 'network-check-target-ip-10-0-135-5: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:37:00Z"
    - latency: 2.275051ms
      message: 'network-check-target-ip-10-0-135-5: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:36:00Z"
    - latency: 2.254438ms
      message: 'network-check-target-ip-10-0-135-5: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:35:00Z"
    - latency: 2.21256ms
      message: 'network-check-target-ip-10-0-135-5: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:34:00Z"
    - latency: 2.177676ms
      message: 'network-check-target-ip-10-0-135-5: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:33:00Z"
    - latency: 2.329128ms
      message: 'network-check-target-ip-10-0-135-5: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:32:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T16:19:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-77-to-network-check-target-ip-10-0-137-32
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-77.ec2.internal
      uid: f09557f2-9a82-4b36-b37d-363bc9fc5467
    resourceVersion: "22997"
    uid: 6da5b777-ed9b-4a0a-b821-158984d03b90
  spec:
    sourcePod: network-check-source-6f8b768455-ckmh7
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T16:27:00Z"
      message: 'network-check-target-ip-10-0-137-32: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.018892ms
      message: 'network-check-target-ip-10-0-137-32: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:41:00Z"
    - latency: 1.623008ms
      message: 'network-check-target-ip-10-0-137-32: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:40:00Z"
    - latency: 2.22448ms
      message: 'network-check-target-ip-10-0-137-32: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:39:00Z"
    - latency: 2.063605ms
      message: 'network-check-target-ip-10-0-137-32: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:38:00Z"
    - latency: 1.947538ms
      message: 'network-check-target-ip-10-0-137-32: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:37:00Z"
    - latency: 6.399709ms
      message: 'network-check-target-ip-10-0-137-32: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:36:00Z"
    - latency: 2.191096ms
      message: 'network-check-target-ip-10-0-137-32: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:35:00Z"
    - latency: 1.955495ms
      message: 'network-check-target-ip-10-0-137-32: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:34:00Z"
    - latency: 2.408946ms
      message: 'network-check-target-ip-10-0-137-32: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:33:00Z"
    - latency: 1.954158ms
      message: 'network-check-target-ip-10-0-137-32: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:32:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T16:19:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-77-to-network-check-target-ip-10-0-141-77
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-77.ec2.internal
      uid: f09557f2-9a82-4b36-b37d-363bc9fc5467
    resourceVersion: "22995"
    uid: e563f77d-9ad9-4e52-b339-398888ebeac7
  spec:
    sourcePod: network-check-source-6f8b768455-ckmh7
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T16:27:00Z"
      message: 'network-check-target-ip-10-0-141-77: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 866.867µs
      message: 'network-check-target-ip-10-0-141-77: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:41:00Z"
    - latency: 1.627256ms
      message: 'network-check-target-ip-10-0-141-77: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:40:00Z"
    - latency: 1.08978ms
      message: 'network-check-target-ip-10-0-141-77: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:39:00Z"
    - latency: 840.405µs
      message: 'network-check-target-ip-10-0-141-77: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:38:00Z"
    - latency: 971.906µs
      message: 'network-check-target-ip-10-0-141-77: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:37:00Z"
    - latency: 1.391807ms
      message: 'network-check-target-ip-10-0-141-77: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:36:00Z"
    - latency: 1.381615ms
      message: 'network-check-target-ip-10-0-141-77: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:35:00Z"
    - latency: 849.338µs
      message: 'network-check-target-ip-10-0-141-77: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:34:00Z"
    - latency: 968.681µs
      message: 'network-check-target-ip-10-0-141-77: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:33:00Z"
    - latency: 1.038579ms
      message: 'network-check-target-ip-10-0-141-77: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:32:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T16:19:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-77-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-77.ec2.internal
      uid: f09557f2-9a82-4b36-b37d-363bc9fc5467
    resourceVersion: "21436"
    uid: 0d02d0f9-d374-45ca-8cf2-a0fcd93ee33e
  spec:
    sourcePod: network-check-source-6f8b768455-ckmh7
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T16:26:00Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.225774ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:38:00Z"
    - latency: 1.791592ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T16:38:00Z"
    - latency: 1.073092ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:37:00Z"
    - latency: 1.753095ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T16:37:00Z"
    - latency: 1.725878ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:36:00Z"
    - latency: 1.833355ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T16:36:00Z"
    - latency: 874.881µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:35:00Z"
    - latency: 1.875236ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T16:35:00Z"
    - latency: 914.486µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:34:00Z"
    - latency: 1.841192ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T16:34:00Z"
kind: List
metadata:
  resourceVersion: ""