apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-12T00:36:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-144-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-144.ec2.internal
      uid: af4f2f11-ac72-4a50-97d4-cfc5ed90d2f6
    resourceVersion: "69787"
    uid: 4bfb104e-ee0e-4f40-a258-2e2b05b3814b
  spec:
    sourcePod: network-check-source-6f8b768455-zs2sx
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-12T00:43:56Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 847.568µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T01:11:56Z"
    - latency: 1.080026ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T01:10:56Z"
    - latency: 963.32µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T01:09:56Z"
    - latency: 1.12957ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T01:08:56Z"
    - latency: 1.147409ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T01:07:56Z"
    - latency: 1.014438ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T01:06:56Z"
    - latency: 1.206758ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T01:05:56Z"
    - latency: 1.633049ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T01:04:56Z"
    - latency: 939.335µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T01:03:56Z"
    - latency: 939.866µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T01:02:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-12T00:36:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-144-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-144.ec2.internal
      uid: af4f2f11-ac72-4a50-97d4-cfc5ed90d2f6
    resourceVersion: "70729"
    uid: 3ba5e104-b7a1-4fb6-a548-21a78ebfbda0
  spec:
    sourcePod: network-check-source-6f8b768455-zs2sx
    targetEndpoint: a8c063bcfc41f4a3688cf3ee3f6350d1-46ff2adbe1db8f92.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-12T00:42:56Z"
      message: 'load-balancer-api-external: tcp connection to a8c063bcfc41f4a3688cf3ee3f6350d1-46ff2adbe1db8f92.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.238508ms
      message: 'load-balancer-api-external: tcp connection to a8c063bcfc41f4a3688cf3ee3f6350d1-46ff2adbe1db8f92.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T01:12:56Z"
    - latency: 8.941664ms
      message: 'load-balancer-api-external: resolved host name a8c063bcfc41f4a3688cf3ee3f6350d1-46ff2adbe1db8f92.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-12T01:12:56Z"
    - latency: 3.930735ms
      message: 'load-balancer-api-external: tcp connection to a8c063bcfc41f4a3688cf3ee3f6350d1-46ff2adbe1db8f92.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T01:11:56Z"
    - latency: 9.089414ms
      message: 'load-balancer-api-external: resolved host name a8c063bcfc41f4a3688cf3ee3f6350d1-46ff2adbe1db8f92.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-12T01:11:56Z"
    - latency: 5.736162ms
      message: 'load-balancer-api-external: tcp connection to a8c063bcfc41f4a3688cf3ee3f6350d1-46ff2adbe1db8f92.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T01:10:56Z"
    - latency: 8.33236ms
      message: 'load-balancer-api-external: resolved host name a8c063bcfc41f4a3688cf3ee3f6350d1-46ff2adbe1db8f92.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-12T01:10:56Z"
    - latency: 4.523517ms
      message: 'load-balancer-api-external: tcp connection to a8c063bcfc41f4a3688cf3ee3f6350d1-46ff2adbe1db8f92.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T01:09:56Z"
    - latency: 8.770585ms
      message: 'load-balancer-api-external: resolved host name a8c063bcfc41f4a3688cf3ee3f6350d1-46ff2adbe1db8f92.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-12T01:09:56Z"
    - latency: 5.506067ms
      message: 'load-balancer-api-external: tcp connection to a8c063bcfc41f4a3688cf3ee3f6350d1-46ff2adbe1db8f92.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T01:08:56Z"
    - latency: 10.088858ms
      message: 'load-balancer-api-external: resolved host name a8c063bcfc41f4a3688cf3ee3f6350d1-46ff2adbe1db8f92.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-12T01:08:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-12T00:36:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-144-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-144.ec2.internal
      uid: af4f2f11-ac72-4a50-97d4-cfc5ed90d2f6
    resourceVersion: "70728"
    uid: 9e004e7e-8ee5-4b6d-a876-b294a6408a21
  spec:
    sourcePod: network-check-source-6f8b768455-zs2sx
    targetEndpoint: a8c063bcfc41f4a3688cf3ee3f6350d1-46ff2adbe1db8f92.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-12T00:42:56Z"
      message: 'load-balancer-api-internal: tcp connection to a8c063bcfc41f4a3688cf3ee3f6350d1-46ff2adbe1db8f92.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.250137ms
      message: 'load-balancer-api-internal: tcp connection to a8c063bcfc41f4a3688cf3ee3f6350d1-46ff2adbe1db8f92.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T01:12:56Z"
    - latency: 8.899065ms
      message: 'load-balancer-api-internal: resolved host name a8c063bcfc41f4a3688cf3ee3f6350d1-46ff2adbe1db8f92.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-12T01:12:56Z"
    - latency: 4.029929ms
      message: 'load-balancer-api-internal: tcp connection to a8c063bcfc41f4a3688cf3ee3f6350d1-46ff2adbe1db8f92.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T01:11:56Z"
    - latency: 9.065636ms
      message: 'load-balancer-api-internal: resolved host name a8c063bcfc41f4a3688cf3ee3f6350d1-46ff2adbe1db8f92.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-12T01:11:56Z"
    - latency: 5.759152ms
      message: 'load-balancer-api-internal: tcp connection to a8c063bcfc41f4a3688cf3ee3f6350d1-46ff2adbe1db8f92.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T01:10:56Z"
    - latency: 8.291732ms
      message: 'load-balancer-api-internal: resolved host name a8c063bcfc41f4a3688cf3ee3f6350d1-46ff2adbe1db8f92.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-12T01:10:56Z"
    - latency: 5.574102ms
      message: 'load-balancer-api-internal: tcp connection to a8c063bcfc41f4a3688cf3ee3f6350d1-46ff2adbe1db8f92.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T01:09:56Z"
    - latency: 8.706463ms
      message: 'load-balancer-api-internal: resolved host name a8c063bcfc41f4a3688cf3ee3f6350d1-46ff2adbe1db8f92.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-12T01:09:56Z"
    - latency: 6.003276ms
      message: 'load-balancer-api-internal: tcp connection to a8c063bcfc41f4a3688cf3ee3f6350d1-46ff2adbe1db8f92.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T01:08:56Z"
    - latency: 9.957924ms
      message: 'load-balancer-api-internal: resolved host name a8c063bcfc41f4a3688cf3ee3f6350d1-46ff2adbe1db8f92.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-12T01:08:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-12T00:36:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-144-to-network-check-target-ip-10-0-130-132
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-144.ec2.internal
      uid: af4f2f11-ac72-4a50-97d4-cfc5ed90d2f6
    resourceVersion: "69786"
    uid: 1f993210-5b8d-4035-861e-f88af7082c95
  spec:
    sourcePod: network-check-source-6f8b768455-zs2sx
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-12T00:43:56Z"
      message: 'network-check-target-ip-10-0-130-132: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.319689ms
      message: 'network-check-target-ip-10-0-130-132: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T01:11:56Z"
    - latency: 2.224904ms
      message: 'network-check-target-ip-10-0-130-132: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T01:10:56Z"
    - latency: 2.567095ms
      message: 'network-check-target-ip-10-0-130-132: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T01:09:56Z"
    - latency: 2.827438ms
      message: 'network-check-target-ip-10-0-130-132: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T01:08:56Z"
    - latency: 2.631203ms
      message: 'network-check-target-ip-10-0-130-132: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T01:07:56Z"
    - latency: 2.35933ms
      message: 'network-check-target-ip-10-0-130-132: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T01:06:56Z"
    - latency: 2.578433ms
      message: 'network-check-target-ip-10-0-130-132: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T01:05:56Z"
    - latency: 2.57494ms
      message: 'network-check-target-ip-10-0-130-132: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T01:04:56Z"
    - latency: 2.722697ms
      message: 'network-check-target-ip-10-0-130-132: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T01:03:56Z"
    - latency: 2.372706ms
      message: 'network-check-target-ip-10-0-130-132: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T01:02:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-12T00:36:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-144-to-network-check-target-ip-10-0-131-144
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-144.ec2.internal
      uid: af4f2f11-ac72-4a50-97d4-cfc5ed90d2f6
    resourceVersion: "69784"
    uid: 478e1540-165f-464b-b9a3-2af95911015b
  spec:
    sourcePod: network-check-source-6f8b768455-zs2sx
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-12T00:43:56Z"
      message: 'network-check-target-ip-10-0-131-144: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.074499ms
      message: 'network-check-target-ip-10-0-131-144: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T01:11:56Z"
    - latency: 953.794µs
      message: 'network-check-target-ip-10-0-131-144: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T01:10:56Z"
    - latency: 995.569µs
      message: 'network-check-target-ip-10-0-131-144: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T01:09:56Z"
    - latency: 939.578µs
      message: 'network-check-target-ip-10-0-131-144: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T01:08:56Z"
    - latency: 983.618µs
      message: 'network-check-target-ip-10-0-131-144: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T01:07:56Z"
    - latency: 989.511µs
      message: 'network-check-target-ip-10-0-131-144: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T01:06:56Z"
    - latency: 921.714µs
      message: 'network-check-target-ip-10-0-131-144: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T01:05:56Z"
    - latency: 946.028µs
      message: 'network-check-target-ip-10-0-131-144: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T01:04:56Z"
    - latency: 1.311283ms
      message: 'network-check-target-ip-10-0-131-144: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T01:03:56Z"
    - latency: 1.580114ms
      message: 'network-check-target-ip-10-0-131-144: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T01:02:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-12T00:36:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-144-to-network-check-target-ip-10-0-142-85
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-144.ec2.internal
      uid: af4f2f11-ac72-4a50-97d4-cfc5ed90d2f6
    resourceVersion: "69785"
    uid: 05e62eb7-9ab2-497f-bd54-008d49e9a7c6
  spec:
    sourcePod: network-check-source-6f8b768455-zs2sx
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-12T00:43:56Z"
      message: 'network-check-target-ip-10-0-142-85: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.276793ms
      message: 'network-check-target-ip-10-0-142-85: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T01:11:56Z"
    - latency: 2.167973ms
      message: 'network-check-target-ip-10-0-142-85: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T01:10:56Z"
    - latency: 2.033431ms
      message: 'network-check-target-ip-10-0-142-85: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T01:09:56Z"
    - latency: 2.655775ms
      message: 'network-check-target-ip-10-0-142-85: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T01:08:56Z"
    - latency: 2.302787ms
      message: 'network-check-target-ip-10-0-142-85: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T01:07:56Z"
    - latency: 2.106637ms
      message: 'network-check-target-ip-10-0-142-85: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T01:06:56Z"
    - latency: 2.199546ms
      message: 'network-check-target-ip-10-0-142-85: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T01:05:56Z"
    - latency: 2.355817ms
      message: 'network-check-target-ip-10-0-142-85: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T01:04:56Z"
    - latency: 2.178794ms
      message: 'network-check-target-ip-10-0-142-85: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T01:03:56Z"
    - latency: 2.135306ms
      message: 'network-check-target-ip-10-0-142-85: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T01:02:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-12T00:36:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-144-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-144.ec2.internal
      uid: af4f2f11-ac72-4a50-97d4-cfc5ed90d2f6
    resourceVersion: "70727"
    uid: fd5b4683-6b90-4978-9459-ad6d5e8c1911
  spec:
    sourcePod: network-check-source-6f8b768455-zs2sx
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-12T00:42:56Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 895.526µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T01:12:56Z"
    - latency: 1.642067ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-12T01:12:56Z"
    - latency: 872.846µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T01:11:56Z"
    - latency: 2.027219ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-12T01:11:56Z"
    - latency: 1.056398ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T01:10:56Z"
    - latency: 1.688823ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-12T01:10:56Z"
    - latency: 898.686µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T01:09:56Z"
    - latency: 2.170109ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-12T01:09:56Z"
    - latency: 1.01718ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T01:08:56Z"
    - latency: 2.681481ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-12T01:08:56Z"
kind: List
metadata:
  resourceVersion: ""