apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T18:01:20Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-5-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-5.ec2.internal
      uid: 054e96e6-5905-4073-bd6c-03e06b0c812d
    resourceVersion: "16116"
    uid: b0481fe7-fdec-47c9-ba1c-7b3a785f09a5
  spec:
    sourcePod: network-check-source-7d88cb55d8-jjqmd
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T18:08:21Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.06215ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:15:21Z"
    - latency: 912.581µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:14:21Z"
    - latency: 1.095959ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:13:21Z"
    - latency: 1.156375ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:12:21Z"
    - latency: 960.496µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:11:21Z"
    - latency: 899.1µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:10:21Z"
    - latency: 851.606µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:09:21Z"
    - latency: 1.1596ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:08:21Z"
    - latency: 1.020012ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:07:21Z"
    - latency: 977.072µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:06:21Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T18:01:20Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-5-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-5.ec2.internal
      uid: 054e96e6-5905-4073-bd6c-03e06b0c812d
    resourceVersion: "15487"
    uid: 70d1f3d4-0f4d-46e3-98e3-edb102146df1
  spec:
    sourcePod: network-check-source-7d88cb55d8-jjqmd
    targetEndpoint: a0982115c59e6429eb4ae3280bae5d35-0f670e03ced74337.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T18:07:21Z"
      message: 'load-balancer-api-external: tcp connection to a0982115c59e6429eb4ae3280bae5d35-0f670e03ced74337.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.617941ms
      message: 'load-balancer-api-external: tcp connection to a0982115c59e6429eb4ae3280bae5d35-0f670e03ced74337.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:13:21Z"
    - latency: 7.576823ms
      message: 'load-balancer-api-external: resolved host name a0982115c59e6429eb4ae3280bae5d35-0f670e03ced74337.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T18:13:21Z"
    - latency: 5.680413ms
      message: 'load-balancer-api-external: tcp connection to a0982115c59e6429eb4ae3280bae5d35-0f670e03ced74337.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:12:21Z"
    - latency: 8.57732ms
      message: 'load-balancer-api-external: resolved host name a0982115c59e6429eb4ae3280bae5d35-0f670e03ced74337.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T18:12:21Z"
    - latency: 4.704895ms
      message: 'load-balancer-api-external: tcp connection to a0982115c59e6429eb4ae3280bae5d35-0f670e03ced74337.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:11:21Z"
    - latency: 8.208035ms
      message: 'load-balancer-api-external: resolved host name a0982115c59e6429eb4ae3280bae5d35-0f670e03ced74337.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T18:11:21Z"
    - latency: 4.718414ms
      message: 'load-balancer-api-external: tcp connection to a0982115c59e6429eb4ae3280bae5d35-0f670e03ced74337.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:10:21Z"
    - latency: 8.028009ms
      message: 'load-balancer-api-external: resolved host name a0982115c59e6429eb4ae3280bae5d35-0f670e03ced74337.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T18:10:21Z"
    - latency: 5.301307ms
      message: 'load-balancer-api-external: tcp connection to a0982115c59e6429eb4ae3280bae5d35-0f670e03ced74337.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:09:21Z"
    - latency: 7.581792ms
      message: 'load-balancer-api-external: resolved host name a0982115c59e6429eb4ae3280bae5d35-0f670e03ced74337.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T18:09:21Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T18:01:20Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-5-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-5.ec2.internal
      uid: 054e96e6-5905-4073-bd6c-03e06b0c812d
    resourceVersion: "15486"
    uid: ff108c24-81fa-4f19-9c40-9242e7a69094
  spec:
    sourcePod: network-check-source-7d88cb55d8-jjqmd
    targetEndpoint: a0982115c59e6429eb4ae3280bae5d35-0f670e03ced74337.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T18:07:21Z"
      message: 'load-balancer-api-internal: tcp connection to a0982115c59e6429eb4ae3280bae5d35-0f670e03ced74337.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.611363ms
      message: 'load-balancer-api-internal: tcp connection to a0982115c59e6429eb4ae3280bae5d35-0f670e03ced74337.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:13:21Z"
    - latency: 7.640077ms
      message: 'load-balancer-api-internal: resolved host name a0982115c59e6429eb4ae3280bae5d35-0f670e03ced74337.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T18:13:21Z"
    - latency: 5.692192ms
      message: 'load-balancer-api-internal: tcp connection to a0982115c59e6429eb4ae3280bae5d35-0f670e03ced74337.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:12:21Z"
    - latency: 8.65898ms
      message: 'load-balancer-api-internal: resolved host name a0982115c59e6429eb4ae3280bae5d35-0f670e03ced74337.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T18:12:21Z"
    - latency: 4.696208ms
      message: 'load-balancer-api-internal: tcp connection to a0982115c59e6429eb4ae3280bae5d35-0f670e03ced74337.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:11:21Z"
    - latency: 8.347827ms
      message: 'load-balancer-api-internal: resolved host name a0982115c59e6429eb4ae3280bae5d35-0f670e03ced74337.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T18:11:21Z"
    - latency: 4.721414ms
      message: 'load-balancer-api-internal: tcp connection to a0982115c59e6429eb4ae3280bae5d35-0f670e03ced74337.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:10:21Z"
    - latency: 8.083277ms
      message: 'load-balancer-api-internal: resolved host name a0982115c59e6429eb4ae3280bae5d35-0f670e03ced74337.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T18:10:21Z"
    - latency: 5.344697ms
      message: 'load-balancer-api-internal: tcp connection to a0982115c59e6429eb4ae3280bae5d35-0f670e03ced74337.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:09:21Z"
    - latency: 7.606351ms
      message: 'load-balancer-api-internal: resolved host name a0982115c59e6429eb4ae3280bae5d35-0f670e03ced74337.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T18:09:21Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T18:01:20Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-5-to-network-check-target-ip-10-0-128-27
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-5.ec2.internal
      uid: 054e96e6-5905-4073-bd6c-03e06b0c812d
    resourceVersion: "16115"
    uid: e2b58e6b-48e9-4d1f-87e5-a19196f4f696
  spec:
    sourcePod: network-check-source-7d88cb55d8-jjqmd
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T18:08:21Z"
      message: 'network-check-target-ip-10-0-128-27: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.910055ms
      message: 'network-check-target-ip-10-0-128-27: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:15:21Z"
    - latency: 1.76951ms
      message: 'network-check-target-ip-10-0-128-27: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:14:21Z"
    - latency: 1.894067ms
      message: 'network-check-target-ip-10-0-128-27: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:13:21Z"
    - latency: 1.90901ms
      message: 'network-check-target-ip-10-0-128-27: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:12:21Z"
    - latency: 1.812743ms
      message: 'network-check-target-ip-10-0-128-27: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:11:21Z"
    - latency: 1.845054ms
      message: 'network-check-target-ip-10-0-128-27: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:10:21Z"
    - latency: 1.857089ms
      message: 'network-check-target-ip-10-0-128-27: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:09:21Z"
    - latency: 1.915066ms
      message: 'network-check-target-ip-10-0-128-27: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:08:21Z"
    - latency: 1.92402ms
      message: 'network-check-target-ip-10-0-128-27: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:07:21Z"
    - latency: 2.233824ms
      message: 'network-check-target-ip-10-0-128-27: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:06:21Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T18:01:20Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-5-to-network-check-target-ip-10-0-139-5
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-5.ec2.internal
      uid: 054e96e6-5905-4073-bd6c-03e06b0c812d
    resourceVersion: "16113"
    uid: 447b0d09-8933-4de6-a985-7e6e6954f7bf
  spec:
    sourcePod: network-check-source-7d88cb55d8-jjqmd
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T18:08:21Z"
      message: 'network-check-target-ip-10-0-139-5: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 937.518µs
      message: 'network-check-target-ip-10-0-139-5: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:15:21Z"
    - latency: 940.098µs
      message: 'network-check-target-ip-10-0-139-5: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:14:21Z"
    - latency: 837.914µs
      message: 'network-check-target-ip-10-0-139-5: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:13:21Z"
    - latency: 1.081847ms
      message: 'network-check-target-ip-10-0-139-5: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:12:21Z"
    - latency: 1.235937ms
      message: 'network-check-target-ip-10-0-139-5: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:11:21Z"
    - latency: 786.511µs
      message: 'network-check-target-ip-10-0-139-5: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:10:21Z"
    - latency: 907.246µs
      message: 'network-check-target-ip-10-0-139-5: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:09:21Z"
    - latency: 844.52µs
      message: 'network-check-target-ip-10-0-139-5: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:08:21Z"
    - latency: 893.573µs
      message: 'network-check-target-ip-10-0-139-5: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:07:21Z"
    - latency: 1.522782ms
      message: 'network-check-target-ip-10-0-139-5: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:06:21Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T18:01:20Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-5-to-network-check-target-ip-10-0-140-128
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-5.ec2.internal
      uid: 054e96e6-5905-4073-bd6c-03e06b0c812d
    resourceVersion: "16114"
    uid: bff04a76-05d2-4b35-bc56-9135796587fc
  spec:
    sourcePod: network-check-source-7d88cb55d8-jjqmd
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T18:08:21Z"
      message: 'network-check-target-ip-10-0-140-128: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.428672ms
      message: 'network-check-target-ip-10-0-140-128: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:15:21Z"
    - latency: 2.288605ms
      message: 'network-check-target-ip-10-0-140-128: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:14:21Z"
    - latency: 2.251593ms
      message: 'network-check-target-ip-10-0-140-128: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:13:21Z"
    - latency: 2.421745ms
      message: 'network-check-target-ip-10-0-140-128: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:12:21Z"
    - latency: 2.379851ms
      message: 'network-check-target-ip-10-0-140-128: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:11:21Z"
    - latency: 2.302136ms
      message: 'network-check-target-ip-10-0-140-128: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:10:21Z"
    - latency: 2.215578ms
      message: 'network-check-target-ip-10-0-140-128: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:09:21Z"
    - latency: 2.293601ms
      message: 'network-check-target-ip-10-0-140-128: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:08:21Z"
    - latency: 2.215974ms
      message: 'network-check-target-ip-10-0-140-128: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:07:21Z"
    - latency: 2.273872ms
      message: 'network-check-target-ip-10-0-140-128: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:06:21Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T18:01:20Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-5-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-5.ec2.internal
      uid: 054e96e6-5905-4073-bd6c-03e06b0c812d
    resourceVersion: "15485"
    uid: a9153048-e8dd-41fb-a040-b8e37b867781
  spec:
    sourcePod: network-check-source-7d88cb55d8-jjqmd
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T18:07:21Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 787.171µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:13:21Z"
    - latency: 1.615254ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T18:13:21Z"
    - latency: 1.219606ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:12:21Z"
    - latency: 1.785812ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T18:12:21Z"
    - latency: 735.116µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:11:21Z"
    - latency: 1.823287ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T18:11:21Z"
    - latency: 771.904µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:10:21Z"
    - latency: 1.633513ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T18:10:21Z"
    - latency: 810.07µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:09:21Z"
    - latency: 1.655553ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T18:09:21Z"
kind: List
metadata:
  resourceVersion: ""