apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T21:42:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-44-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-44.ec2.internal
      uid: f90d2caa-b67a-4f2a-9a9b-277c641d60df
    resourceVersion: "54799"
    uid: 15585dad-e92e-4829-b664-19361fe96d64
  spec:
    sourcePod: network-check-source-7bc5b6bf85-tk5mx
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T21:49:06Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.626365ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:17:06Z"
    - latency: 1.594933ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:16:06Z"
    - latency: 1.261749ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:15:06Z"
    - latency: 1.138016ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:14:06Z"
    - latency: 1.055632ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:13:06Z"
    - latency: 1.025016ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:12:06Z"
    - latency: 1.045612ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:11:06Z"
    - latency: 1.017319ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:10:06Z"
    - latency: 1.32215ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:09:06Z"
    - latency: 1.607201ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:08:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T21:42:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-44-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-44.ec2.internal
      uid: f90d2caa-b67a-4f2a-9a9b-277c641d60df
    resourceVersion: "55849"
    uid: 8d9daef3-2daa-425a-9c33-b4833438be7a
  spec:
    sourcePod: network-check-source-7bc5b6bf85-tk5mx
    targetEndpoint: a617a8d19ff59485db3937b03626dadb-98f3f004a891bbcb.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T21:48:06Z"
      message: 'load-balancer-api-external: tcp connection to a617a8d19ff59485db3937b03626dadb-98f3f004a891bbcb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.289289ms
      message: 'load-balancer-api-external: tcp connection to a617a8d19ff59485db3937b03626dadb-98f3f004a891bbcb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:18:06Z"
    - latency: 9.577255ms
      message: 'load-balancer-api-external: resolved host name a617a8d19ff59485db3937b03626dadb-98f3f004a891bbcb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T22:18:06Z"
    - latency: 7.141918ms
      message: 'load-balancer-api-external: tcp connection to a617a8d19ff59485db3937b03626dadb-98f3f004a891bbcb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:17:06Z"
    - latency: 8.30674ms
      message: 'load-balancer-api-external: resolved host name a617a8d19ff59485db3937b03626dadb-98f3f004a891bbcb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T22:17:06Z"
    - latency: 4.382404ms
      message: 'load-balancer-api-external: tcp connection to a617a8d19ff59485db3937b03626dadb-98f3f004a891bbcb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:16:06Z"
    - latency: 11.619102ms
      message: 'load-balancer-api-external: resolved host name a617a8d19ff59485db3937b03626dadb-98f3f004a891bbcb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T22:16:06Z"
    - latency: 4.877198ms
      message: 'load-balancer-api-external: tcp connection to a617a8d19ff59485db3937b03626dadb-98f3f004a891bbcb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:15:06Z"
    - latency: 9.353121ms
      message: 'load-balancer-api-external: resolved host name a617a8d19ff59485db3937b03626dadb-98f3f004a891bbcb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T22:15:06Z"
    - latency: 4.752295ms
      message: 'load-balancer-api-external: tcp connection to a617a8d19ff59485db3937b03626dadb-98f3f004a891bbcb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:14:06Z"
    - latency: 7.246005ms
      message: 'load-balancer-api-external: resolved host name a617a8d19ff59485db3937b03626dadb-98f3f004a891bbcb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T22:14:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T21:42:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-44-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-44.ec2.internal
      uid: f90d2caa-b67a-4f2a-9a9b-277c641d60df
    resourceVersion: "55848"
    uid: 086d0d9f-5556-464a-896d-fbd8c3e3d2f9
  spec:
    sourcePod: network-check-source-7bc5b6bf85-tk5mx
    targetEndpoint: a617a8d19ff59485db3937b03626dadb-98f3f004a891bbcb.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T21:48:06Z"
      message: 'load-balancer-api-internal: tcp connection to a617a8d19ff59485db3937b03626dadb-98f3f004a891bbcb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.637152ms
      message: 'load-balancer-api-internal: tcp connection to a617a8d19ff59485db3937b03626dadb-98f3f004a891bbcb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:18:06Z"
    - latency: 9.532187ms
      message: 'load-balancer-api-internal: resolved host name a617a8d19ff59485db3937b03626dadb-98f3f004a891bbcb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T22:18:06Z"
    - latency: 7.080911ms
      message: 'load-balancer-api-internal: tcp connection to a617a8d19ff59485db3937b03626dadb-98f3f004a891bbcb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:17:06Z"
    - latency: 8.389966ms
      message: 'load-balancer-api-internal: resolved host name a617a8d19ff59485db3937b03626dadb-98f3f004a891bbcb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T22:17:06Z"
    - latency: 6.643654ms
      message: 'load-balancer-api-internal: tcp connection to a617a8d19ff59485db3937b03626dadb-98f3f004a891bbcb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:16:06Z"
    - latency: 11.647098ms
      message: 'load-balancer-api-internal: resolved host name a617a8d19ff59485db3937b03626dadb-98f3f004a891bbcb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T22:16:06Z"
    - latency: 3.594549ms
      message: 'load-balancer-api-internal: tcp connection to a617a8d19ff59485db3937b03626dadb-98f3f004a891bbcb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:15:06Z"
    - latency: 9.264226ms
      message: 'load-balancer-api-internal: resolved host name a617a8d19ff59485db3937b03626dadb-98f3f004a891bbcb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T22:15:06Z"
    - latency: 5.476826ms
      message: 'load-balancer-api-internal: tcp connection to a617a8d19ff59485db3937b03626dadb-98f3f004a891bbcb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:14:06Z"
    - latency: 7.124241ms
      message: 'load-balancer-api-internal: resolved host name a617a8d19ff59485db3937b03626dadb-98f3f004a891bbcb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T22:14:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T21:42:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-44-to-network-check-target-ip-10-0-133-93
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-44.ec2.internal
      uid: f90d2caa-b67a-4f2a-9a9b-277c641d60df
    resourceVersion: "54797"
    uid: b0d6fb4f-fae5-4dbd-812c-cdbaafe4417b
  spec:
    sourcePod: network-check-source-7bc5b6bf85-tk5mx
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T21:49:06Z"
      message: 'network-check-target-ip-10-0-133-93: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.927085ms
      message: 'network-check-target-ip-10-0-133-93: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:17:06Z"
    - latency: 2.309604ms
      message: 'network-check-target-ip-10-0-133-93: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:16:06Z"
    - latency: 2.227026ms
      message: 'network-check-target-ip-10-0-133-93: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:15:06Z"
    - latency: 2.214879ms
      message: 'network-check-target-ip-10-0-133-93: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:14:06Z"
    - latency: 2.342607ms
      message: 'network-check-target-ip-10-0-133-93: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:13:06Z"
    - latency: 2.018924ms
      message: 'network-check-target-ip-10-0-133-93: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:12:06Z"
    - latency: 2.321795ms
      message: 'network-check-target-ip-10-0-133-93: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:11:06Z"
    - latency: 1.848698ms
      message: 'network-check-target-ip-10-0-133-93: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:10:06Z"
    - latency: 2.031129ms
      message: 'network-check-target-ip-10-0-133-93: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:09:06Z"
    - latency: 2.117977ms
      message: 'network-check-target-ip-10-0-133-93: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:08:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T21:42:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-44-to-network-check-target-ip-10-0-136-44
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-44.ec2.internal
      uid: f90d2caa-b67a-4f2a-9a9b-277c641d60df
    resourceVersion: "54796"
    uid: 8326d46a-f4b5-4bcb-bfe9-94732a4c8172
  spec:
    sourcePod: network-check-source-7bc5b6bf85-tk5mx
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T21:49:06Z"
      message: 'network-check-target-ip-10-0-136-44: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.096187ms
      message: 'network-check-target-ip-10-0-136-44: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:17:06Z"
    - latency: 978.19µs
      message: 'network-check-target-ip-10-0-136-44: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:16:06Z"
    - latency: 1.038011ms
      message: 'network-check-target-ip-10-0-136-44: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:15:06Z"
    - latency: 938.305µs
      message: 'network-check-target-ip-10-0-136-44: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:14:06Z"
    - latency: 930.598µs
      message: 'network-check-target-ip-10-0-136-44: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:13:06Z"
    - latency: 1.226688ms
      message: 'network-check-target-ip-10-0-136-44: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:12:06Z"
    - latency: 1.584712ms
      message: 'network-check-target-ip-10-0-136-44: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:11:06Z"
    - latency: 1.215319ms
      message: 'network-check-target-ip-10-0-136-44: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:10:06Z"
    - latency: 902.142µs
      message: 'network-check-target-ip-10-0-136-44: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:09:06Z"
    - latency: 929.7µs
      message: 'network-check-target-ip-10-0-136-44: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:08:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T21:42:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-44-to-network-check-target-ip-10-0-142-10
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-44.ec2.internal
      uid: f90d2caa-b67a-4f2a-9a9b-277c641d60df
    resourceVersion: "54798"
    uid: 3430fde6-6e4a-46a8-8e01-018cc06b6e3a
  spec:
    sourcePod: network-check-source-7bc5b6bf85-tk5mx
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T21:49:06Z"
      message: 'network-check-target-ip-10-0-142-10: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.242569ms
      message: 'network-check-target-ip-10-0-142-10: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:17:06Z"
    - latency: 2.22338ms
      message: 'network-check-target-ip-10-0-142-10: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:16:06Z"
    - latency: 2.201081ms
      message: 'network-check-target-ip-10-0-142-10: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:15:06Z"
    - latency: 2.553521ms
      message: 'network-check-target-ip-10-0-142-10: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:14:06Z"
    - latency: 2.040236ms
      message: 'network-check-target-ip-10-0-142-10: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:13:06Z"
    - latency: 2.036035ms
      message: 'network-check-target-ip-10-0-142-10: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:12:06Z"
    - latency: 2.612723ms
      message: 'network-check-target-ip-10-0-142-10: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:11:06Z"
    - latency: 2.287298ms
      message: 'network-check-target-ip-10-0-142-10: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:10:06Z"
    - latency: 2.185299ms
      message: 'network-check-target-ip-10-0-142-10: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:09:06Z"
    - latency: 2.191727ms
      message: 'network-check-target-ip-10-0-142-10: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:08:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T21:42:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-44-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-44.ec2.internal
      uid: f90d2caa-b67a-4f2a-9a9b-277c641d60df
    resourceVersion: "55847"
    uid: fb41bd31-b2af-4d40-a647-82060eb3b5b7
  spec:
    sourcePod: network-check-source-7bc5b6bf85-tk5mx
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T21:48:06Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 899.368µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:18:06Z"
    - latency: 2.537504ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T22:18:06Z"
    - latency: 1.3394ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:17:06Z"
    - latency: 2.080501ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T22:17:06Z"
    - latency: 980.002µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:16:06Z"
    - latency: 1.912524ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T22:16:06Z"
    - latency: 1.43121ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:15:06Z"
    - latency: 1.962455ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T22:15:06Z"
    - latency: 872.892µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:14:06Z"
    - latency: 1.789426ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T22:14:06Z"
kind: List
metadata:
  resourceVersion: ""