apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T17:08:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-29-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-29.ec2.internal
      uid: f90f7b8a-cd0e-43a2-afd4-8915f14580d7
    resourceVersion: "63995"
    uid: 7e205063-039c-441b-967b-73ac3dd89068
  spec:
    sourcePod: network-check-source-7bc5b6bf85-v8shl
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T17:15:26Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.024532ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T17:50:26Z"
    - latency: 1.118128ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T17:49:26Z"
    - latency: 1.17802ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T17:48:26Z"
    - latency: 896.333µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T17:47:26Z"
    - latency: 1.002232ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T17:46:26Z"
    - latency: 841.646µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T17:45:26Z"
    - latency: 1.080067ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T17:44:26Z"
    - latency: 1.224546ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T17:43:26Z"
    - latency: 1.153055ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T17:42:26Z"
    - latency: 846.396µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T17:41:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T17:08:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-29-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-29.ec2.internal
      uid: f90f7b8a-cd0e-43a2-afd4-8915f14580d7
    resourceVersion: "63996"
    uid: 2d75a1f8-d1d9-45a9-af27-dd4fb5e02a0b
  spec:
    sourcePod: network-check-source-7bc5b6bf85-v8shl
    targetEndpoint: a152e818864384ee5a46c1a2f02c437f-0894e408cc29961f.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T17:14:26Z"
      message: 'load-balancer-api-external: tcp connection to a152e818864384ee5a46c1a2f02c437f-0894e408cc29961f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.001869ms
      message: 'load-balancer-api-external: tcp connection to a152e818864384ee5a46c1a2f02c437f-0894e408cc29961f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T17:50:26Z"
    - latency: 7.396986ms
      message: 'load-balancer-api-external: resolved host name a152e818864384ee5a46c1a2f02c437f-0894e408cc29961f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T17:50:26Z"
    - latency: 5.851044ms
      message: 'load-balancer-api-external: tcp connection to a152e818864384ee5a46c1a2f02c437f-0894e408cc29961f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T17:49:26Z"
    - latency: 6.800983ms
      message: 'load-balancer-api-external: resolved host name a152e818864384ee5a46c1a2f02c437f-0894e408cc29961f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T17:49:26Z"
    - latency: 3.725784ms
      message: 'load-balancer-api-external: tcp connection to a152e818864384ee5a46c1a2f02c437f-0894e408cc29961f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T17:48:26Z"
    - latency: 8.53834ms
      message: 'load-balancer-api-external: resolved host name a152e818864384ee5a46c1a2f02c437f-0894e408cc29961f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T17:48:26Z"
    - latency: 3.749456ms
      message: 'load-balancer-api-external: tcp connection to a152e818864384ee5a46c1a2f02c437f-0894e408cc29961f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T17:47:26Z"
    - latency: 7.100346ms
      message: 'load-balancer-api-external: resolved host name a152e818864384ee5a46c1a2f02c437f-0894e408cc29961f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T17:47:26Z"
    - latency: 4.216962ms
      message: 'load-balancer-api-external: tcp connection to a152e818864384ee5a46c1a2f02c437f-0894e408cc29961f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T17:46:26Z"
    - latency: 9.903403ms
      message: 'load-balancer-api-external: resolved host name a152e818864384ee5a46c1a2f02c437f-0894e408cc29961f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T17:46:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T17:08:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-29-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-29.ec2.internal
      uid: f90f7b8a-cd0e-43a2-afd4-8915f14580d7
    resourceVersion: "63997"
    uid: 606f00c4-1f6a-4f18-a8d3-3e63b12a792f
  spec:
    sourcePod: network-check-source-7bc5b6bf85-v8shl
    targetEndpoint: a152e818864384ee5a46c1a2f02c437f-0894e408cc29961f.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T17:14:26Z"
      message: 'load-balancer-api-internal: tcp connection to a152e818864384ee5a46c1a2f02c437f-0894e408cc29961f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.982653ms
      message: 'load-balancer-api-internal: tcp connection to a152e818864384ee5a46c1a2f02c437f-0894e408cc29961f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T17:50:26Z"
    - latency: 7.492368ms
      message: 'load-balancer-api-internal: resolved host name a152e818864384ee5a46c1a2f02c437f-0894e408cc29961f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T17:50:26Z"
    - latency: 5.827053ms
      message: 'load-balancer-api-internal: tcp connection to a152e818864384ee5a46c1a2f02c437f-0894e408cc29961f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T17:49:26Z"
    - latency: 6.867299ms
      message: 'load-balancer-api-internal: resolved host name a152e818864384ee5a46c1a2f02c437f-0894e408cc29961f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T17:49:26Z"
    - latency: 4.919655ms
      message: 'load-balancer-api-internal: tcp connection to a152e818864384ee5a46c1a2f02c437f-0894e408cc29961f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T17:48:26Z"
    - latency: 8.624677ms
      message: 'load-balancer-api-internal: resolved host name a152e818864384ee5a46c1a2f02c437f-0894e408cc29961f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T17:48:26Z"
    - latency: 3.916117ms
      message: 'load-balancer-api-internal: tcp connection to a152e818864384ee5a46c1a2f02c437f-0894e408cc29961f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T17:47:26Z"
    - latency: 7.165841ms
      message: 'load-balancer-api-internal: resolved host name a152e818864384ee5a46c1a2f02c437f-0894e408cc29961f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T17:47:26Z"
    - latency: 4.243171ms
      message: 'load-balancer-api-internal: tcp connection to a152e818864384ee5a46c1a2f02c437f-0894e408cc29961f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T17:46:26Z"
    - latency: 9.959615ms
      message: 'load-balancer-api-internal: resolved host name a152e818864384ee5a46c1a2f02c437f-0894e408cc29961f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T17:46:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T17:08:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-29-to-network-check-target-ip-10-0-129-216
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-29.ec2.internal
      uid: f90f7b8a-cd0e-43a2-afd4-8915f14580d7
    resourceVersion: "63993"
    uid: 70251a95-92f8-4f6a-866b-19ad53acdda5
  spec:
    sourcePod: network-check-source-7bc5b6bf85-v8shl
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T17:15:26Z"
      message: 'network-check-target-ip-10-0-129-216: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.262451ms
      message: 'network-check-target-ip-10-0-129-216: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T17:50:26Z"
    - latency: 2.533701ms
      message: 'network-check-target-ip-10-0-129-216: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T17:49:26Z"
    - latency: 2.523141ms
      message: 'network-check-target-ip-10-0-129-216: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T17:48:26Z"
    - latency: 2.392226ms
      message: 'network-check-target-ip-10-0-129-216: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T17:47:26Z"
    - latency: 2.449017ms
      message: 'network-check-target-ip-10-0-129-216: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T17:46:26Z"
    - latency: 2.347725ms
      message: 'network-check-target-ip-10-0-129-216: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T17:45:26Z"
    - latency: 2.657871ms
      message: 'network-check-target-ip-10-0-129-216: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T17:44:26Z"
    - latency: 2.796497ms
      message: 'network-check-target-ip-10-0-129-216: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T17:43:26Z"
    - latency: 2.246442ms
      message: 'network-check-target-ip-10-0-129-216: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T17:42:26Z"
    - latency: 2.489114ms
      message: 'network-check-target-ip-10-0-129-216: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T17:41:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T17:08:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-29-to-network-check-target-ip-10-0-133-26
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-29.ec2.internal
      uid: f90f7b8a-cd0e-43a2-afd4-8915f14580d7
    resourceVersion: "63992"
    uid: d9dcd30a-981d-411f-89d3-af817993b3ef
  spec:
    sourcePod: network-check-source-7bc5b6bf85-v8shl
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T17:15:26Z"
      message: 'network-check-target-ip-10-0-133-26: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.106743ms
      message: 'network-check-target-ip-10-0-133-26: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T17:50:26Z"
    - latency: 2.28321ms
      message: 'network-check-target-ip-10-0-133-26: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T17:49:26Z"
    - latency: 2.303325ms
      message: 'network-check-target-ip-10-0-133-26: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T17:48:26Z"
    - latency: 2.487237ms
      message: 'network-check-target-ip-10-0-133-26: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T17:47:26Z"
    - latency: 2.446512ms
      message: 'network-check-target-ip-10-0-133-26: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T17:46:26Z"
    - latency: 2.188301ms
      message: 'network-check-target-ip-10-0-133-26: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T17:45:26Z"
    - latency: 2.274587ms
      message: 'network-check-target-ip-10-0-133-26: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T17:44:26Z"
    - latency: 2.716992ms
      message: 'network-check-target-ip-10-0-133-26: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T17:43:26Z"
    - latency: 2.089616ms
      message: 'network-check-target-ip-10-0-133-26: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T17:42:26Z"
    - latency: 2.324117ms
      message: 'network-check-target-ip-10-0-133-26: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T17:41:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T17:08:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-29-to-network-check-target-ip-10-0-136-29
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-29.ec2.internal
      uid: f90f7b8a-cd0e-43a2-afd4-8915f14580d7
    resourceVersion: "63991"
    uid: 5f6d743c-b248-4ad0-801e-b43420d3f003
  spec:
    sourcePod: network-check-source-7bc5b6bf85-v8shl
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T17:15:26Z"
      message: 'network-check-target-ip-10-0-136-29: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 978.848µs
      message: 'network-check-target-ip-10-0-136-29: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T17:50:26Z"
    - latency: 951.9µs
      message: 'network-check-target-ip-10-0-136-29: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T17:49:26Z"
    - latency: 920.471µs
      message: 'network-check-target-ip-10-0-136-29: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T17:48:26Z"
    - latency: 1.176963ms
      message: 'network-check-target-ip-10-0-136-29: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T17:47:26Z"
    - latency: 862.798µs
      message: 'network-check-target-ip-10-0-136-29: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T17:46:26Z"
    - latency: 1.312327ms
      message: 'network-check-target-ip-10-0-136-29: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T17:45:26Z"
    - latency: 745.22µs
      message: 'network-check-target-ip-10-0-136-29: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T17:44:26Z"
    - latency: 905.966µs
      message: 'network-check-target-ip-10-0-136-29: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T17:43:26Z"
    - latency: 985.174µs
      message: 'network-check-target-ip-10-0-136-29: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T17:42:26Z"
    - latency: 971.532µs
      message: 'network-check-target-ip-10-0-136-29: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T17:41:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T17:08:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-29-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-29.ec2.internal
      uid: f90f7b8a-cd0e-43a2-afd4-8915f14580d7
    resourceVersion: "63994"
    uid: 5796b567-8ad1-463e-9a77-305ff0c72cd7
  spec:
    sourcePod: network-check-source-7bc5b6bf85-v8shl
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T17:14:26Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 824.948µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T17:50:26Z"
    - latency: 2.03011ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T17:50:26Z"
    - latency: 1.100573ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T17:49:26Z"
    - latency: 1.717282ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T17:49:26Z"
    - latency: 890.892µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T17:48:26Z"
    - latency: 1.650346ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T17:48:26Z"
    - latency: 1.313875ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T17:47:26Z"
    - latency: 1.896333ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T17:47:26Z"
    - latency: 1.279406ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T17:46:26Z"
    - latency: 1.987987ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T17:46:26Z"
kind: List
metadata:
  resourceVersion: ""