apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T12:05:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-160-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-160.ec2.internal
      uid: 312c5c34-15dc-4060-ac9e-db0458f43175
    resourceVersion: "53262"
    uid: 67638ba8-a9af-4e6d-b420-17f46891f27f
  spec:
    sourcePod: network-check-source-989f8b8dc-m2hgr
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T12:12:41Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.045218ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T12:40:41Z"
    - latency: 1.103146ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T12:39:41Z"
    - latency: 1.1299ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T12:38:41Z"
    - latency: 1.724859ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T12:37:41Z"
    - latency: 1.075931ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T12:36:41Z"
    - latency: 913.552µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T12:35:41Z"
    - latency: 1.021258ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T12:34:41Z"
    - latency: 1.045609ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T12:33:41Z"
    - latency: 972.983µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T12:32:41Z"
    - latency: 1.019895ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T12:31:41Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T12:05:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-160-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-160.ec2.internal
      uid: 312c5c34-15dc-4060-ac9e-db0458f43175
    resourceVersion: "54187"
    uid: 75ae6ec8-c0af-487e-8c95-35af9b182b35
  spec:
    sourcePod: network-check-source-989f8b8dc-m2hgr
    targetEndpoint: ae1498562bd504bb4b4c92f50b04da12-8685d3290c4b7305.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T12:11:41Z"
      message: 'load-balancer-api-external: tcp connection to ae1498562bd504bb4b4c92f50b04da12-8685d3290c4b7305.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.38284ms
      message: 'load-balancer-api-external: tcp connection to ae1498562bd504bb4b4c92f50b04da12-8685d3290c4b7305.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T12:41:41Z"
    - latency: 8.23417ms
      message: 'load-balancer-api-external: resolved host name ae1498562bd504bb4b4c92f50b04da12-8685d3290c4b7305.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T12:41:41Z"
    - latency: 5.543687ms
      message: 'load-balancer-api-external: tcp connection to ae1498562bd504bb4b4c92f50b04da12-8685d3290c4b7305.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T12:40:41Z"
    - latency: 9.082827ms
      message: 'load-balancer-api-external: resolved host name ae1498562bd504bb4b4c92f50b04da12-8685d3290c4b7305.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T12:40:41Z"
    - latency: 8.370005ms
      message: 'load-balancer-api-external: tcp connection to ae1498562bd504bb4b4c92f50b04da12-8685d3290c4b7305.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T12:39:41Z"
    - latency: 9.09698ms
      message: 'load-balancer-api-external: resolved host name ae1498562bd504bb4b4c92f50b04da12-8685d3290c4b7305.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T12:39:41Z"
    - latency: 5.647178ms
      message: 'load-balancer-api-external: tcp connection to ae1498562bd504bb4b4c92f50b04da12-8685d3290c4b7305.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T12:38:41Z"
    - latency: 9.192058ms
      message: 'load-balancer-api-external: resolved host name ae1498562bd504bb4b4c92f50b04da12-8685d3290c4b7305.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T12:38:41Z"
    - latency: 5.87836ms
      message: 'load-balancer-api-external: tcp connection to ae1498562bd504bb4b4c92f50b04da12-8685d3290c4b7305.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T12:37:41Z"
    - latency: 6.416702ms
      message: 'load-balancer-api-external: resolved host name ae1498562bd504bb4b4c92f50b04da12-8685d3290c4b7305.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T12:37:41Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T12:05:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-160-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-160.ec2.internal
      uid: 312c5c34-15dc-4060-ac9e-db0458f43175
    resourceVersion: "54186"
    uid: 34a82d8c-a486-4bc0-beba-fbc1a53c2467
  spec:
    sourcePod: network-check-source-989f8b8dc-m2hgr
    targetEndpoint: ae1498562bd504bb4b4c92f50b04da12-8685d3290c4b7305.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T12:11:41Z"
      message: 'load-balancer-api-internal: tcp connection to ae1498562bd504bb4b4c92f50b04da12-8685d3290c4b7305.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.428935ms
      message: 'load-balancer-api-internal: tcp connection to ae1498562bd504bb4b4c92f50b04da12-8685d3290c4b7305.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T12:41:41Z"
    - latency: 8.133044ms
      message: 'load-balancer-api-internal: resolved host name ae1498562bd504bb4b4c92f50b04da12-8685d3290c4b7305.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T12:41:41Z"
    - latency: 5.575061ms
      message: 'load-balancer-api-internal: tcp connection to ae1498562bd504bb4b4c92f50b04da12-8685d3290c4b7305.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T12:40:41Z"
    - latency: 9.047108ms
      message: 'load-balancer-api-internal: resolved host name ae1498562bd504bb4b4c92f50b04da12-8685d3290c4b7305.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T12:40:41Z"
    - latency: 4.037444ms
      message: 'load-balancer-api-internal: tcp connection to ae1498562bd504bb4b4c92f50b04da12-8685d3290c4b7305.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T12:39:41Z"
    - latency: 9.053422ms
      message: 'load-balancer-api-internal: resolved host name ae1498562bd504bb4b4c92f50b04da12-8685d3290c4b7305.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T12:39:41Z"
    - latency: 5.630999ms
      message: 'load-balancer-api-internal: tcp connection to ae1498562bd504bb4b4c92f50b04da12-8685d3290c4b7305.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T12:38:41Z"
    - latency: 9.112256ms
      message: 'load-balancer-api-internal: resolved host name ae1498562bd504bb4b4c92f50b04da12-8685d3290c4b7305.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T12:38:41Z"
    - latency: 5.886726ms
      message: 'load-balancer-api-internal: tcp connection to ae1498562bd504bb4b4c92f50b04da12-8685d3290c4b7305.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T12:37:41Z"
    - latency: 6.959678ms
      message: 'load-balancer-api-internal: resolved host name ae1498562bd504bb4b4c92f50b04da12-8685d3290c4b7305.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T12:37:41Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T12:05:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-160-to-network-check-target-ip-10-0-137-232
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-160.ec2.internal
      uid: 312c5c34-15dc-4060-ac9e-db0458f43175
    resourceVersion: "53261"
    uid: 8334f4f3-0219-4b1e-aa65-35428cbf371f
  spec:
    sourcePod: network-check-source-989f8b8dc-m2hgr
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T12:12:41Z"
      message: 'network-check-target-ip-10-0-137-232: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.908741ms
      message: 'network-check-target-ip-10-0-137-232: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T12:40:41Z"
    - latency: 2.477238ms
      message: 'network-check-target-ip-10-0-137-232: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T12:39:41Z"
    - latency: 2.725504ms
      message: 'network-check-target-ip-10-0-137-232: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T12:38:41Z"
    - latency: 2.459463ms
      message: 'network-check-target-ip-10-0-137-232: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T12:37:41Z"
    - latency: 2.511312ms
      message: 'network-check-target-ip-10-0-137-232: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T12:36:41Z"
    - latency: 2.233154ms
      message: 'network-check-target-ip-10-0-137-232: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T12:35:41Z"
    - latency: 2.527909ms
      message: 'network-check-target-ip-10-0-137-232: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T12:34:41Z"
    - latency: 3.005285ms
      message: 'network-check-target-ip-10-0-137-232: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T12:33:41Z"
    - latency: 2.521633ms
      message: 'network-check-target-ip-10-0-137-232: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T12:32:41Z"
    - latency: 2.366582ms
      message: 'network-check-target-ip-10-0-137-232: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T12:31:41Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T12:05:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-160-to-network-check-target-ip-10-0-138-160
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-160.ec2.internal
      uid: 312c5c34-15dc-4060-ac9e-db0458f43175
    resourceVersion: "53259"
    uid: d423a579-f8fe-4c2f-9725-42a167e0966b
  spec:
    sourcePod: network-check-source-989f8b8dc-m2hgr
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T12:12:41Z"
      message: 'network-check-target-ip-10-0-138-160: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.028756ms
      message: 'network-check-target-ip-10-0-138-160: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T12:40:41Z"
    - latency: 998.806µs
      message: 'network-check-target-ip-10-0-138-160: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T12:39:41Z"
    - latency: 1.008217ms
      message: 'network-check-target-ip-10-0-138-160: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T12:38:41Z"
    - latency: 1.02866ms
      message: 'network-check-target-ip-10-0-138-160: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T12:37:41Z"
    - latency: 880.141µs
      message: 'network-check-target-ip-10-0-138-160: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T12:36:41Z"
    - latency: 1.392846ms
      message: 'network-check-target-ip-10-0-138-160: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T12:35:41Z"
    - latency: 1.371611ms
      message: 'network-check-target-ip-10-0-138-160: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T12:34:41Z"
    - latency: 927.836µs
      message: 'network-check-target-ip-10-0-138-160: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T12:33:41Z"
    - latency: 1.574993ms
      message: 'network-check-target-ip-10-0-138-160: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T12:32:41Z"
    - latency: 1.627557ms
      message: 'network-check-target-ip-10-0-138-160: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T12:31:41Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T12:05:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-160-to-network-check-target-ip-10-0-138-89
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-160.ec2.internal
      uid: 312c5c34-15dc-4060-ac9e-db0458f43175
    resourceVersion: "53260"
    uid: d8d892e3-0e78-4fa2-b454-3141717f6f98
  spec:
    sourcePod: network-check-source-989f8b8dc-m2hgr
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T12:12:41Z"
      message: 'network-check-target-ip-10-0-138-89: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.27248ms
      message: 'network-check-target-ip-10-0-138-89: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T12:40:41Z"
    - latency: 2.420398ms
      message: 'network-check-target-ip-10-0-138-89: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T12:39:41Z"
    - latency: 2.587175ms
      message: 'network-check-target-ip-10-0-138-89: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T12:38:41Z"
    - latency: 3.387465ms
      message: 'network-check-target-ip-10-0-138-89: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T12:37:41Z"
    - latency: 2.492543ms
      message: 'network-check-target-ip-10-0-138-89: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T12:36:41Z"
    - latency: 2.396099ms
      message: 'network-check-target-ip-10-0-138-89: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T12:35:41Z"
    - latency: 2.461016ms
      message: 'network-check-target-ip-10-0-138-89: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T12:34:41Z"
    - latency: 2.66612ms
      message: 'network-check-target-ip-10-0-138-89: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T12:33:41Z"
    - latency: 2.607869ms
      message: 'network-check-target-ip-10-0-138-89: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T12:32:41Z"
    - latency: 2.633936ms
      message: 'network-check-target-ip-10-0-138-89: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T12:31:41Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T12:05:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-160-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-160.ec2.internal
      uid: 312c5c34-15dc-4060-ac9e-db0458f43175
    resourceVersion: "54185"
    uid: fe90b541-27e5-42a4-8507-ef52eb154141
  spec:
    sourcePod: network-check-source-989f8b8dc-m2hgr
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T12:11:41Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 996.575µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T12:41:41Z"
    - latency: 1.695793ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T12:41:41Z"
    - latency: 856.873µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T12:40:41Z"
    - latency: 1.927833ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T12:40:41Z"
    - latency: 877.03µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T12:39:41Z"
    - latency: 1.692271ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T12:39:41Z"
    - latency: 937.154µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T12:38:41Z"
    - latency: 1.848471ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T12:38:41Z"
    - latency: 1.123509ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T12:37:41Z"
    - latency: 1.875717ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T12:37:41Z"
kind: List
metadata:
  resourceVersion: ""