apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-22T17:40:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-36-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-36.ec2.internal
      uid: e514979a-7805-4a66-8012-129b0b075d3a
    resourceVersion: "39457"
    uid: 0654aef9-dff0-4fa6-a1c2-aa13377eeb4d
  spec:
    sourcePod: network-check-source-8894fc9bd-pwhxf
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-04-22T17:47:08Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.305286ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T18:08:08Z"
    - latency: 853.319µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T18:07:08Z"
    - latency: 1.036063ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T18:06:08Z"
    - latency: 1.287827ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T18:05:08Z"
    - latency: 1.296855ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T18:04:08Z"
    - latency: 1.443846ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T18:03:08Z"
    - latency: 1.088434ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T18:02:08Z"
    - latency: 930.685µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T18:01:08Z"
    - latency: 1.112719ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T18:00:08Z"
    - latency: 1.391126ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T17:59:08Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-22T17:40:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-36-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-36.ec2.internal
      uid: e514979a-7805-4a66-8012-129b0b075d3a
    resourceVersion: "35733"
    uid: b4fdad47-8cbf-4087-9895-8e3f33b68849
  spec:
    sourcePod: network-check-source-8894fc9bd-pwhxf
    targetEndpoint: ab183528b5e0846c5b2cd8ad45778e7b-42d69154150c6fea.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-04-22T17:46:08Z"
      message: 'load-balancer-api-external: tcp connection to ab183528b5e0846c5b2cd8ad45778e7b-42d69154150c6fea.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.603334ms
      message: 'load-balancer-api-external: tcp connection to ab183528b5e0846c5b2cd8ad45778e7b-42d69154150c6fea.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T18:04:08Z"
    - latency: 6.839945ms
      message: 'load-balancer-api-external: resolved host name ab183528b5e0846c5b2cd8ad45778e7b-42d69154150c6fea.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T18:04:08Z"
    - latency: 4.075097ms
      message: 'load-balancer-api-external: tcp connection to ab183528b5e0846c5b2cd8ad45778e7b-42d69154150c6fea.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T18:03:08Z"
    - latency: 6.969931ms
      message: 'load-balancer-api-external: resolved host name ab183528b5e0846c5b2cd8ad45778e7b-42d69154150c6fea.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T18:03:08Z"
    - latency: 4.223455ms
      message: 'load-balancer-api-external: tcp connection to ab183528b5e0846c5b2cd8ad45778e7b-42d69154150c6fea.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T18:02:08Z"
    - latency: 10.982593ms
      message: 'load-balancer-api-external: resolved host name ab183528b5e0846c5b2cd8ad45778e7b-42d69154150c6fea.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T18:02:08Z"
    - latency: 4.254799ms
      message: 'load-balancer-api-external: tcp connection to ab183528b5e0846c5b2cd8ad45778e7b-42d69154150c6fea.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T18:01:08Z"
    - latency: 9.11689ms
      message: 'load-balancer-api-external: resolved host name ab183528b5e0846c5b2cd8ad45778e7b-42d69154150c6fea.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T18:01:08Z"
    - latency: 5.101788ms
      message: 'load-balancer-api-external: tcp connection to ab183528b5e0846c5b2cd8ad45778e7b-42d69154150c6fea.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T18:00:08Z"
    - latency: 7.416766ms
      message: 'load-balancer-api-external: resolved host name ab183528b5e0846c5b2cd8ad45778e7b-42d69154150c6fea.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T18:00:08Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-22T17:40:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-36-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-36.ec2.internal
      uid: e514979a-7805-4a66-8012-129b0b075d3a
    resourceVersion: "35734"
    uid: c5468f4e-61ba-49fa-882d-8599b86c359a
  spec:
    sourcePod: network-check-source-8894fc9bd-pwhxf
    targetEndpoint: ab183528b5e0846c5b2cd8ad45778e7b-42d69154150c6fea.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-04-22T17:46:08Z"
      message: 'load-balancer-api-internal: tcp connection to ab183528b5e0846c5b2cd8ad45778e7b-42d69154150c6fea.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.240588ms
      message: 'load-balancer-api-internal: tcp connection to ab183528b5e0846c5b2cd8ad45778e7b-42d69154150c6fea.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T18:04:08Z"
    - latency: 6.983245ms
      message: 'load-balancer-api-internal: resolved host name ab183528b5e0846c5b2cd8ad45778e7b-42d69154150c6fea.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T18:04:08Z"
    - latency: 4.64571ms
      message: 'load-balancer-api-internal: tcp connection to ab183528b5e0846c5b2cd8ad45778e7b-42d69154150c6fea.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T18:03:08Z"
    - latency: 7.022478ms
      message: 'load-balancer-api-internal: resolved host name ab183528b5e0846c5b2cd8ad45778e7b-42d69154150c6fea.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T18:03:08Z"
    - latency: 4.217161ms
      message: 'load-balancer-api-internal: tcp connection to ab183528b5e0846c5b2cd8ad45778e7b-42d69154150c6fea.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T18:02:08Z"
    - latency: 11.021991ms
      message: 'load-balancer-api-internal: resolved host name ab183528b5e0846c5b2cd8ad45778e7b-42d69154150c6fea.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T18:02:08Z"
    - latency: 4.232105ms
      message: 'load-balancer-api-internal: tcp connection to ab183528b5e0846c5b2cd8ad45778e7b-42d69154150c6fea.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T18:01:08Z"
    - latency: 9.209086ms
      message: 'load-balancer-api-internal: resolved host name ab183528b5e0846c5b2cd8ad45778e7b-42d69154150c6fea.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T18:01:08Z"
    - latency: 4.553604ms
      message: 'load-balancer-api-internal: tcp connection to ab183528b5e0846c5b2cd8ad45778e7b-42d69154150c6fea.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T18:00:08Z"
    - latency: 7.437976ms
      message: 'load-balancer-api-internal: resolved host name ab183528b5e0846c5b2cd8ad45778e7b-42d69154150c6fea.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T18:00:08Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-22T17:40:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-36-to-network-check-target-ip-10-0-133-169
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-36.ec2.internal
      uid: e514979a-7805-4a66-8012-129b0b075d3a
    resourceVersion: "39456"
    uid: 0246d077-e7d5-4c8e-be7b-987b49f6a3f3
  spec:
    sourcePod: network-check-source-8894fc9bd-pwhxf
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-22T17:47:08Z"
      message: 'network-check-target-ip-10-0-133-169: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.163846ms
      message: 'network-check-target-ip-10-0-133-169: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T18:08:08Z"
    - latency: 1.825678ms
      message: 'network-check-target-ip-10-0-133-169: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T18:07:08Z"
    - latency: 2.103972ms
      message: 'network-check-target-ip-10-0-133-169: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T18:06:08Z"
    - latency: 2.271233ms
      message: 'network-check-target-ip-10-0-133-169: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T18:05:08Z"
    - latency: 3.003974ms
      message: 'network-check-target-ip-10-0-133-169: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T18:04:08Z"
    - latency: 2.276104ms
      message: 'network-check-target-ip-10-0-133-169: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T18:03:08Z"
    - latency: 2.175908ms
      message: 'network-check-target-ip-10-0-133-169: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T18:02:08Z"
    - latency: 3.658332ms
      message: 'network-check-target-ip-10-0-133-169: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T18:01:08Z"
    - latency: 2.005643ms
      message: 'network-check-target-ip-10-0-133-169: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T18:00:08Z"
    - latency: 2.166929ms
      message: 'network-check-target-ip-10-0-133-169: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T17:59:08Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-22T17:40:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-36-to-network-check-target-ip-10-0-135-36
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-36.ec2.internal
      uid: e514979a-7805-4a66-8012-129b0b075d3a
    resourceVersion: "39454"
    uid: 86715d46-bd40-41ae-b88e-97437c2b9a81
  spec:
    sourcePod: network-check-source-8894fc9bd-pwhxf
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-22T17:47:08Z"
      message: 'network-check-target-ip-10-0-135-36: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.59129ms
      message: 'network-check-target-ip-10-0-135-36: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T18:08:08Z"
    - latency: 851.392µs
      message: 'network-check-target-ip-10-0-135-36: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T18:07:08Z"
    - latency: 1.144996ms
      message: 'network-check-target-ip-10-0-135-36: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T18:06:08Z"
    - latency: 1.550098ms
      message: 'network-check-target-ip-10-0-135-36: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T18:05:08Z"
    - latency: 1.801315ms
      message: 'network-check-target-ip-10-0-135-36: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T18:04:08Z"
    - latency: 844.631µs
      message: 'network-check-target-ip-10-0-135-36: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T18:03:08Z"
    - latency: 942.968µs
      message: 'network-check-target-ip-10-0-135-36: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T18:02:08Z"
    - latency: 1.362031ms
      message: 'network-check-target-ip-10-0-135-36: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T18:01:08Z"
    - latency: 1.244107ms
      message: 'network-check-target-ip-10-0-135-36: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T18:00:08Z"
    - latency: 870.992µs
      message: 'network-check-target-ip-10-0-135-36: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T17:59:08Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-22T17:40:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-36-to-network-check-target-ip-10-0-143-54
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-36.ec2.internal
      uid: e514979a-7805-4a66-8012-129b0b075d3a
    resourceVersion: "39455"
    uid: e3f113bc-5f3c-429e-bc29-0e7b0982c6f6
  spec:
    sourcePod: network-check-source-8894fc9bd-pwhxf
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-22T17:47:08Z"
      message: 'network-check-target-ip-10-0-143-54: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.051371ms
      message: 'network-check-target-ip-10-0-143-54: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T18:08:08Z"
    - latency: 1.527018ms
      message: 'network-check-target-ip-10-0-143-54: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T18:07:08Z"
    - latency: 1.981885ms
      message: 'network-check-target-ip-10-0-143-54: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T18:06:08Z"
    - latency: 2.358337ms
      message: 'network-check-target-ip-10-0-143-54: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T18:05:08Z"
    - latency: 1.786453ms
      message: 'network-check-target-ip-10-0-143-54: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T18:04:08Z"
    - latency: 1.900108ms
      message: 'network-check-target-ip-10-0-143-54: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T18:03:08Z"
    - latency: 1.934637ms
      message: 'network-check-target-ip-10-0-143-54: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T18:02:08Z"
    - latency: 2.349237ms
      message: 'network-check-target-ip-10-0-143-54: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T18:01:08Z"
    - latency: 1.910676ms
      message: 'network-check-target-ip-10-0-143-54: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T18:00:08Z"
    - latency: 2.024684ms
      message: 'network-check-target-ip-10-0-143-54: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T17:59:08Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-22T17:40:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-36-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-36.ec2.internal
      uid: e514979a-7805-4a66-8012-129b0b075d3a
    resourceVersion: "35732"
    uid: 066d9224-fa34-454f-ad7d-b70327408a8f
  spec:
    sourcePod: network-check-source-8894fc9bd-pwhxf
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-04-22T17:46:08Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 998.365µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T18:04:08Z"
    - latency: 2.247278ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T18:04:08Z"
    - latency: 1.112148ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T18:03:08Z"
    - latency: 1.805728ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T18:03:08Z"
    - latency: 1.154439ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T18:02:08Z"
    - latency: 1.705414ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T18:02:08Z"
    - latency: 1.038049ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T18:01:08Z"
    - latency: 2.171957ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T18:01:08Z"
    - latency: 852.565µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T18:00:08Z"
    - latency: 2.019233ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T18:00:08Z"
kind: List
metadata:
  resourceVersion: ""