apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T10:31:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-188-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-188.ec2.internal
      uid: 3b935b47-4437-445f-8d5a-0a72f808bbf1
    resourceVersion: "32309"
    uid: 7fd17b74-8e56-4a43-869c-dd71f90cf296
  spec:
    sourcePod: network-check-source-7d88cb55d8-2pzw7
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T10:38:36Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.044592ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T11:13:36Z"
    - latency: 1.388106ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T11:12:36Z"
    - latency: 888.421µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T11:11:36Z"
    - latency: 1.412653ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T11:10:36Z"
    - latency: 913.333µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T11:09:36Z"
    - latency: 946.411µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T11:08:36Z"
    - latency: 1.08123ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T11:07:36Z"
    - latency: 863.827µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T11:06:36Z"
    - latency: 912.597µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T11:05:36Z"
    - latency: 867.928µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T11:04:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T10:31:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-188-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-188.ec2.internal
      uid: 3b935b47-4437-445f-8d5a-0a72f808bbf1
    resourceVersion: "32310"
    uid: 9459f3f9-e983-4e32-907a-1c9391512778
  spec:
    sourcePod: network-check-source-7d88cb55d8-2pzw7
    targetEndpoint: aa0499736c9dd4ac2bfe96fa582abf56-267834f97d642aad.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T10:37:36Z"
      message: 'load-balancer-api-external: tcp connection to aa0499736c9dd4ac2bfe96fa582abf56-267834f97d642aad.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.868809ms
      message: 'load-balancer-api-external: tcp connection to aa0499736c9dd4ac2bfe96fa582abf56-267834f97d642aad.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T11:13:36Z"
    - latency: 8.916601ms
      message: 'load-balancer-api-external: resolved host name aa0499736c9dd4ac2bfe96fa582abf56-267834f97d642aad.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T11:13:36Z"
    - latency: 4.540131ms
      message: 'load-balancer-api-external: tcp connection to aa0499736c9dd4ac2bfe96fa582abf56-267834f97d642aad.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T11:12:36Z"
    - latency: 8.626657ms
      message: 'load-balancer-api-external: resolved host name aa0499736c9dd4ac2bfe96fa582abf56-267834f97d642aad.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T11:12:36Z"
    - latency: 5.050961ms
      message: 'load-balancer-api-external: tcp connection to aa0499736c9dd4ac2bfe96fa582abf56-267834f97d642aad.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T11:11:36Z"
    - latency: 8.201709ms
      message: 'load-balancer-api-external: resolved host name aa0499736c9dd4ac2bfe96fa582abf56-267834f97d642aad.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T11:11:36Z"
    - latency: 5.640966ms
      message: 'load-balancer-api-external: tcp connection to aa0499736c9dd4ac2bfe96fa582abf56-267834f97d642aad.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T11:10:36Z"
    - latency: 8.616351ms
      message: 'load-balancer-api-external: resolved host name aa0499736c9dd4ac2bfe96fa582abf56-267834f97d642aad.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T11:10:36Z"
    - latency: 3.877494ms
      message: 'load-balancer-api-external: tcp connection to aa0499736c9dd4ac2bfe96fa582abf56-267834f97d642aad.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T11:09:36Z"
    - latency: 9.216528ms
      message: 'load-balancer-api-external: resolved host name aa0499736c9dd4ac2bfe96fa582abf56-267834f97d642aad.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T11:09:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T10:31:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-188-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-188.ec2.internal
      uid: 3b935b47-4437-445f-8d5a-0a72f808bbf1
    resourceVersion: "32311"
    uid: 6e6f270b-d5b4-4cf7-8c4f-3b757c803fd5
  spec:
    sourcePod: network-check-source-7d88cb55d8-2pzw7
    targetEndpoint: aa0499736c9dd4ac2bfe96fa582abf56-267834f97d642aad.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T10:37:36Z"
      message: 'load-balancer-api-internal: tcp connection to aa0499736c9dd4ac2bfe96fa582abf56-267834f97d642aad.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.085442ms
      message: 'load-balancer-api-internal: tcp connection to aa0499736c9dd4ac2bfe96fa582abf56-267834f97d642aad.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T11:13:36Z"
    - latency: 8.838532ms
      message: 'load-balancer-api-internal: resolved host name aa0499736c9dd4ac2bfe96fa582abf56-267834f97d642aad.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T11:13:36Z"
    - latency: 5.528898ms
      message: 'load-balancer-api-internal: tcp connection to aa0499736c9dd4ac2bfe96fa582abf56-267834f97d642aad.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T11:12:36Z"
    - latency: 8.674259ms
      message: 'load-balancer-api-internal: resolved host name aa0499736c9dd4ac2bfe96fa582abf56-267834f97d642aad.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T11:12:36Z"
    - latency: 5.026166ms
      message: 'load-balancer-api-internal: tcp connection to aa0499736c9dd4ac2bfe96fa582abf56-267834f97d642aad.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T11:11:36Z"
    - latency: 8.311305ms
      message: 'load-balancer-api-internal: resolved host name aa0499736c9dd4ac2bfe96fa582abf56-267834f97d642aad.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T11:11:36Z"
    - latency: 5.636954ms
      message: 'load-balancer-api-internal: tcp connection to aa0499736c9dd4ac2bfe96fa582abf56-267834f97d642aad.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T11:10:36Z"
    - latency: 8.698052ms
      message: 'load-balancer-api-internal: resolved host name aa0499736c9dd4ac2bfe96fa582abf56-267834f97d642aad.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T11:10:36Z"
    - latency: 4.149605ms
      message: 'load-balancer-api-internal: tcp connection to aa0499736c9dd4ac2bfe96fa582abf56-267834f97d642aad.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T11:09:36Z"
    - latency: 9.322588ms
      message: 'load-balancer-api-internal: resolved host name aa0499736c9dd4ac2bfe96fa582abf56-267834f97d642aad.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T11:09:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T10:31:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-188-to-network-check-target-ip-10-0-129-138
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-188.ec2.internal
      uid: 3b935b47-4437-445f-8d5a-0a72f808bbf1
    resourceVersion: "32306"
    uid: bcc9a0f9-7e5f-44f0-8356-f7645ba769c5
  spec:
    sourcePod: network-check-source-7d88cb55d8-2pzw7
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T10:38:36Z"
      message: 'network-check-target-ip-10-0-129-138: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.374797ms
      message: 'network-check-target-ip-10-0-129-138: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T11:13:36Z"
    - latency: 2.226771ms
      message: 'network-check-target-ip-10-0-129-138: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T11:12:36Z"
    - latency: 2.417396ms
      message: 'network-check-target-ip-10-0-129-138: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T11:11:36Z"
    - latency: 2.041964ms
      message: 'network-check-target-ip-10-0-129-138: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T11:10:36Z"
    - latency: 2.316833ms
      message: 'network-check-target-ip-10-0-129-138: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T11:09:36Z"
    - latency: 2.337788ms
      message: 'network-check-target-ip-10-0-129-138: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T11:08:36Z"
    - latency: 2.315773ms
      message: 'network-check-target-ip-10-0-129-138: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T11:07:36Z"
    - latency: 2.392439ms
      message: 'network-check-target-ip-10-0-129-138: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T11:06:36Z"
    - latency: 2.38927ms
      message: 'network-check-target-ip-10-0-129-138: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T11:05:36Z"
    - latency: 2.113324ms
      message: 'network-check-target-ip-10-0-129-138: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T11:04:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T10:31:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-188-to-network-check-target-ip-10-0-137-188
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-188.ec2.internal
      uid: 3b935b47-4437-445f-8d5a-0a72f808bbf1
    resourceVersion: "32304"
    uid: 5dfa9b15-a917-49de-923d-4c7470770ada
  spec:
    sourcePod: network-check-source-7d88cb55d8-2pzw7
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T10:38:36Z"
      message: 'network-check-target-ip-10-0-137-188: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 888.949µs
      message: 'network-check-target-ip-10-0-137-188: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T11:13:36Z"
    - latency: 1.535461ms
      message: 'network-check-target-ip-10-0-137-188: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T11:12:36Z"
    - latency: 975.754µs
      message: 'network-check-target-ip-10-0-137-188: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T11:11:36Z"
    - latency: 880.779µs
      message: 'network-check-target-ip-10-0-137-188: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T11:10:36Z"
    - latency: 1.180763ms
      message: 'network-check-target-ip-10-0-137-188: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T11:09:36Z"
    - latency: 987.071µs
      message: 'network-check-target-ip-10-0-137-188: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T11:08:36Z"
    - latency: 742.235µs
      message: 'network-check-target-ip-10-0-137-188: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T11:07:36Z"
    - latency: 951.086µs
      message: 'network-check-target-ip-10-0-137-188: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T11:06:36Z"
    - latency: 988.232µs
      message: 'network-check-target-ip-10-0-137-188: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T11:05:36Z"
    - latency: 892.241µs
      message: 'network-check-target-ip-10-0-137-188: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T11:04:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T10:31:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-188-to-network-check-target-ip-10-0-143-36
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-188.ec2.internal
      uid: 3b935b47-4437-445f-8d5a-0a72f808bbf1
    resourceVersion: "32305"
    uid: be12332d-23f7-42b4-a995-d6e75d8736e7
  spec:
    sourcePod: network-check-source-7d88cb55d8-2pzw7
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T10:38:36Z"
      message: 'network-check-target-ip-10-0-143-36: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.441209ms
      message: 'network-check-target-ip-10-0-143-36: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T11:13:36Z"
    - latency: 3.130835ms
      message: 'network-check-target-ip-10-0-143-36: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T11:12:36Z"
    - latency: 2.289162ms
      message: 'network-check-target-ip-10-0-143-36: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T11:11:36Z"
    - latency: 2.794261ms
      message: 'network-check-target-ip-10-0-143-36: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T11:10:36Z"
    - latency: 2.189845ms
      message: 'network-check-target-ip-10-0-143-36: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T11:09:36Z"
    - latency: 2.277621ms
      message: 'network-check-target-ip-10-0-143-36: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T11:08:36Z"
    - latency: 2.343537ms
      message: 'network-check-target-ip-10-0-143-36: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T11:07:36Z"
    - latency: 2.425522ms
      message: 'network-check-target-ip-10-0-143-36: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T11:06:36Z"
    - latency: 2.411342ms
      message: 'network-check-target-ip-10-0-143-36: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T11:05:36Z"
    - latency: 2.402319ms
      message: 'network-check-target-ip-10-0-143-36: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T11:04:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T10:31:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-188-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-188.ec2.internal
      uid: 3b935b47-4437-445f-8d5a-0a72f808bbf1
    resourceVersion: "32307"
    uid: e52fcd8f-9ba7-42dd-a0c6-ed81845efbad
  spec:
    sourcePod: network-check-source-7d88cb55d8-2pzw7
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T10:37:36Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.017628ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T11:13:36Z"
    - latency: 2.251361ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T11:13:36Z"
    - latency: 959.932µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T11:12:36Z"
    - latency: 2.208629ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T11:12:36Z"
    - latency: 758.477µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T11:11:36Z"
    - latency: 1.753289ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T11:11:36Z"
    - latency: 776.603µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T11:10:36Z"
    - latency: 1.741168ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T11:10:36Z"
    - latency: 1.2634ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T11:09:36Z"
    - latency: 1.783921ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T11:09:36Z"
kind: List
metadata:
  resourceVersion: ""