apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T19:10:17Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-17-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-17.ec2.internal
      uid: 12339405-ad63-4cbf-ad43-24194723473b
    resourceVersion: "84607"
    uid: 2b6d2894-c7f4-426c-999b-554a859f74f0
  spec:
    sourcePod: network-check-source-6f8b768455-sgz7s
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T19:17:19Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 978.255µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T20:27:19Z"
    - latency: 918.776µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T20:26:19Z"
    - latency: 975.901µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T20:25:19Z"
    - latency: 939.109µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T20:24:19Z"
    - latency: 1.537496ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T20:23:19Z"
    - latency: 902.867µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T20:22:19Z"
    - latency: 934.856µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T20:21:19Z"
    - latency: 1.643212ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T20:20:19Z"
    - latency: 1.517756ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T20:19:19Z"
    - latency: 938.832µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T20:18:19Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T19:10:17Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-17-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-17.ec2.internal
      uid: 12339405-ad63-4cbf-ad43-24194723473b
    resourceVersion: "80722"
    uid: 4b031d25-4e52-476d-ab23-307bdb42a2e4
  spec:
    sourcePod: network-check-source-6f8b768455-sgz7s
    targetEndpoint: ac3ec6656a6c64dd7ad183e1cdeccf4d-070d00bdba6fb3e5.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T19:16:19Z"
      message: 'load-balancer-api-external: tcp connection to ac3ec6656a6c64dd7ad183e1cdeccf4d-070d00bdba6fb3e5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.86436ms
      message: 'load-balancer-api-external: tcp connection to ac3ec6656a6c64dd7ad183e1cdeccf4d-070d00bdba6fb3e5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T20:22:19Z"
    - latency: 8.545375ms
      message: 'load-balancer-api-external: resolved host name ac3ec6656a6c64dd7ad183e1cdeccf4d-070d00bdba6fb3e5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T20:22:19Z"
    - latency: 5.449009ms
      message: 'load-balancer-api-external: tcp connection to ac3ec6656a6c64dd7ad183e1cdeccf4d-070d00bdba6fb3e5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T20:21:19Z"
    - latency: 8.187261ms
      message: 'load-balancer-api-external: resolved host name ac3ec6656a6c64dd7ad183e1cdeccf4d-070d00bdba6fb3e5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T20:21:19Z"
    - latency: 5.751827ms
      message: 'load-balancer-api-external: tcp connection to ac3ec6656a6c64dd7ad183e1cdeccf4d-070d00bdba6fb3e5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T20:20:19Z"
    - latency: 9.829025ms
      message: 'load-balancer-api-external: resolved host name ac3ec6656a6c64dd7ad183e1cdeccf4d-070d00bdba6fb3e5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T20:20:19Z"
    - latency: 6.502361ms
      message: 'load-balancer-api-external: tcp connection to ac3ec6656a6c64dd7ad183e1cdeccf4d-070d00bdba6fb3e5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T20:19:19Z"
    - latency: 8.949241ms
      message: 'load-balancer-api-external: resolved host name ac3ec6656a6c64dd7ad183e1cdeccf4d-070d00bdba6fb3e5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T20:19:19Z"
    - latency: 5.568187ms
      message: 'load-balancer-api-external: tcp connection to ac3ec6656a6c64dd7ad183e1cdeccf4d-070d00bdba6fb3e5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T20:18:19Z"
    - latency: 7.952328ms
      message: 'load-balancer-api-external: resolved host name ac3ec6656a6c64dd7ad183e1cdeccf4d-070d00bdba6fb3e5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T20:18:19Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T19:10:17Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-17-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-17.ec2.internal
      uid: 12339405-ad63-4cbf-ad43-24194723473b
    resourceVersion: "80721"
    uid: 082d5ce3-281e-4bcf-8e1c-0901f5c8291c
  spec:
    sourcePod: network-check-source-6f8b768455-sgz7s
    targetEndpoint: ac3ec6656a6c64dd7ad183e1cdeccf4d-070d00bdba6fb3e5.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T19:16:19Z"
      message: 'load-balancer-api-internal: tcp connection to ac3ec6656a6c64dd7ad183e1cdeccf4d-070d00bdba6fb3e5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.819368ms
      message: 'load-balancer-api-internal: tcp connection to ac3ec6656a6c64dd7ad183e1cdeccf4d-070d00bdba6fb3e5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T20:22:19Z"
    - latency: 8.59323ms
      message: 'load-balancer-api-internal: resolved host name ac3ec6656a6c64dd7ad183e1cdeccf4d-070d00bdba6fb3e5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T20:22:19Z"
    - latency: 5.51827ms
      message: 'load-balancer-api-internal: tcp connection to ac3ec6656a6c64dd7ad183e1cdeccf4d-070d00bdba6fb3e5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T20:21:19Z"
    - latency: 8.159444ms
      message: 'load-balancer-api-internal: resolved host name ac3ec6656a6c64dd7ad183e1cdeccf4d-070d00bdba6fb3e5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T20:21:19Z"
    - latency: 7.125542ms
      message: 'load-balancer-api-internal: tcp connection to ac3ec6656a6c64dd7ad183e1cdeccf4d-070d00bdba6fb3e5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T20:20:19Z"
    - latency: 9.876943ms
      message: 'load-balancer-api-internal: resolved host name ac3ec6656a6c64dd7ad183e1cdeccf4d-070d00bdba6fb3e5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T20:20:19Z"
    - latency: 5.450307ms
      message: 'load-balancer-api-internal: tcp connection to ac3ec6656a6c64dd7ad183e1cdeccf4d-070d00bdba6fb3e5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T20:19:19Z"
    - latency: 8.97415ms
      message: 'load-balancer-api-internal: resolved host name ac3ec6656a6c64dd7ad183e1cdeccf4d-070d00bdba6fb3e5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T20:19:19Z"
    - latency: 5.57445ms
      message: 'load-balancer-api-internal: tcp connection to ac3ec6656a6c64dd7ad183e1cdeccf4d-070d00bdba6fb3e5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T20:18:19Z"
    - latency: 7.940635ms
      message: 'load-balancer-api-internal: resolved host name ac3ec6656a6c64dd7ad183e1cdeccf4d-070d00bdba6fb3e5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T20:18:19Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T19:10:17Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-17-to-network-check-target-ip-10-0-128-148
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-17.ec2.internal
      uid: 12339405-ad63-4cbf-ad43-24194723473b
    resourceVersion: "84606"
    uid: 64ebc3ad-599d-4775-bee0-d2cac0edb6d3
  spec:
    sourcePod: network-check-source-6f8b768455-sgz7s
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T19:17:19Z"
      message: 'network-check-target-ip-10-0-128-148: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.284092ms
      message: 'network-check-target-ip-10-0-128-148: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T20:27:19Z"
    - latency: 2.111886ms
      message: 'network-check-target-ip-10-0-128-148: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T20:26:19Z"
    - latency: 2.51334ms
      message: 'network-check-target-ip-10-0-128-148: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T20:25:19Z"
    - latency: 2.499694ms
      message: 'network-check-target-ip-10-0-128-148: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T20:24:19Z"
    - latency: 2.359311ms
      message: 'network-check-target-ip-10-0-128-148: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T20:23:19Z"
    - latency: 2.329842ms
      message: 'network-check-target-ip-10-0-128-148: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T20:22:19Z"
    - latency: 2.518197ms
      message: 'network-check-target-ip-10-0-128-148: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T20:21:19Z"
    - latency: 2.403613ms
      message: 'network-check-target-ip-10-0-128-148: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T20:20:19Z"
    - latency: 2.754872ms
      message: 'network-check-target-ip-10-0-128-148: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T20:19:19Z"
    - latency: 2.216219ms
      message: 'network-check-target-ip-10-0-128-148: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T20:18:19Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T19:10:17Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-17-to-network-check-target-ip-10-0-139-148
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-17.ec2.internal
      uid: 12339405-ad63-4cbf-ad43-24194723473b
    resourceVersion: "84605"
    uid: 3ea49821-e69c-4000-8df7-f4dcfe5d5865
  spec:
    sourcePod: network-check-source-6f8b768455-sgz7s
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T19:17:19Z"
      message: 'network-check-target-ip-10-0-139-148: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.332936ms
      message: 'network-check-target-ip-10-0-139-148: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T20:27:19Z"
    - latency: 1.810564ms
      message: 'network-check-target-ip-10-0-139-148: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T20:26:19Z"
    - latency: 2.006133ms
      message: 'network-check-target-ip-10-0-139-148: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T20:25:19Z"
    - latency: 2.130007ms
      message: 'network-check-target-ip-10-0-139-148: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T20:24:19Z"
    - latency: 2.111709ms
      message: 'network-check-target-ip-10-0-139-148: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T20:23:19Z"
    - latency: 2.007345ms
      message: 'network-check-target-ip-10-0-139-148: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T20:22:19Z"
    - latency: 2.094385ms
      message: 'network-check-target-ip-10-0-139-148: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T20:21:19Z"
    - latency: 2.101326ms
      message: 'network-check-target-ip-10-0-139-148: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T20:20:19Z"
    - latency: 2.176168ms
      message: 'network-check-target-ip-10-0-139-148: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T20:19:19Z"
    - latency: 2.071548ms
      message: 'network-check-target-ip-10-0-139-148: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T20:18:19Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T19:10:17Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-17-to-network-check-target-ip-10-0-139-17
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-17.ec2.internal
      uid: 12339405-ad63-4cbf-ad43-24194723473b
    resourceVersion: "84604"
    uid: 3a9f5bd9-0e84-4b6a-9355-a11bd3225d0a
  spec:
    sourcePod: network-check-source-6f8b768455-sgz7s
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T19:17:19Z"
      message: 'network-check-target-ip-10-0-139-17: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.17922ms
      message: 'network-check-target-ip-10-0-139-17: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T20:27:19Z"
    - latency: 962.804µs
      message: 'network-check-target-ip-10-0-139-17: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T20:26:19Z"
    - latency: 899.332µs
      message: 'network-check-target-ip-10-0-139-17: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T20:25:19Z"
    - latency: 963.405µs
      message: 'network-check-target-ip-10-0-139-17: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T20:24:19Z"
    - latency: 1.251887ms
      message: 'network-check-target-ip-10-0-139-17: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T20:23:19Z"
    - latency: 794.944µs
      message: 'network-check-target-ip-10-0-139-17: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T20:22:19Z"
    - latency: 1.261536ms
      message: 'network-check-target-ip-10-0-139-17: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T20:21:19Z"
    - latency: 749.008µs
      message: 'network-check-target-ip-10-0-139-17: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T20:20:19Z"
    - latency: 1.454333ms
      message: 'network-check-target-ip-10-0-139-17: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T20:19:19Z"
    - latency: 923.96µs
      message: 'network-check-target-ip-10-0-139-17: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T20:18:19Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T19:10:17Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-17-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-17.ec2.internal
      uid: 12339405-ad63-4cbf-ad43-24194723473b
    resourceVersion: "80720"
    uid: d5eb6952-779b-4eb2-a5be-dccbaf4c3a5f
  spec:
    sourcePod: network-check-source-6f8b768455-sgz7s
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T19:16:19Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 785.159µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T20:22:19Z"
    - latency: 2.323806ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T20:22:19Z"
    - latency: 1.275881ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T20:21:19Z"
    - latency: 1.806993ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T20:21:19Z"
    - latency: 1.37993ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T20:20:19Z"
    - latency: 1.962577ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T20:20:19Z"
    - latency: 789.72µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T20:19:19Z"
    - latency: 1.860993ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T20:19:19Z"
    - latency: 946.099µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T20:18:19Z"
    - latency: 1.774014ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T20:18:19Z"
kind: List
metadata:
  resourceVersion: ""