apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-11T17:52:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-204-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-204.ec2.internal
      uid: 3558b13f-bab9-49a8-a4f7-9bed25e5f33d
    resourceVersion: "53338"
    uid: 20bc5b11-57e6-4cf1-848d-b24c268660a3
  spec:
    sourcePod: network-check-source-6947749cfc-pwvhn
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-06-11T17:59: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.250036ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T18:27:21Z"
    - latency: 1.229732ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T18:26:21Z"
    - latency: 1.330438ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T18:25:21Z"
    - latency: 1.514055ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T18:24:21Z"
    - latency: 1.028979ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T18:23:21Z"
    - latency: 1.356892ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T18:22:21Z"
    - latency: 894.504µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T18:21:21Z"
    - latency: 1.068786ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T18:20:21Z"
    - latency: 1.092432ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T18:19:21Z"
    - latency: 1.102301ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T18:18:21Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-11T17:52:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-204-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-204.ec2.internal
      uid: 3558b13f-bab9-49a8-a4f7-9bed25e5f33d
    resourceVersion: "53974"
    uid: 69c445e7-0457-496a-bf91-3189d9ae3448
  spec:
    sourcePod: network-check-source-6947749cfc-pwvhn
    targetEndpoint: ae7252d83e46b4272a9265fda152c608-11e5176f2e319c11.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-11T17:58:21Z"
      message: 'load-balancer-api-external: tcp connection to ae7252d83e46b4272a9265fda152c608-11e5176f2e319c11.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.07025ms
      message: 'load-balancer-api-external: tcp connection to ae7252d83e46b4272a9265fda152c608-11e5176f2e319c11.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T18:28:21Z"
    - latency: 10.186152ms
      message: 'load-balancer-api-external: resolved host name ae7252d83e46b4272a9265fda152c608-11e5176f2e319c11.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T18:28:21Z"
    - latency: 5.014173ms
      message: 'load-balancer-api-external: tcp connection to ae7252d83e46b4272a9265fda152c608-11e5176f2e319c11.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T18:27:21Z"
    - latency: 8.572995ms
      message: 'load-balancer-api-external: resolved host name ae7252d83e46b4272a9265fda152c608-11e5176f2e319c11.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T18:27:21Z"
    - latency: 4.654864ms
      message: 'load-balancer-api-external: tcp connection to ae7252d83e46b4272a9265fda152c608-11e5176f2e319c11.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T18:26:21Z"
    - latency: 9.252166ms
      message: 'load-balancer-api-external: resolved host name ae7252d83e46b4272a9265fda152c608-11e5176f2e319c11.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T18:26:21Z"
    - latency: 3.54744ms
      message: 'load-balancer-api-external: tcp connection to ae7252d83e46b4272a9265fda152c608-11e5176f2e319c11.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T18:25:21Z"
    - latency: 8.280317ms
      message: 'load-balancer-api-external: resolved host name ae7252d83e46b4272a9265fda152c608-11e5176f2e319c11.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T18:25:21Z"
    - latency: 3.929847ms
      message: 'load-balancer-api-external: tcp connection to ae7252d83e46b4272a9265fda152c608-11e5176f2e319c11.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T18:24:21Z"
    - latency: 9.180614ms
      message: 'load-balancer-api-external: resolved host name ae7252d83e46b4272a9265fda152c608-11e5176f2e319c11.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T18:24:21Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-11T17:52:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-204-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-204.ec2.internal
      uid: 3558b13f-bab9-49a8-a4f7-9bed25e5f33d
    resourceVersion: "53975"
    uid: d6ce0762-ac96-4b7c-a7ba-9d64ed928600
  spec:
    sourcePod: network-check-source-6947749cfc-pwvhn
    targetEndpoint: ae7252d83e46b4272a9265fda152c608-11e5176f2e319c11.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-11T17:58:21Z"
      message: 'load-balancer-api-internal: tcp connection to ae7252d83e46b4272a9265fda152c608-11e5176f2e319c11.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.025199ms
      message: 'load-balancer-api-internal: tcp connection to ae7252d83e46b4272a9265fda152c608-11e5176f2e319c11.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T18:28:21Z"
    - latency: 10.31854ms
      message: 'load-balancer-api-internal: resolved host name ae7252d83e46b4272a9265fda152c608-11e5176f2e319c11.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T18:28:21Z"
    - latency: 5.298778ms
      message: 'load-balancer-api-internal: tcp connection to ae7252d83e46b4272a9265fda152c608-11e5176f2e319c11.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T18:27:21Z"
    - latency: 8.663519ms
      message: 'load-balancer-api-internal: resolved host name ae7252d83e46b4272a9265fda152c608-11e5176f2e319c11.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T18:27:21Z"
    - latency: 3.807488ms
      message: 'load-balancer-api-internal: tcp connection to ae7252d83e46b4272a9265fda152c608-11e5176f2e319c11.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T18:26:21Z"
    - latency: 9.163088ms
      message: 'load-balancer-api-internal: resolved host name ae7252d83e46b4272a9265fda152c608-11e5176f2e319c11.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T18:26:21Z"
    - latency: 4.491865ms
      message: 'load-balancer-api-internal: tcp connection to ae7252d83e46b4272a9265fda152c608-11e5176f2e319c11.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T18:25:21Z"
    - latency: 8.328978ms
      message: 'load-balancer-api-internal: resolved host name ae7252d83e46b4272a9265fda152c608-11e5176f2e319c11.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T18:25:21Z"
    - latency: 3.896671ms
      message: 'load-balancer-api-internal: tcp connection to ae7252d83e46b4272a9265fda152c608-11e5176f2e319c11.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T18:24:21Z"
    - latency: 9.257949ms
      message: 'load-balancer-api-internal: resolved host name ae7252d83e46b4272a9265fda152c608-11e5176f2e319c11.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T18:24:21Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-11T17:52:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-204-to-network-check-target-ip-10-0-128-171
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-204.ec2.internal
      uid: 3558b13f-bab9-49a8-a4f7-9bed25e5f33d
    resourceVersion: "53337"
    uid: cdd80b9e-6b4f-43b4-ad7b-2170bbc53376
  spec:
    sourcePod: network-check-source-6947749cfc-pwvhn
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-11T17:59:21Z"
      message: 'network-check-target-ip-10-0-128-171: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.105467ms
      message: 'network-check-target-ip-10-0-128-171: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T18:27:21Z"
    - latency: 2.277543ms
      message: 'network-check-target-ip-10-0-128-171: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T18:26:21Z"
    - latency: 2.198109ms
      message: 'network-check-target-ip-10-0-128-171: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T18:25:21Z"
    - latency: 2.191202ms
      message: 'network-check-target-ip-10-0-128-171: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T18:24:21Z"
    - latency: 2.132735ms
      message: 'network-check-target-ip-10-0-128-171: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T18:23:21Z"
    - latency: 2.392578ms
      message: 'network-check-target-ip-10-0-128-171: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T18:22:21Z"
    - latency: 2.266562ms
      message: 'network-check-target-ip-10-0-128-171: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T18:21:21Z"
    - latency: 2.311663ms
      message: 'network-check-target-ip-10-0-128-171: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T18:20:21Z"
    - latency: 2.271096ms
      message: 'network-check-target-ip-10-0-128-171: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T18:19:21Z"
    - latency: 2.386015ms
      message: 'network-check-target-ip-10-0-128-171: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T18:18:21Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-11T17:52:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-204-to-network-check-target-ip-10-0-133-204
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-204.ec2.internal
      uid: 3558b13f-bab9-49a8-a4f7-9bed25e5f33d
    resourceVersion: "53335"
    uid: 34f82819-7dc8-4743-bc0f-9ba77ae88872
  spec:
    sourcePod: network-check-source-6947749cfc-pwvhn
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-11T17:59:21Z"
      message: 'network-check-target-ip-10-0-133-204: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 857.378µs
      message: 'network-check-target-ip-10-0-133-204: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T18:27:21Z"
    - latency: 836.616µs
      message: 'network-check-target-ip-10-0-133-204: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T18:26:21Z"
    - latency: 976.159µs
      message: 'network-check-target-ip-10-0-133-204: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T18:25:21Z"
    - latency: 1.086445ms
      message: 'network-check-target-ip-10-0-133-204: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T18:24:21Z"
    - latency: 1.568999ms
      message: 'network-check-target-ip-10-0-133-204: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T18:23:21Z"
    - latency: 1.509152ms
      message: 'network-check-target-ip-10-0-133-204: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T18:22:21Z"
    - latency: 879.657µs
      message: 'network-check-target-ip-10-0-133-204: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T18:21:21Z"
    - latency: 1.584201ms
      message: 'network-check-target-ip-10-0-133-204: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T18:20:21Z"
    - latency: 852.563µs
      message: 'network-check-target-ip-10-0-133-204: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T18:19:21Z"
    - latency: 691.138µs
      message: 'network-check-target-ip-10-0-133-204: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T18:18:21Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-11T17:52:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-204-to-network-check-target-ip-10-0-135-235
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-204.ec2.internal
      uid: 3558b13f-bab9-49a8-a4f7-9bed25e5f33d
    resourceVersion: "53336"
    uid: 7c6a8a7f-6555-4141-8f00-bf43b15ead65
  spec:
    sourcePod: network-check-source-6947749cfc-pwvhn
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-11T17:59:21Z"
      message: 'network-check-target-ip-10-0-135-235: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.750003ms
      message: 'network-check-target-ip-10-0-135-235: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T18:27:21Z"
    - latency: 1.686108ms
      message: 'network-check-target-ip-10-0-135-235: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T18:26:21Z"
    - latency: 2.983579ms
      message: 'network-check-target-ip-10-0-135-235: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T18:25:21Z"
    - latency: 1.999843ms
      message: 'network-check-target-ip-10-0-135-235: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T18:24:21Z"
    - latency: 1.541082ms
      message: 'network-check-target-ip-10-0-135-235: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T18:23:21Z"
    - latency: 1.945888ms
      message: 'network-check-target-ip-10-0-135-235: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T18:22:21Z"
    - latency: 1.567373ms
      message: 'network-check-target-ip-10-0-135-235: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T18:21:21Z"
    - latency: 1.877192ms
      message: 'network-check-target-ip-10-0-135-235: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T18:20:21Z"
    - latency: 2.28431ms
      message: 'network-check-target-ip-10-0-135-235: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T18:19:21Z"
    - latency: 2.054034ms
      message: 'network-check-target-ip-10-0-135-235: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T18:18:21Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-11T17:52:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-204-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-204.ec2.internal
      uid: 3558b13f-bab9-49a8-a4f7-9bed25e5f33d
    resourceVersion: "53973"
    uid: 94d8b961-b402-47ab-96b4-5b99e05cf1c8
  spec:
    sourcePod: network-check-source-6947749cfc-pwvhn
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-06-11T17:58:21Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 946.818µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T18:28:21Z"
    - latency: 1.846557ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T18:28:21Z"
    - latency: 849.696µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T18:27:21Z"
    - latency: 1.878693ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T18:27:21Z"
    - latency: 848.364µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T18:26:21Z"
    - latency: 2.031891ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T18:26:21Z"
    - latency: 837.797µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T18:25:21Z"
    - latency: 2.188923ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T18:25:21Z"
    - latency: 789.731µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T18:24:21Z"
    - latency: 2.097611ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T18:24:21Z"
kind: List
metadata:
  resourceVersion: ""