apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T10:35:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-186-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-186.ec2.internal
      uid: d310cc32-98a7-4753-be6c-b5d68b063df2
    resourceVersion: "54703"
    uid: 320a6c6b-d90d-4717-8092-dc1b29940137
  spec:
    sourcePod: network-check-source-869dcfcdcd-mvgn6
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T10:42:26Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.022013ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T11:10:26Z"
    - latency: 899.658µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T11:09:26Z"
    - latency: 982.874µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T11:08:26Z"
    - latency: 1.075145ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T11:07:26Z"
    - latency: 1.026694ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T11:06:26Z"
    - latency: 924.212µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T11:05:26Z"
    - latency: 1.17653ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T11:04:26Z"
    - latency: 1.253843ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T11:03:26Z"
    - latency: 1.198846ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T11:02:26Z"
    - latency: 805.535µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T11:01:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T10:35:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-186-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-186.ec2.internal
      uid: d310cc32-98a7-4753-be6c-b5d68b063df2
    resourceVersion: "55651"
    uid: ee42ab5e-a5f8-43dd-b755-509180067646
  spec:
    sourcePod: network-check-source-869dcfcdcd-mvgn6
    targetEndpoint: a30052d06f6d547f5838f6939dbe06ea-54f5ec9558e36f8d.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T10:41:26Z"
      message: 'load-balancer-api-external: tcp connection to a30052d06f6d547f5838f6939dbe06ea-54f5ec9558e36f8d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.468788ms
      message: 'load-balancer-api-external: tcp connection to a30052d06f6d547f5838f6939dbe06ea-54f5ec9558e36f8d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T11:11:26Z"
    - latency: 7.084598ms
      message: 'load-balancer-api-external: resolved host name a30052d06f6d547f5838f6939dbe06ea-54f5ec9558e36f8d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T11:11:26Z"
    - latency: 4.266647ms
      message: 'load-balancer-api-external: tcp connection to a30052d06f6d547f5838f6939dbe06ea-54f5ec9558e36f8d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T11:10:26Z"
    - latency: 7.533814ms
      message: 'load-balancer-api-external: resolved host name a30052d06f6d547f5838f6939dbe06ea-54f5ec9558e36f8d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T11:10:26Z"
    - latency: 5.001314ms
      message: 'load-balancer-api-external: tcp connection to a30052d06f6d547f5838f6939dbe06ea-54f5ec9558e36f8d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T11:09:26Z"
    - latency: 6.993756ms
      message: 'load-balancer-api-external: resolved host name a30052d06f6d547f5838f6939dbe06ea-54f5ec9558e36f8d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T11:09:26Z"
    - latency: 4.775799ms
      message: 'load-balancer-api-external: tcp connection to a30052d06f6d547f5838f6939dbe06ea-54f5ec9558e36f8d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T11:08:26Z"
    - latency: 6.218523ms
      message: 'load-balancer-api-external: resolved host name a30052d06f6d547f5838f6939dbe06ea-54f5ec9558e36f8d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T11:08:26Z"
    - latency: 4.816337ms
      message: 'load-balancer-api-external: tcp connection to a30052d06f6d547f5838f6939dbe06ea-54f5ec9558e36f8d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T11:07:26Z"
    - latency: 7.005744ms
      message: 'load-balancer-api-external: resolved host name a30052d06f6d547f5838f6939dbe06ea-54f5ec9558e36f8d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T11:07:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T10:35:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-186-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-186.ec2.internal
      uid: d310cc32-98a7-4753-be6c-b5d68b063df2
    resourceVersion: "55650"
    uid: a5d40a4f-3db3-4051-834d-f6e40d9db70c
  spec:
    sourcePod: network-check-source-869dcfcdcd-mvgn6
    targetEndpoint: a30052d06f6d547f5838f6939dbe06ea-54f5ec9558e36f8d.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T10:41:26Z"
      message: 'load-balancer-api-internal: tcp connection to a30052d06f6d547f5838f6939dbe06ea-54f5ec9558e36f8d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.601887ms
      message: 'load-balancer-api-internal: tcp connection to a30052d06f6d547f5838f6939dbe06ea-54f5ec9558e36f8d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T11:11:26Z"
    - latency: 7.050178ms
      message: 'load-balancer-api-internal: resolved host name a30052d06f6d547f5838f6939dbe06ea-54f5ec9558e36f8d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T11:11:26Z"
    - latency: 4.292705ms
      message: 'load-balancer-api-internal: tcp connection to a30052d06f6d547f5838f6939dbe06ea-54f5ec9558e36f8d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T11:10:26Z"
    - latency: 7.419811ms
      message: 'load-balancer-api-internal: resolved host name a30052d06f6d547f5838f6939dbe06ea-54f5ec9558e36f8d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T11:10:26Z"
    - latency: 4.992445ms
      message: 'load-balancer-api-internal: tcp connection to a30052d06f6d547f5838f6939dbe06ea-54f5ec9558e36f8d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T11:09:26Z"
    - latency: 6.949211ms
      message: 'load-balancer-api-internal: resolved host name a30052d06f6d547f5838f6939dbe06ea-54f5ec9558e36f8d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T11:09:26Z"
    - latency: 4.187087ms
      message: 'load-balancer-api-internal: tcp connection to a30052d06f6d547f5838f6939dbe06ea-54f5ec9558e36f8d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T11:08:26Z"
    - latency: 6.257539ms
      message: 'load-balancer-api-internal: resolved host name a30052d06f6d547f5838f6939dbe06ea-54f5ec9558e36f8d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T11:08:26Z"
    - latency: 4.826635ms
      message: 'load-balancer-api-internal: tcp connection to a30052d06f6d547f5838f6939dbe06ea-54f5ec9558e36f8d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T11:07:26Z"
    - latency: 6.964309ms
      message: 'load-balancer-api-internal: resolved host name a30052d06f6d547f5838f6939dbe06ea-54f5ec9558e36f8d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T11:07:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T10:35:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-186-to-network-check-target-ip-10-0-128-213
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-186.ec2.internal
      uid: d310cc32-98a7-4753-be6c-b5d68b063df2
    resourceVersion: "54701"
    uid: 61461e48-62f7-4d3b-be16-66e92b4dc3e7
  spec:
    sourcePod: network-check-source-869dcfcdcd-mvgn6
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T10:42:26Z"
      message: 'network-check-target-ip-10-0-128-213: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.233979ms
      message: 'network-check-target-ip-10-0-128-213: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T11:10:26Z"
    - latency: 2.502653ms
      message: 'network-check-target-ip-10-0-128-213: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T11:09:26Z"
    - latency: 2.220403ms
      message: 'network-check-target-ip-10-0-128-213: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T11:08:26Z"
    - latency: 2.234655ms
      message: 'network-check-target-ip-10-0-128-213: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T11:07:26Z"
    - latency: 2.182294ms
      message: 'network-check-target-ip-10-0-128-213: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T11:06:26Z"
    - latency: 2.159275ms
      message: 'network-check-target-ip-10-0-128-213: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T11:05:26Z"
    - latency: 2.021481ms
      message: 'network-check-target-ip-10-0-128-213: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T11:04:26Z"
    - latency: 2.023838ms
      message: 'network-check-target-ip-10-0-128-213: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T11:03:26Z"
    - latency: 2.231821ms
      message: 'network-check-target-ip-10-0-128-213: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T11:02:26Z"
    - latency: 1.912066ms
      message: 'network-check-target-ip-10-0-128-213: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T11:01:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T10:35:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-186-to-network-check-target-ip-10-0-138-186
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-186.ec2.internal
      uid: d310cc32-98a7-4753-be6c-b5d68b063df2
    resourceVersion: "54702"
    uid: 8993dab7-7d9c-42b6-b839-5a1dcde8549a
  spec:
    sourcePod: network-check-source-869dcfcdcd-mvgn6
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T10:42:26Z"
      message: 'network-check-target-ip-10-0-138-186: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 884.967µs
      message: 'network-check-target-ip-10-0-138-186: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T11:10:26Z"
    - latency: 821.013µs
      message: 'network-check-target-ip-10-0-138-186: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T11:09:26Z"
    - latency: 838.475µs
      message: 'network-check-target-ip-10-0-138-186: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T11:08:26Z"
    - latency: 819.052µs
      message: 'network-check-target-ip-10-0-138-186: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T11:07:26Z"
    - latency: 1.31895ms
      message: 'network-check-target-ip-10-0-138-186: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T11:06:26Z"
    - latency: 934.806µs
      message: 'network-check-target-ip-10-0-138-186: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T11:05:26Z"
    - latency: 762.627µs
      message: 'network-check-target-ip-10-0-138-186: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T11:04:26Z"
    - latency: 887.671µs
      message: 'network-check-target-ip-10-0-138-186: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T11:03:26Z"
    - latency: 1.153816ms
      message: 'network-check-target-ip-10-0-138-186: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T11:02:26Z"
    - latency: 1.280213ms
      message: 'network-check-target-ip-10-0-138-186: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T11:01:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T10:35:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-186-to-network-check-target-ip-10-0-142-37
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-186.ec2.internal
      uid: d310cc32-98a7-4753-be6c-b5d68b063df2
    resourceVersion: "54705"
    uid: d30c1b33-c09d-41b6-b6cd-e36f322d3670
  spec:
    sourcePod: network-check-source-869dcfcdcd-mvgn6
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T10:42:26Z"
      message: 'network-check-target-ip-10-0-142-37: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.455865ms
      message: 'network-check-target-ip-10-0-142-37: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T11:10:26Z"
    - latency: 2.547541ms
      message: 'network-check-target-ip-10-0-142-37: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T11:09:26Z"
    - latency: 2.235846ms
      message: 'network-check-target-ip-10-0-142-37: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T11:08:26Z"
    - latency: 2.333188ms
      message: 'network-check-target-ip-10-0-142-37: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T11:07:26Z"
    - latency: 2.469155ms
      message: 'network-check-target-ip-10-0-142-37: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T11:06:26Z"
    - latency: 2.473231ms
      message: 'network-check-target-ip-10-0-142-37: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T11:05:26Z"
    - latency: 2.203508ms
      message: 'network-check-target-ip-10-0-142-37: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T11:04:26Z"
    - latency: 2.491613ms
      message: 'network-check-target-ip-10-0-142-37: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T11:03:26Z"
    - latency: 2.3433ms
      message: 'network-check-target-ip-10-0-142-37: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T11:02:26Z"
    - latency: 2.541121ms
      message: 'network-check-target-ip-10-0-142-37: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T11:01:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T10:35:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-186-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-186.ec2.internal
      uid: d310cc32-98a7-4753-be6c-b5d68b063df2
    resourceVersion: "55649"
    uid: 8e268916-31c8-408a-bf75-fa6ea999ff64
  spec:
    sourcePod: network-check-source-869dcfcdcd-mvgn6
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T10:41:26Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 818.834µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T11:11:26Z"
    - latency: 1.594145ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T11:11:26Z"
    - latency: 851.697µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T11:10:26Z"
    - latency: 1.644107ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T11:10:26Z"
    - latency: 911.936µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T11:09:26Z"
    - latency: 1.549109ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T11:09:26Z"
    - latency: 871.57µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T11:08:26Z"
    - latency: 1.47976ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T11:08:26Z"
    - latency: 1.334818ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T11:07:26Z"
    - latency: 1.647644ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T11:07:26Z"
kind: List
metadata:
  resourceVersion: ""