apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T14:02:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-144-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-144.ec2.internal
      uid: 3435fc71-555f-4783-b078-b73a747a06b9
    resourceVersion: "58136"
    uid: 3bdc7582-df57-449d-a995-9173ab13bb38
  spec:
    sourcePod: network-check-source-6f8b768455-mvpvl
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T14:09:28Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.016978ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:37:28Z"
    - latency: 1.282321ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:36:28Z"
    - latency: 1.006529ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:35:28Z"
    - latency: 1.486801ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:34:28Z"
    - latency: 1.114546ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:33:28Z"
    - latency: 997.987µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:32:28Z"
    - latency: 1.211651ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:31:28Z"
    - latency: 1.137457ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:30:28Z"
    - latency: 1.062804ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:29:28Z"
    - latency: 1.005734ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:28:28Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T14:02:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-144-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-144.ec2.internal
      uid: 3435fc71-555f-4783-b078-b73a747a06b9
    resourceVersion: "59004"
    uid: 79fb67af-8588-4e64-b919-bd3cc6b60280
  spec:
    sourcePod: network-check-source-6f8b768455-mvpvl
    targetEndpoint: ae35bdc26d50c4087ab92c6aeb0d9fd9-1bfb543498d20572.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T14:08:28Z"
      message: 'load-balancer-api-external: tcp connection to ae35bdc26d50c4087ab92c6aeb0d9fd9-1bfb543498d20572.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.394165ms
      message: 'load-balancer-api-external: tcp connection to ae35bdc26d50c4087ab92c6aeb0d9fd9-1bfb543498d20572.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:38:28Z"
    - latency: 7.067008ms
      message: 'load-balancer-api-external: resolved host name ae35bdc26d50c4087ab92c6aeb0d9fd9-1bfb543498d20572.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T14:38:28Z"
    - latency: 4.524656ms
      message: 'load-balancer-api-external: tcp connection to ae35bdc26d50c4087ab92c6aeb0d9fd9-1bfb543498d20572.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:37:28Z"
    - latency: 7.34806ms
      message: 'load-balancer-api-external: resolved host name ae35bdc26d50c4087ab92c6aeb0d9fd9-1bfb543498d20572.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T14:37:28Z"
    - latency: 4.548051ms
      message: 'load-balancer-api-external: tcp connection to ae35bdc26d50c4087ab92c6aeb0d9fd9-1bfb543498d20572.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:36:28Z"
    - latency: 7.164795ms
      message: 'load-balancer-api-external: resolved host name ae35bdc26d50c4087ab92c6aeb0d9fd9-1bfb543498d20572.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T14:36:28Z"
    - latency: 6.172511ms
      message: 'load-balancer-api-external: tcp connection to ae35bdc26d50c4087ab92c6aeb0d9fd9-1bfb543498d20572.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:35:28Z"
    - latency: 6.529793ms
      message: 'load-balancer-api-external: resolved host name ae35bdc26d50c4087ab92c6aeb0d9fd9-1bfb543498d20572.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T14:35:28Z"
    - latency: 5.128374ms
      message: 'load-balancer-api-external: tcp connection to ae35bdc26d50c4087ab92c6aeb0d9fd9-1bfb543498d20572.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:34:28Z"
    - latency: 6.806378ms
      message: 'load-balancer-api-external: resolved host name ae35bdc26d50c4087ab92c6aeb0d9fd9-1bfb543498d20572.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T14:34:28Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T14:02:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-144-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-144.ec2.internal
      uid: 3435fc71-555f-4783-b078-b73a747a06b9
    resourceVersion: "59003"
    uid: d815e6b8-f470-47c4-8eab-3f94f17741a1
  spec:
    sourcePod: network-check-source-6f8b768455-mvpvl
    targetEndpoint: ae35bdc26d50c4087ab92c6aeb0d9fd9-1bfb543498d20572.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T14:08:28Z"
      message: 'load-balancer-api-internal: tcp connection to ae35bdc26d50c4087ab92c6aeb0d9fd9-1bfb543498d20572.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.506152ms
      message: 'load-balancer-api-internal: tcp connection to ae35bdc26d50c4087ab92c6aeb0d9fd9-1bfb543498d20572.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:38:28Z"
    - latency: 6.989398ms
      message: 'load-balancer-api-internal: resolved host name ae35bdc26d50c4087ab92c6aeb0d9fd9-1bfb543498d20572.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T14:38:28Z"
    - latency: 4.563602ms
      message: 'load-balancer-api-internal: tcp connection to ae35bdc26d50c4087ab92c6aeb0d9fd9-1bfb543498d20572.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:37:28Z"
    - latency: 7.278669ms
      message: 'load-balancer-api-internal: resolved host name ae35bdc26d50c4087ab92c6aeb0d9fd9-1bfb543498d20572.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T14:37:28Z"
    - latency: 4.557904ms
      message: 'load-balancer-api-internal: tcp connection to ae35bdc26d50c4087ab92c6aeb0d9fd9-1bfb543498d20572.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:36:28Z"
    - latency: 7.24153ms
      message: 'load-balancer-api-internal: resolved host name ae35bdc26d50c4087ab92c6aeb0d9fd9-1bfb543498d20572.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T14:36:28Z"
    - latency: 6.179478ms
      message: 'load-balancer-api-internal: tcp connection to ae35bdc26d50c4087ab92c6aeb0d9fd9-1bfb543498d20572.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:35:28Z"
    - latency: 6.556338ms
      message: 'load-balancer-api-internal: resolved host name ae35bdc26d50c4087ab92c6aeb0d9fd9-1bfb543498d20572.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T14:35:28Z"
    - latency: 4.131752ms
      message: 'load-balancer-api-internal: tcp connection to ae35bdc26d50c4087ab92c6aeb0d9fd9-1bfb543498d20572.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:34:28Z"
    - latency: 6.953527ms
      message: 'load-balancer-api-internal: resolved host name ae35bdc26d50c4087ab92c6aeb0d9fd9-1bfb543498d20572.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T14:34:28Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T14:02:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-144-to-network-check-target-ip-10-0-129-195
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-144.ec2.internal
      uid: 3435fc71-555f-4783-b078-b73a747a06b9
    resourceVersion: "58134"
    uid: 32882ae0-1a84-4028-94b7-6d0fe361b5f8
  spec:
    sourcePod: network-check-source-6f8b768455-mvpvl
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T14:09:28Z"
      message: 'network-check-target-ip-10-0-129-195: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.336112ms
      message: 'network-check-target-ip-10-0-129-195: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:37:28Z"
    - latency: 2.02071ms
      message: 'network-check-target-ip-10-0-129-195: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:36:28Z"
    - latency: 2.289414ms
      message: 'network-check-target-ip-10-0-129-195: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:35:28Z"
    - latency: 2.748445ms
      message: 'network-check-target-ip-10-0-129-195: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:34:28Z"
    - latency: 2.331271ms
      message: 'network-check-target-ip-10-0-129-195: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:33:28Z"
    - latency: 2.21717ms
      message: 'network-check-target-ip-10-0-129-195: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:32:28Z"
    - latency: 2.220785ms
      message: 'network-check-target-ip-10-0-129-195: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:31:28Z"
    - latency: 2.72753ms
      message: 'network-check-target-ip-10-0-129-195: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:30:28Z"
    - latency: 2.229834ms
      message: 'network-check-target-ip-10-0-129-195: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:29:28Z"
    - latency: 2.11686ms
      message: 'network-check-target-ip-10-0-129-195: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:28:28Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T14:02:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-144-to-network-check-target-ip-10-0-136-92
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-144.ec2.internal
      uid: 3435fc71-555f-4783-b078-b73a747a06b9
    resourceVersion: "58135"
    uid: ab1bcf83-c38c-4285-b538-217cf8cf1b8e
  spec:
    sourcePod: network-check-source-6f8b768455-mvpvl
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T14:09:28Z"
      message: 'network-check-target-ip-10-0-136-92: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.930123ms
      message: 'network-check-target-ip-10-0-136-92: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:37:28Z"
    - latency: 2.245111ms
      message: 'network-check-target-ip-10-0-136-92: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:36:28Z"
    - latency: 2.465479ms
      message: 'network-check-target-ip-10-0-136-92: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:35:28Z"
    - latency: 2.539063ms
      message: 'network-check-target-ip-10-0-136-92: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:34:28Z"
    - latency: 2.470713ms
      message: 'network-check-target-ip-10-0-136-92: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:33:28Z"
    - latency: 2.483082ms
      message: 'network-check-target-ip-10-0-136-92: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:32:28Z"
    - latency: 2.396501ms
      message: 'network-check-target-ip-10-0-136-92: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:31:28Z"
    - latency: 2.527378ms
      message: 'network-check-target-ip-10-0-136-92: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:30:28Z"
    - latency: 2.516866ms
      message: 'network-check-target-ip-10-0-136-92: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:29:28Z"
    - latency: 2.629277ms
      message: 'network-check-target-ip-10-0-136-92: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:28:28Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T14:02:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-144-to-network-check-target-ip-10-0-140-144
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-144.ec2.internal
      uid: 3435fc71-555f-4783-b078-b73a747a06b9
    resourceVersion: "58133"
    uid: 5354e6a4-90cd-4bb2-b5c9-1fa6aab6b77a
  spec:
    sourcePod: network-check-source-6f8b768455-mvpvl
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T14:09:28Z"
      message: 'network-check-target-ip-10-0-140-144: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.587961ms
      message: 'network-check-target-ip-10-0-140-144: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:37:28Z"
    - latency: 916.706µs
      message: 'network-check-target-ip-10-0-140-144: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:36:28Z"
    - latency: 1.008916ms
      message: 'network-check-target-ip-10-0-140-144: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:35:28Z"
    - latency: 1.347169ms
      message: 'network-check-target-ip-10-0-140-144: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:34:28Z"
    - latency: 979.205µs
      message: 'network-check-target-ip-10-0-140-144: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:33:28Z"
    - latency: 1.049091ms
      message: 'network-check-target-ip-10-0-140-144: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:32:28Z"
    - latency: 1.222773ms
      message: 'network-check-target-ip-10-0-140-144: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:31:28Z"
    - latency: 961.093µs
      message: 'network-check-target-ip-10-0-140-144: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:30:28Z"
    - latency: 1.070344ms
      message: 'network-check-target-ip-10-0-140-144: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:29:28Z"
    - latency: 784.001µs
      message: 'network-check-target-ip-10-0-140-144: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:28:28Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T14:02:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-144-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-144.ec2.internal
      uid: 3435fc71-555f-4783-b078-b73a747a06b9
    resourceVersion: "59002"
    uid: c18e8fd6-721c-415e-8f5f-f0bde0bfb4a2
  spec:
    sourcePod: network-check-source-6f8b768455-mvpvl
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T14:08:28Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 991.668µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:38:28Z"
    - latency: 1.665256ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T14:38:28Z"
    - latency: 758.41µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:37:28Z"
    - latency: 1.635707ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T14:37:28Z"
    - latency: 854.255µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:36:28Z"
    - latency: 1.815193ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T14:36:28Z"
    - latency: 887.839µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:35:28Z"
    - latency: 2.032158ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T14:35:28Z"
    - latency: 1.455189ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:34:28Z"
    - latency: 1.995903ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T14:34:28Z"
kind: List
metadata:
  resourceVersion: ""