apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T13:06:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-77-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-77.us-east-2.compute.internal
      uid: 459aec61-508c-4469-8bb1-6c084a6d032e
    resourceVersion: "180506"
    uid: 7921a511-75d8-49f4-97b5-a8af84136ef4
  spec:
    sourcePod: network-check-source-6f78d59f99-lcmgp
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T13:13:38Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.063433ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T14:16:38Z"
    - latency: 935.945µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T14:15:38Z"
    - latency: 957.124µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T14:14:38Z"
    - latency: 937.585µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T14:13:38Z"
    - latency: 842.313µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T14:12:38Z"
    - latency: 1.056144ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T14:11:38Z"
    - latency: 1.698399ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T14:10:38Z"
    - latency: 1.048484ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T14:09:38Z"
    - latency: 1.030445ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T14:08:38Z"
    - latency: 890.314µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T14:07:38Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T13:06:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-77-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-77.us-east-2.compute.internal
      uid: 459aec61-508c-4469-8bb1-6c084a6d032e
    resourceVersion: "184599"
    uid: f7504cf2-22be-49ac-ad5a-f61bbf309779
  spec:
    sourcePod: network-check-source-6f78d59f99-lcmgp
    targetEndpoint: aba03bd5768ec4010a48a86cc88829a5-69ae702012462fcf.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T13:12:38Z"
      message: 'load-balancer-api-external: tcp connection to aba03bd5768ec4010a48a86cc88829a5-69ae702012462fcf.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.682094ms
      message: 'load-balancer-api-external: tcp connection to aba03bd5768ec4010a48a86cc88829a5-69ae702012462fcf.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T14:18:38Z"
    - latency: 7.126518ms
      message: 'load-balancer-api-external: resolved host name aba03bd5768ec4010a48a86cc88829a5-69ae702012462fcf.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T14:18:38Z"
    - latency: 5.53027ms
      message: 'load-balancer-api-external: tcp connection to aba03bd5768ec4010a48a86cc88829a5-69ae702012462fcf.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T14:17:38Z"
    - latency: 7.27675ms
      message: 'load-balancer-api-external: resolved host name aba03bd5768ec4010a48a86cc88829a5-69ae702012462fcf.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T14:17:38Z"
    - latency: 4.985698ms
      message: 'load-balancer-api-external: tcp connection to aba03bd5768ec4010a48a86cc88829a5-69ae702012462fcf.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T14:16:38Z"
    - latency: 7.284092ms
      message: 'load-balancer-api-external: resolved host name aba03bd5768ec4010a48a86cc88829a5-69ae702012462fcf.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T14:16:38Z"
    - latency: 5.119738ms
      message: 'load-balancer-api-external: tcp connection to aba03bd5768ec4010a48a86cc88829a5-69ae702012462fcf.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T14:15:38Z"
    - latency: 7.162979ms
      message: 'load-balancer-api-external: resolved host name aba03bd5768ec4010a48a86cc88829a5-69ae702012462fcf.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T14:15:38Z"
    - latency: 10.205554ms
      message: 'load-balancer-api-external: tcp connection to aba03bd5768ec4010a48a86cc88829a5-69ae702012462fcf.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T14:14:38Z"
    - latency: 8.229242ms
      message: 'load-balancer-api-external: resolved host name aba03bd5768ec4010a48a86cc88829a5-69ae702012462fcf.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T14:14:38Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T13:06:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-77-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-77.us-east-2.compute.internal
      uid: 459aec61-508c-4469-8bb1-6c084a6d032e
    resourceVersion: "184598"
    uid: e6dea563-2db1-4c83-984b-394508b51beb
  spec:
    sourcePod: network-check-source-6f78d59f99-lcmgp
    targetEndpoint: aba03bd5768ec4010a48a86cc88829a5-69ae702012462fcf.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T13:12:38Z"
      message: 'load-balancer-api-internal: tcp connection to aba03bd5768ec4010a48a86cc88829a5-69ae702012462fcf.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.658433ms
      message: 'load-balancer-api-internal: tcp connection to aba03bd5768ec4010a48a86cc88829a5-69ae702012462fcf.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T14:18:38Z"
    - latency: 7.074563ms
      message: 'load-balancer-api-internal: resolved host name aba03bd5768ec4010a48a86cc88829a5-69ae702012462fcf.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T14:18:38Z"
    - latency: 5.567813ms
      message: 'load-balancer-api-internal: tcp connection to aba03bd5768ec4010a48a86cc88829a5-69ae702012462fcf.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T14:17:38Z"
    - latency: 7.18969ms
      message: 'load-balancer-api-internal: resolved host name aba03bd5768ec4010a48a86cc88829a5-69ae702012462fcf.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T14:17:38Z"
    - latency: 5.395116ms
      message: 'load-balancer-api-internal: tcp connection to aba03bd5768ec4010a48a86cc88829a5-69ae702012462fcf.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T14:16:38Z"
    - latency: 7.208969ms
      message: 'load-balancer-api-internal: resolved host name aba03bd5768ec4010a48a86cc88829a5-69ae702012462fcf.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T14:16:38Z"
    - latency: 5.125209ms
      message: 'load-balancer-api-internal: tcp connection to aba03bd5768ec4010a48a86cc88829a5-69ae702012462fcf.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T14:15:38Z"
    - latency: 7.14508ms
      message: 'load-balancer-api-internal: resolved host name aba03bd5768ec4010a48a86cc88829a5-69ae702012462fcf.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T14:15:38Z"
    - latency: 8.579458ms
      message: 'load-balancer-api-internal: tcp connection to aba03bd5768ec4010a48a86cc88829a5-69ae702012462fcf.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T14:14:38Z"
    - latency: 8.197057ms
      message: 'load-balancer-api-internal: resolved host name aba03bd5768ec4010a48a86cc88829a5-69ae702012462fcf.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T14:14:38Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T13:06:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-77-to-network-check-target-ip-10-0-128-41
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-77.us-east-2.compute.internal
      uid: 459aec61-508c-4469-8bb1-6c084a6d032e
    resourceVersion: "180504"
    uid: 3f4d4979-794a-4ee2-a222-3c3e3d914803
  spec:
    sourcePod: network-check-source-6f78d59f99-lcmgp
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T13:13:38Z"
      message: 'network-check-target-ip-10-0-128-41: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.986506ms
      message: 'network-check-target-ip-10-0-128-41: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T14:16:38Z"
    - latency: 1.897367ms
      message: 'network-check-target-ip-10-0-128-41: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T14:15:38Z"
    - latency: 2.024409ms
      message: 'network-check-target-ip-10-0-128-41: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T14:14:38Z"
    - latency: 1.555325ms
      message: 'network-check-target-ip-10-0-128-41: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T14:13:38Z"
    - latency: 1.929517ms
      message: 'network-check-target-ip-10-0-128-41: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T14:12:38Z"
    - latency: 1.783068ms
      message: 'network-check-target-ip-10-0-128-41: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T14:11:38Z"
    - latency: 2.420483ms
      message: 'network-check-target-ip-10-0-128-41: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T14:10:38Z"
    - latency: 2.595727ms
      message: 'network-check-target-ip-10-0-128-41: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T14:09:38Z"
    - latency: 1.702938ms
      message: 'network-check-target-ip-10-0-128-41: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T14:08:38Z"
    - latency: 1.688008ms
      message: 'network-check-target-ip-10-0-128-41: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T14:07:38Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T13:06:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-77-to-network-check-target-ip-10-0-136-168
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-77.us-east-2.compute.internal
      uid: 459aec61-508c-4469-8bb1-6c084a6d032e
    resourceVersion: "180505"
    uid: 47e7b6dc-d4b4-453b-93ba-3b9177cd6d33
  spec:
    sourcePod: network-check-source-6f78d59f99-lcmgp
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T13:13:38Z"
      message: 'network-check-target-ip-10-0-136-168: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.103394ms
      message: 'network-check-target-ip-10-0-136-168: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T14:16:38Z"
    - latency: 2.013441ms
      message: 'network-check-target-ip-10-0-136-168: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T14:15:38Z"
    - latency: 2.297481ms
      message: 'network-check-target-ip-10-0-136-168: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T14:14:38Z"
    - latency: 1.991119ms
      message: 'network-check-target-ip-10-0-136-168: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T14:13:38Z"
    - latency: 2.379414ms
      message: 'network-check-target-ip-10-0-136-168: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T14:12:38Z"
    - latency: 2.172116ms
      message: 'network-check-target-ip-10-0-136-168: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T14:11:38Z"
    - latency: 2.431735ms
      message: 'network-check-target-ip-10-0-136-168: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T14:10:38Z"
    - latency: 3.651948ms
      message: 'network-check-target-ip-10-0-136-168: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T14:09:38Z"
    - latency: 2.188857ms
      message: 'network-check-target-ip-10-0-136-168: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T14:08:38Z"
    - latency: 2.137408ms
      message: 'network-check-target-ip-10-0-136-168: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T14:07:38Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T13:06:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-77-to-network-check-target-ip-10-0-137-77
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-77.us-east-2.compute.internal
      uid: 459aec61-508c-4469-8bb1-6c084a6d032e
    resourceVersion: "180503"
    uid: 6134b929-0d49-4e08-9979-d7243a7bd174
  spec:
    sourcePod: network-check-source-6f78d59f99-lcmgp
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T13:13:38Z"
      message: 'network-check-target-ip-10-0-137-77: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.018206ms
      message: 'network-check-target-ip-10-0-137-77: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T14:16:38Z"
    - latency: 886.985µs
      message: 'network-check-target-ip-10-0-137-77: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T14:15:38Z"
    - latency: 988.053µs
      message: 'network-check-target-ip-10-0-137-77: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T14:14:38Z"
    - latency: 796.931µs
      message: 'network-check-target-ip-10-0-137-77: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T14:13:38Z"
    - latency: 1.628921ms
      message: 'network-check-target-ip-10-0-137-77: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T14:12:38Z"
    - latency: 921.121µs
      message: 'network-check-target-ip-10-0-137-77: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T14:11:38Z"
    - latency: 1.099893ms
      message: 'network-check-target-ip-10-0-137-77: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T14:10:38Z"
    - latency: 3.012424ms
      message: 'network-check-target-ip-10-0-137-77: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T14:09:38Z"
    - latency: 862.783µs
      message: 'network-check-target-ip-10-0-137-77: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T14:08:38Z"
    - latency: 1.010913ms
      message: 'network-check-target-ip-10-0-137-77: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T14:07:38Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T13:06:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-77-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-77.us-east-2.compute.internal
      uid: 459aec61-508c-4469-8bb1-6c084a6d032e
    resourceVersion: "184596"
    uid: 006ad5b0-9a50-4f6d-9050-17af480cf756
  spec:
    sourcePod: network-check-source-6f78d59f99-lcmgp
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T13:12:38Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 929.055µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T14:18:38Z"
    - latency: 2.065829ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T14:18:38Z"
    - latency: 1.013956ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T14:17:38Z"
    - latency: 1.810966ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T14:17:38Z"
    - latency: 886.594µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T14:16:38Z"
    - latency: 1.98676ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T14:16:38Z"
    - latency: 820.833µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T14:15:38Z"
    - latency: 2.446737ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T14:15:38Z"
    - latency: 987.874µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T14:14:38Z"
    - latency: 2.211746ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T14:14:38Z"
kind: List
metadata:
  resourceVersion: ""