apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-10T03:38:54Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-167-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-167.ec2.internal
      uid: 4aeaca18-bbba-4844-944a-c4305451299f
    resourceVersion: "55586"
    uid: 4d0c5ab2-6563-4173-b0c3-ff6e6cf9a80a
  spec:
    sourcePod: network-check-source-869dcfcdcd-nkxvw
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-10T03:45:55Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 903.673µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T04:13:55Z"
    - latency: 783.009µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T04:12:55Z"
    - latency: 901.994µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T04:11:55Z"
    - latency: 1.330713ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T04:10:55Z"
    - latency: 1.224831ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T04:09:55Z"
    - latency: 1.026681ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T04:08:55Z"
    - latency: 948.016µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T04:07:55Z"
    - latency: 1.283046ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T04:06:55Z"
    - latency: 1.415919ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T04:05:55Z"
    - latency: 889.395µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T04:04:55Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-10T03:38:54Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-167-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-167.ec2.internal
      uid: 4aeaca18-bbba-4844-944a-c4305451299f
    resourceVersion: "56486"
    uid: 58df84c4-d85f-457c-bfc0-495262820a0d
  spec:
    sourcePod: network-check-source-869dcfcdcd-nkxvw
    targetEndpoint: ad1ffd3470c964525bf85b94a3f0e283-c3df5a89eea7372f.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-10T03:44:55Z"
      message: 'load-balancer-api-external: tcp connection to ad1ffd3470c964525bf85b94a3f0e283-c3df5a89eea7372f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.65706ms
      message: 'load-balancer-api-external: tcp connection to ad1ffd3470c964525bf85b94a3f0e283-c3df5a89eea7372f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T04:14:55Z"
    - latency: 6.923856ms
      message: 'load-balancer-api-external: resolved host name ad1ffd3470c964525bf85b94a3f0e283-c3df5a89eea7372f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T04:14:55Z"
    - latency: 4.420824ms
      message: 'load-balancer-api-external: tcp connection to ad1ffd3470c964525bf85b94a3f0e283-c3df5a89eea7372f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T04:13:55Z"
    - latency: 7.030767ms
      message: 'load-balancer-api-external: resolved host name ad1ffd3470c964525bf85b94a3f0e283-c3df5a89eea7372f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T04:13:55Z"
    - latency: 3.526864ms
      message: 'load-balancer-api-external: tcp connection to ad1ffd3470c964525bf85b94a3f0e283-c3df5a89eea7372f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T04:12:55Z"
    - latency: 5.980245ms
      message: 'load-balancer-api-external: resolved host name ad1ffd3470c964525bf85b94a3f0e283-c3df5a89eea7372f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T04:12:55Z"
    - latency: 3.999617ms
      message: 'load-balancer-api-external: tcp connection to ad1ffd3470c964525bf85b94a3f0e283-c3df5a89eea7372f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T04:11:55Z"
    - latency: 9.243384ms
      message: 'load-balancer-api-external: resolved host name ad1ffd3470c964525bf85b94a3f0e283-c3df5a89eea7372f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T04:11:55Z"
    - latency: 4.500178ms
      message: 'load-balancer-api-external: tcp connection to ad1ffd3470c964525bf85b94a3f0e283-c3df5a89eea7372f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T04:10:55Z"
    - latency: 7.473736ms
      message: 'load-balancer-api-external: resolved host name ad1ffd3470c964525bf85b94a3f0e283-c3df5a89eea7372f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T04:10:55Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-10T03:38:54Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-167-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-167.ec2.internal
      uid: 4aeaca18-bbba-4844-944a-c4305451299f
    resourceVersion: "56485"
    uid: 448b2d5d-a6df-447b-b81f-0cfe35cbbd4c
  spec:
    sourcePod: network-check-source-869dcfcdcd-nkxvw
    targetEndpoint: ad1ffd3470c964525bf85b94a3f0e283-c3df5a89eea7372f.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-10T03:44:55Z"
      message: 'load-balancer-api-internal: tcp connection to ad1ffd3470c964525bf85b94a3f0e283-c3df5a89eea7372f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.716778ms
      message: 'load-balancer-api-internal: tcp connection to ad1ffd3470c964525bf85b94a3f0e283-c3df5a89eea7372f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T04:14:55Z"
    - latency: 6.952387ms
      message: 'load-balancer-api-internal: resolved host name ad1ffd3470c964525bf85b94a3f0e283-c3df5a89eea7372f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T04:14:55Z"
    - latency: 4.236042ms
      message: 'load-balancer-api-internal: tcp connection to ad1ffd3470c964525bf85b94a3f0e283-c3df5a89eea7372f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T04:13:55Z"
    - latency: 7.111363ms
      message: 'load-balancer-api-internal: resolved host name ad1ffd3470c964525bf85b94a3f0e283-c3df5a89eea7372f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T04:13:55Z"
    - latency: 4.687353ms
      message: 'load-balancer-api-internal: tcp connection to ad1ffd3470c964525bf85b94a3f0e283-c3df5a89eea7372f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T04:12:55Z"
    - latency: 6.046894ms
      message: 'load-balancer-api-internal: resolved host name ad1ffd3470c964525bf85b94a3f0e283-c3df5a89eea7372f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T04:12:55Z"
    - latency: 4.10281ms
      message: 'load-balancer-api-internal: tcp connection to ad1ffd3470c964525bf85b94a3f0e283-c3df5a89eea7372f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T04:11:55Z"
    - latency: 9.307363ms
      message: 'load-balancer-api-internal: resolved host name ad1ffd3470c964525bf85b94a3f0e283-c3df5a89eea7372f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T04:11:55Z"
    - latency: 4.474768ms
      message: 'load-balancer-api-internal: tcp connection to ad1ffd3470c964525bf85b94a3f0e283-c3df5a89eea7372f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T04:10:55Z"
    - latency: 7.512104ms
      message: 'load-balancer-api-internal: resolved host name ad1ffd3470c964525bf85b94a3f0e283-c3df5a89eea7372f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T04:10:55Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-10T03:38:54Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-167-to-network-check-target-ip-10-0-129-177
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-167.ec2.internal
      uid: 4aeaca18-bbba-4844-944a-c4305451299f
    resourceVersion: "55584"
    uid: 6f01e7f0-0761-4cd3-ae73-4aa370f3c0eb
  spec:
    sourcePod: network-check-source-869dcfcdcd-nkxvw
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-10T03:45:55Z"
      message: 'network-check-target-ip-10-0-129-177: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.138239ms
      message: 'network-check-target-ip-10-0-129-177: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T04:13:55Z"
    - latency: 2.187242ms
      message: 'network-check-target-ip-10-0-129-177: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T04:12:55Z"
    - latency: 2.078918ms
      message: 'network-check-target-ip-10-0-129-177: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T04:11:55Z"
    - latency: 2.437512ms
      message: 'network-check-target-ip-10-0-129-177: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T04:10:55Z"
    - latency: 2.086378ms
      message: 'network-check-target-ip-10-0-129-177: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T04:09:55Z"
    - latency: 2.067713ms
      message: 'network-check-target-ip-10-0-129-177: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T04:08:55Z"
    - latency: 2.018607ms
      message: 'network-check-target-ip-10-0-129-177: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T04:07:55Z"
    - latency: 2.658678ms
      message: 'network-check-target-ip-10-0-129-177: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T04:06:55Z"
    - latency: 2.361102ms
      message: 'network-check-target-ip-10-0-129-177: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T04:05:55Z"
    - latency: 1.880924ms
      message: 'network-check-target-ip-10-0-129-177: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T04:04:55Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-10T03:38:54Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-167-to-network-check-target-ip-10-0-140-167
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-167.ec2.internal
      uid: 4aeaca18-bbba-4844-944a-c4305451299f
    resourceVersion: "55583"
    uid: 18f9f157-9ed1-46be-a90c-1946f49aab2a
  spec:
    sourcePod: network-check-source-869dcfcdcd-nkxvw
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-10T03:45:55Z"
      message: 'network-check-target-ip-10-0-140-167: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 924.073µs
      message: 'network-check-target-ip-10-0-140-167: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T04:13:55Z"
    - latency: 840.553µs
      message: 'network-check-target-ip-10-0-140-167: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T04:12:55Z"
    - latency: 1.078955ms
      message: 'network-check-target-ip-10-0-140-167: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T04:11:55Z"
    - latency: 990.764µs
      message: 'network-check-target-ip-10-0-140-167: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T04:10:55Z"
    - latency: 955.501µs
      message: 'network-check-target-ip-10-0-140-167: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T04:09:55Z"
    - latency: 944.234µs
      message: 'network-check-target-ip-10-0-140-167: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T04:08:55Z"
    - latency: 853.123µs
      message: 'network-check-target-ip-10-0-140-167: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T04:07:55Z"
    - latency: 1.434548ms
      message: 'network-check-target-ip-10-0-140-167: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T04:06:55Z"
    - latency: 1.046897ms
      message: 'network-check-target-ip-10-0-140-167: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T04:05:55Z"
    - latency: 876.391µs
      message: 'network-check-target-ip-10-0-140-167: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T04:04:55Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-10T03:38:54Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-167-to-network-check-target-ip-10-0-143-142
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-167.ec2.internal
      uid: 4aeaca18-bbba-4844-944a-c4305451299f
    resourceVersion: "55585"
    uid: 4ed3cb3e-0fa8-482e-8384-a2a4197d3486
  spec:
    sourcePod: network-check-source-869dcfcdcd-nkxvw
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-10T03:45:55Z"
      message: 'network-check-target-ip-10-0-143-142: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.582372ms
      message: 'network-check-target-ip-10-0-143-142: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T04:13:55Z"
    - latency: 2.452877ms
      message: 'network-check-target-ip-10-0-143-142: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T04:12:55Z"
    - latency: 2.628371ms
      message: 'network-check-target-ip-10-0-143-142: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T04:11:55Z"
    - latency: 2.370989ms
      message: 'network-check-target-ip-10-0-143-142: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T04:10:55Z"
    - latency: 2.615608ms
      message: 'network-check-target-ip-10-0-143-142: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T04:09:55Z"
    - latency: 2.361143ms
      message: 'network-check-target-ip-10-0-143-142: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T04:08:55Z"
    - latency: 2.241052ms
      message: 'network-check-target-ip-10-0-143-142: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T04:07:55Z"
    - latency: 2.459035ms
      message: 'network-check-target-ip-10-0-143-142: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T04:06:55Z"
    - latency: 2.639562ms
      message: 'network-check-target-ip-10-0-143-142: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T04:05:55Z"
    - latency: 2.165902ms
      message: 'network-check-target-ip-10-0-143-142: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T04:04:55Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-10T03:38:54Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-167-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-167.ec2.internal
      uid: 4aeaca18-bbba-4844-944a-c4305451299f
    resourceVersion: "56484"
    uid: c95a1755-2bd6-42d4-ab70-0078648fc095
  spec:
    sourcePod: network-check-source-869dcfcdcd-nkxvw
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-10T03:44:55Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 773.316µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T04:14:55Z"
    - latency: 1.747124ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T04:14:55Z"
    - latency: 881.366µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T04:13:55Z"
    - latency: 1.944431ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T04:13:55Z"
    - latency: 1.032757ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T04:12:55Z"
    - latency: 1.630468ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T04:12:55Z"
    - latency: 800.12µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T04:11:55Z"
    - latency: 1.760041ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T04:11:55Z"
    - latency: 866.955µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T04:10:55Z"
    - latency: 1.782388ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T04:10:55Z"
kind: List
metadata:
  resourceVersion: ""