apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T15:00:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-241-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-241.ec2.internal
      uid: 8af52e28-2ddc-4101-a099-ea431c4517e0
    resourceVersion: "55428"
    uid: fa5cd0c2-721f-4bdd-80e8-138144925edf
  spec:
    sourcePod: network-check-source-869dcfcdcd-jtjs8
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T15:07:39Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.106449ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T15:35:39Z"
    - latency: 983.195µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T15:34:39Z"
    - latency: 1.12013ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T15:33:39Z"
    - latency: 1.144242ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T15:32:39Z"
    - latency: 1.291504ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T15:31:39Z"
    - latency: 1.168655ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T15:30:39Z"
    - latency: 1.299286ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T15:29:39Z"
    - latency: 914.719µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T15:28:39Z"
    - latency: 1.001261ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T15:27:39Z"
    - latency: 994.838µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T15:26:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T15:00:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-241-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-241.ec2.internal
      uid: 8af52e28-2ddc-4101-a099-ea431c4517e0
    resourceVersion: "56501"
    uid: 6073793f-2c52-4e83-ab46-a65b3ac1a024
  spec:
    sourcePod: network-check-source-869dcfcdcd-jtjs8
    targetEndpoint: ab502220c9c0e459989e9bfd2c3be551-621cc0f8499fa912.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T15:06:39Z"
      message: 'load-balancer-api-external: tcp connection to ab502220c9c0e459989e9bfd2c3be551-621cc0f8499fa912.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.607965ms
      message: 'load-balancer-api-external: tcp connection to ab502220c9c0e459989e9bfd2c3be551-621cc0f8499fa912.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T15:36:39Z"
    - latency: 9.420077ms
      message: 'load-balancer-api-external: resolved host name ab502220c9c0e459989e9bfd2c3be551-621cc0f8499fa912.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T15:36:39Z"
    - latency: 5.009035ms
      message: 'load-balancer-api-external: tcp connection to ab502220c9c0e459989e9bfd2c3be551-621cc0f8499fa912.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T15:35:39Z"
    - latency: 11.288321ms
      message: 'load-balancer-api-external: resolved host name ab502220c9c0e459989e9bfd2c3be551-621cc0f8499fa912.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T15:35:39Z"
    - latency: 4.9121ms
      message: 'load-balancer-api-external: tcp connection to ab502220c9c0e459989e9bfd2c3be551-621cc0f8499fa912.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T15:34:39Z"
    - latency: 6.041964ms
      message: 'load-balancer-api-external: resolved host name ab502220c9c0e459989e9bfd2c3be551-621cc0f8499fa912.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T15:34:39Z"
    - latency: 4.000125ms
      message: 'load-balancer-api-external: tcp connection to ab502220c9c0e459989e9bfd2c3be551-621cc0f8499fa912.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T15:33:39Z"
    - latency: 11.338097ms
      message: 'load-balancer-api-external: resolved host name ab502220c9c0e459989e9bfd2c3be551-621cc0f8499fa912.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T15:33:39Z"
    - latency: 3.879542ms
      message: 'load-balancer-api-external: tcp connection to ab502220c9c0e459989e9bfd2c3be551-621cc0f8499fa912.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T15:32:39Z"
    - latency: 9.554708ms
      message: 'load-balancer-api-external: resolved host name ab502220c9c0e459989e9bfd2c3be551-621cc0f8499fa912.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T15:32:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T15:00:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-241-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-241.ec2.internal
      uid: 8af52e28-2ddc-4101-a099-ea431c4517e0
    resourceVersion: "56500"
    uid: eb48bab0-86cd-4175-a9d6-b04c4f5f9b2a
  spec:
    sourcePod: network-check-source-869dcfcdcd-jtjs8
    targetEndpoint: ab502220c9c0e459989e9bfd2c3be551-621cc0f8499fa912.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T15:06:39Z"
      message: 'load-balancer-api-internal: tcp connection to ab502220c9c0e459989e9bfd2c3be551-621cc0f8499fa912.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.661952ms
      message: 'load-balancer-api-internal: tcp connection to ab502220c9c0e459989e9bfd2c3be551-621cc0f8499fa912.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T15:36:39Z"
    - latency: 9.343139ms
      message: 'load-balancer-api-internal: resolved host name ab502220c9c0e459989e9bfd2c3be551-621cc0f8499fa912.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T15:36:39Z"
    - latency: 4.945951ms
      message: 'load-balancer-api-internal: tcp connection to ab502220c9c0e459989e9bfd2c3be551-621cc0f8499fa912.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T15:35:39Z"
    - latency: 11.320564ms
      message: 'load-balancer-api-internal: resolved host name ab502220c9c0e459989e9bfd2c3be551-621cc0f8499fa912.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T15:35:39Z"
    - latency: 4.887345ms
      message: 'load-balancer-api-internal: tcp connection to ab502220c9c0e459989e9bfd2c3be551-621cc0f8499fa912.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T15:34:39Z"
    - latency: 6.128832ms
      message: 'load-balancer-api-internal: resolved host name ab502220c9c0e459989e9bfd2c3be551-621cc0f8499fa912.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T15:34:39Z"
    - latency: 4.027832ms
      message: 'load-balancer-api-internal: tcp connection to ab502220c9c0e459989e9bfd2c3be551-621cc0f8499fa912.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T15:33:39Z"
    - latency: 11.273859ms
      message: 'load-balancer-api-internal: resolved host name ab502220c9c0e459989e9bfd2c3be551-621cc0f8499fa912.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T15:33:39Z"
    - latency: 4.578149ms
      message: 'load-balancer-api-internal: tcp connection to ab502220c9c0e459989e9bfd2c3be551-621cc0f8499fa912.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T15:32:39Z"
    - latency: 9.429478ms
      message: 'load-balancer-api-internal: resolved host name ab502220c9c0e459989e9bfd2c3be551-621cc0f8499fa912.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T15:32:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T15:00:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-241-to-network-check-target-ip-10-0-133-241
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-241.ec2.internal
      uid: 8af52e28-2ddc-4101-a099-ea431c4517e0
    resourceVersion: "55425"
    uid: b9cbe55a-285f-4762-a16d-faf4898bd889
  spec:
    sourcePod: network-check-source-869dcfcdcd-jtjs8
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T15:07:39Z"
      message: 'network-check-target-ip-10-0-133-241: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.019584ms
      message: 'network-check-target-ip-10-0-133-241: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T15:35:39Z"
    - latency: 1.293808ms
      message: 'network-check-target-ip-10-0-133-241: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T15:34:39Z"
    - latency: 1.410877ms
      message: 'network-check-target-ip-10-0-133-241: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T15:33:39Z"
    - latency: 1.111931ms
      message: 'network-check-target-ip-10-0-133-241: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T15:32:39Z"
    - latency: 865.842µs
      message: 'network-check-target-ip-10-0-133-241: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T15:31:39Z"
    - latency: 1.053605ms
      message: 'network-check-target-ip-10-0-133-241: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T15:30:39Z"
    - latency: 1.059753ms
      message: 'network-check-target-ip-10-0-133-241: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T15:29:39Z"
    - latency: 945.018µs
      message: 'network-check-target-ip-10-0-133-241: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T15:28:39Z"
    - latency: 946.919µs
      message: 'network-check-target-ip-10-0-133-241: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T15:27:39Z"
    - latency: 1.11565ms
      message: 'network-check-target-ip-10-0-133-241: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T15:26:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T15:00:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-241-to-network-check-target-ip-10-0-133-59
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-241.ec2.internal
      uid: 8af52e28-2ddc-4101-a099-ea431c4517e0
    resourceVersion: "55426"
    uid: 13f05376-17c5-45c9-b454-e96d8bd4dbfa
  spec:
    sourcePod: network-check-source-869dcfcdcd-jtjs8
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T15:07:39Z"
      message: 'network-check-target-ip-10-0-133-59: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.037268ms
      message: 'network-check-target-ip-10-0-133-59: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T15:35:39Z"
    - latency: 2.477007ms
      message: 'network-check-target-ip-10-0-133-59: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T15:34:39Z"
    - latency: 2.2113ms
      message: 'network-check-target-ip-10-0-133-59: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T15:33:39Z"
    - latency: 2.587492ms
      message: 'network-check-target-ip-10-0-133-59: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T15:32:39Z"
    - latency: 2.201586ms
      message: 'network-check-target-ip-10-0-133-59: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T15:31:39Z"
    - latency: 2.303722ms
      message: 'network-check-target-ip-10-0-133-59: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T15:30:39Z"
    - latency: 2.097327ms
      message: 'network-check-target-ip-10-0-133-59: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T15:29:39Z"
    - latency: 2.026071ms
      message: 'network-check-target-ip-10-0-133-59: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T15:28:39Z"
    - latency: 2.216515ms
      message: 'network-check-target-ip-10-0-133-59: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T15:27:39Z"
    - latency: 2.04968ms
      message: 'network-check-target-ip-10-0-133-59: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T15:26:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T15:00:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-241-to-network-check-target-ip-10-0-137-94
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-241.ec2.internal
      uid: 8af52e28-2ddc-4101-a099-ea431c4517e0
    resourceVersion: "55427"
    uid: eb1e84fa-b249-4e15-b4d6-67288fa10b52
  spec:
    sourcePod: network-check-source-869dcfcdcd-jtjs8
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T15:07:39Z"
      message: 'network-check-target-ip-10-0-137-94: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.053511ms
      message: 'network-check-target-ip-10-0-137-94: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T15:35:39Z"
    - latency: 2.503037ms
      message: 'network-check-target-ip-10-0-137-94: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T15:34:39Z"
    - latency: 2.275173ms
      message: 'network-check-target-ip-10-0-137-94: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T15:33:39Z"
    - latency: 2.303871ms
      message: 'network-check-target-ip-10-0-137-94: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T15:32:39Z"
    - latency: 2.580545ms
      message: 'network-check-target-ip-10-0-137-94: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T15:31:39Z"
    - latency: 2.246866ms
      message: 'network-check-target-ip-10-0-137-94: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T15:30:39Z"
    - latency: 2.269591ms
      message: 'network-check-target-ip-10-0-137-94: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T15:29:39Z"
    - latency: 2.142983ms
      message: 'network-check-target-ip-10-0-137-94: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T15:28:39Z"
    - latency: 2.214611ms
      message: 'network-check-target-ip-10-0-137-94: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T15:27:39Z"
    - latency: 1.987369ms
      message: 'network-check-target-ip-10-0-137-94: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T15:26:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T15:00:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-241-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-241.ec2.internal
      uid: 8af52e28-2ddc-4101-a099-ea431c4517e0
    resourceVersion: "56498"
    uid: 095923c1-9c54-4ab2-a518-065d2ee2b128
  spec:
    sourcePod: network-check-source-869dcfcdcd-jtjs8
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T15:06:39Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 969.859µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T15:36:39Z"
    - latency: 1.867788ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T15:36:39Z"
    - latency: 1.18581ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T15:35:39Z"
    - latency: 3.105068ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T15:35:39Z"
    - latency: 1.151236ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T15:34:39Z"
    - latency: 1.630475ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T15:34:39Z"
    - latency: 1.025346ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T15:33:39Z"
    - latency: 1.888716ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T15:33:39Z"
    - latency: 844.843µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T15:32:39Z"
    - latency: 1.82159ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T15:32:39Z"
kind: List
metadata:
  resourceVersion: ""