apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-03T20:50:12Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-196-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-196.ec2.internal
      uid: 7fc19583-3167-44ae-928d-3db939f37f85
    resourceVersion: "47647"
    uid: f21b8146-d358-4721-bb7e-a3702e8d2c60
  spec:
    sourcePod: network-check-source-dbd9cf844-d56v4
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-06-03T20:57:13Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.080056ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T21:18:13Z"
    - latency: 964.388µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T21:17:13Z"
    - latency: 993.553µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T21:16:13Z"
    - latency: 955.26µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T21:15:13Z"
    - latency: 1.568611ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T21:14:13Z"
    - latency: 1.523207ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T21:13:13Z"
    - latency: 984.337µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T21:12:13Z"
    - latency: 1.689967ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T21:11:13Z"
    - latency: 858.12µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T21:10:13Z"
    - latency: 1.186998ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T21:09:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-03T20:50:12Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-196-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-196.ec2.internal
      uid: 7fc19583-3167-44ae-928d-3db939f37f85
    resourceVersion: "49948"
    uid: 3fbef277-8ffc-404d-a483-38b86126a404
  spec:
    sourcePod: network-check-source-dbd9cf844-d56v4
    targetEndpoint: a8a072d04bb8b434792c908c810d5a94-eee452b674aa0227.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-03T20:56:13Z"
      message: 'load-balancer-api-external: tcp connection to a8a072d04bb8b434792c908c810d5a94-eee452b674aa0227.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.579948ms
      message: 'load-balancer-api-external: tcp connection to a8a072d04bb8b434792c908c810d5a94-eee452b674aa0227.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T21:20:13Z"
    - latency: 8.689752ms
      message: 'load-balancer-api-external: resolved host name a8a072d04bb8b434792c908c810d5a94-eee452b674aa0227.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T21:20:13Z"
    - latency: 3.875829ms
      message: 'load-balancer-api-external: tcp connection to a8a072d04bb8b434792c908c810d5a94-eee452b674aa0227.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T21:19:13Z"
    - latency: 8.00838ms
      message: 'load-balancer-api-external: resolved host name a8a072d04bb8b434792c908c810d5a94-eee452b674aa0227.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T21:19:13Z"
    - latency: 3.895511ms
      message: 'load-balancer-api-external: tcp connection to a8a072d04bb8b434792c908c810d5a94-eee452b674aa0227.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T21:18:13Z"
    - latency: 8.460632ms
      message: 'load-balancer-api-external: resolved host name a8a072d04bb8b434792c908c810d5a94-eee452b674aa0227.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T21:18:13Z"
    - latency: 5.523341ms
      message: 'load-balancer-api-external: tcp connection to a8a072d04bb8b434792c908c810d5a94-eee452b674aa0227.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T21:17:13Z"
    - latency: 10.6898ms
      message: 'load-balancer-api-external: resolved host name a8a072d04bb8b434792c908c810d5a94-eee452b674aa0227.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T21:17:13Z"
    - latency: 3.917424ms
      message: 'load-balancer-api-external: tcp connection to a8a072d04bb8b434792c908c810d5a94-eee452b674aa0227.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T21:16:13Z"
    - latency: 8.410526ms
      message: 'load-balancer-api-external: resolved host name a8a072d04bb8b434792c908c810d5a94-eee452b674aa0227.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T21:16:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-03T20:50:12Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-196-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-196.ec2.internal
      uid: 7fc19583-3167-44ae-928d-3db939f37f85
    resourceVersion: "49949"
    uid: 73b47762-eded-4016-8f8f-ba35983bfe58
  spec:
    sourcePod: network-check-source-dbd9cf844-d56v4
    targetEndpoint: a8a072d04bb8b434792c908c810d5a94-eee452b674aa0227.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-03T20:56:13Z"
      message: 'load-balancer-api-internal: tcp connection to a8a072d04bb8b434792c908c810d5a94-eee452b674aa0227.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.368381ms
      message: 'load-balancer-api-internal: tcp connection to a8a072d04bb8b434792c908c810d5a94-eee452b674aa0227.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T21:20:13Z"
    - latency: 8.657571ms
      message: 'load-balancer-api-internal: resolved host name a8a072d04bb8b434792c908c810d5a94-eee452b674aa0227.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T21:20:13Z"
    - latency: 3.924661ms
      message: 'load-balancer-api-internal: tcp connection to a8a072d04bb8b434792c908c810d5a94-eee452b674aa0227.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T21:19:13Z"
    - latency: 7.968529ms
      message: 'load-balancer-api-internal: resolved host name a8a072d04bb8b434792c908c810d5a94-eee452b674aa0227.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T21:19:13Z"
    - latency: 4.668168ms
      message: 'load-balancer-api-internal: tcp connection to a8a072d04bb8b434792c908c810d5a94-eee452b674aa0227.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T21:18:13Z"
    - latency: 8.426917ms
      message: 'load-balancer-api-internal: resolved host name a8a072d04bb8b434792c908c810d5a94-eee452b674aa0227.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T21:18:13Z"
    - latency: 5.561553ms
      message: 'load-balancer-api-internal: tcp connection to a8a072d04bb8b434792c908c810d5a94-eee452b674aa0227.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T21:17:13Z"
    - latency: 10.55003ms
      message: 'load-balancer-api-internal: resolved host name a8a072d04bb8b434792c908c810d5a94-eee452b674aa0227.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T21:17:13Z"
    - latency: 4.402074ms
      message: 'load-balancer-api-internal: tcp connection to a8a072d04bb8b434792c908c810d5a94-eee452b674aa0227.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T21:16:13Z"
    - latency: 8.422994ms
      message: 'load-balancer-api-internal: resolved host name a8a072d04bb8b434792c908c810d5a94-eee452b674aa0227.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T21:16:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-03T20:50:12Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-196-to-network-check-target-ip-10-0-128-149
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-196.ec2.internal
      uid: 7fc19583-3167-44ae-928d-3db939f37f85
    resourceVersion: "47645"
    uid: e0cf1888-3f06-48b2-85e9-d263b3f61c21
  spec:
    sourcePod: network-check-source-dbd9cf844-d56v4
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-03T20:57:13Z"
      message: 'network-check-target-ip-10-0-128-149: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.316411ms
      message: 'network-check-target-ip-10-0-128-149: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T21:18:13Z"
    - latency: 2.855718ms
      message: 'network-check-target-ip-10-0-128-149: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T21:17:13Z"
    - latency: 2.266263ms
      message: 'network-check-target-ip-10-0-128-149: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T21:16:13Z"
    - latency: 2.298329ms
      message: 'network-check-target-ip-10-0-128-149: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T21:15:13Z"
    - latency: 2.266552ms
      message: 'network-check-target-ip-10-0-128-149: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T21:14:13Z"
    - latency: 2.244608ms
      message: 'network-check-target-ip-10-0-128-149: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T21:13:13Z"
    - latency: 2.580177ms
      message: 'network-check-target-ip-10-0-128-149: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T21:12:13Z"
    - latency: 2.106039ms
      message: 'network-check-target-ip-10-0-128-149: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T21:11:13Z"
    - latency: 2.038175ms
      message: 'network-check-target-ip-10-0-128-149: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T21:10:13Z"
    - latency: 2.319927ms
      message: 'network-check-target-ip-10-0-128-149: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T21:09:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-03T20:50:12Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-196-to-network-check-target-ip-10-0-128-196
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-196.ec2.internal
      uid: 7fc19583-3167-44ae-928d-3db939f37f85
    resourceVersion: "47644"
    uid: 6f00cc3a-b44c-402b-b032-3d3c72857916
  spec:
    sourcePod: network-check-source-dbd9cf844-d56v4
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-03T20:57:13Z"
      message: 'network-check-target-ip-10-0-128-196: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 886.749µs
      message: 'network-check-target-ip-10-0-128-196: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T21:18:13Z"
    - latency: 1.237696ms
      message: 'network-check-target-ip-10-0-128-196: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T21:17:13Z"
    - latency: 959.211µs
      message: 'network-check-target-ip-10-0-128-196: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T21:16:13Z"
    - latency: 940.592µs
      message: 'network-check-target-ip-10-0-128-196: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T21:15:13Z"
    - latency: 1.604411ms
      message: 'network-check-target-ip-10-0-128-196: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T21:14:13Z"
    - latency: 866.606µs
      message: 'network-check-target-ip-10-0-128-196: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T21:13:13Z"
    - latency: 1.169498ms
      message: 'network-check-target-ip-10-0-128-196: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T21:12:13Z"
    - latency: 837.53µs
      message: 'network-check-target-ip-10-0-128-196: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T21:11:13Z"
    - latency: 823.069µs
      message: 'network-check-target-ip-10-0-128-196: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T21:10:13Z"
    - latency: 1.459777ms
      message: 'network-check-target-ip-10-0-128-196: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T21:09:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-03T20:50:12Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-196-to-network-check-target-ip-10-0-134-233
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-196.ec2.internal
      uid: 7fc19583-3167-44ae-928d-3db939f37f85
    resourceVersion: "47646"
    uid: e1b58f37-4d2a-48ac-ab85-f603d1a7b1ac
  spec:
    sourcePod: network-check-source-dbd9cf844-d56v4
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-03T20:57:13Z"
      message: 'network-check-target-ip-10-0-134-233: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.441228ms
      message: 'network-check-target-ip-10-0-134-233: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T21:18:13Z"
    - latency: 2.495845ms
      message: 'network-check-target-ip-10-0-134-233: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T21:17:13Z"
    - latency: 2.208085ms
      message: 'network-check-target-ip-10-0-134-233: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T21:16:13Z"
    - latency: 2.33876ms
      message: 'network-check-target-ip-10-0-134-233: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T21:15:13Z"
    - latency: 2.779416ms
      message: 'network-check-target-ip-10-0-134-233: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T21:14:13Z"
    - latency: 1.91865ms
      message: 'network-check-target-ip-10-0-134-233: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T21:13:13Z"
    - latency: 2.129377ms
      message: 'network-check-target-ip-10-0-134-233: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T21:12:13Z"
    - latency: 2.04481ms
      message: 'network-check-target-ip-10-0-134-233: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T21:11:13Z"
    - latency: 2.272966ms
      message: 'network-check-target-ip-10-0-134-233: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T21:10:13Z"
    - latency: 2.381015ms
      message: 'network-check-target-ip-10-0-134-233: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T21:09:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-03T20:50:12Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-196-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-196.ec2.internal
      uid: 7fc19583-3167-44ae-928d-3db939f37f85
    resourceVersion: "49947"
    uid: 1296b326-bcfc-467d-a759-73a951555600
  spec:
    sourcePod: network-check-source-dbd9cf844-d56v4
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-06-03T20:56:13Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 906.315µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T21:20:13Z"
    - latency: 1.959594ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T21:20:13Z"
    - latency: 839.5µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T21:19:13Z"
    - latency: 1.67601ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T21:19:13Z"
    - latency: 818.56µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T21:18:13Z"
    - latency: 1.795758ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T21:18:13Z"
    - latency: 1.262489ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T21:17:13Z"
    - latency: 2.135941ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T21:17:13Z"
    - latency: 809.782µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T21:16:13Z"
    - latency: 1.811809ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T21:16:13Z"
kind: List
metadata:
  resourceVersion: ""