apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T14:39:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-124-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-124.ec2.internal
      uid: b2a0a9c7-da89-41fd-8b10-770e66ca0964
    resourceVersion: "68307"
    uid: b5a95050-af2c-4964-a80a-8eaedc2e2d16
  spec:
    sourcePod: network-check-source-6f8b768455-fd89k
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T14:46:20Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.004822ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T15:14:20Z"
    - latency: 1.352667ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T15:13:20Z"
    - latency: 968.568µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T15:12:20Z"
    - latency: 1.234969ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T15:11:20Z"
    - latency: 1.324618ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T15:10:20Z"
    - latency: 1.019515ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T15:09:20Z"
    - latency: 1.050079ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T15:08:20Z"
    - latency: 1.086745ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T15:07:20Z"
    - latency: 880.326µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T15:06:20Z"
    - latency: 1.073419ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T15:05:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T14:39:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-124-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-124.ec2.internal
      uid: b2a0a9c7-da89-41fd-8b10-770e66ca0964
    resourceVersion: "69259"
    uid: 16f0aa02-558f-45c4-b007-5e32fd4c3672
  spec:
    sourcePod: network-check-source-6f8b768455-fd89k
    targetEndpoint: ac21a75dbc4f04b6aab1d67eb4022ce7-08ee3ca262adc8ac.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T14:45:20Z"
      message: 'load-balancer-api-external: tcp connection to ac21a75dbc4f04b6aab1d67eb4022ce7-08ee3ca262adc8ac.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.052241ms
      message: 'load-balancer-api-external: tcp connection to ac21a75dbc4f04b6aab1d67eb4022ce7-08ee3ca262adc8ac.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T15:15:20Z"
    - latency: 8.378616ms
      message: 'load-balancer-api-external: resolved host name ac21a75dbc4f04b6aab1d67eb4022ce7-08ee3ca262adc8ac.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T15:15:20Z"
    - latency: 5.223939ms
      message: 'load-balancer-api-external: tcp connection to ac21a75dbc4f04b6aab1d67eb4022ce7-08ee3ca262adc8ac.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T15:14:20Z"
    - latency: 9.72172ms
      message: 'load-balancer-api-external: resolved host name ac21a75dbc4f04b6aab1d67eb4022ce7-08ee3ca262adc8ac.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T15:14:20Z"
    - latency: 3.645666ms
      message: 'load-balancer-api-external: tcp connection to ac21a75dbc4f04b6aab1d67eb4022ce7-08ee3ca262adc8ac.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T15:13:20Z"
    - latency: 7.882297ms
      message: 'load-balancer-api-external: resolved host name ac21a75dbc4f04b6aab1d67eb4022ce7-08ee3ca262adc8ac.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T15:13:20Z"
    - latency: 3.958285ms
      message: 'load-balancer-api-external: tcp connection to ac21a75dbc4f04b6aab1d67eb4022ce7-08ee3ca262adc8ac.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T15:12:20Z"
    - latency: 8.593767ms
      message: 'load-balancer-api-external: resolved host name ac21a75dbc4f04b6aab1d67eb4022ce7-08ee3ca262adc8ac.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T15:12:20Z"
    - latency: 5.331528ms
      message: 'load-balancer-api-external: tcp connection to ac21a75dbc4f04b6aab1d67eb4022ce7-08ee3ca262adc8ac.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T15:11:20Z"
    - latency: 8.103825ms
      message: 'load-balancer-api-external: resolved host name ac21a75dbc4f04b6aab1d67eb4022ce7-08ee3ca262adc8ac.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T15:11:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T14:39:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-124-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-124.ec2.internal
      uid: b2a0a9c7-da89-41fd-8b10-770e66ca0964
    resourceVersion: "69258"
    uid: 340e8c8c-1169-4f0f-a50f-39f6c847c924
  spec:
    sourcePod: network-check-source-6f8b768455-fd89k
    targetEndpoint: ac21a75dbc4f04b6aab1d67eb4022ce7-08ee3ca262adc8ac.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T14:45:20Z"
      message: 'load-balancer-api-internal: tcp connection to ac21a75dbc4f04b6aab1d67eb4022ce7-08ee3ca262adc8ac.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.02981ms
      message: 'load-balancer-api-internal: tcp connection to ac21a75dbc4f04b6aab1d67eb4022ce7-08ee3ca262adc8ac.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T15:15:20Z"
    - latency: 8.433529ms
      message: 'load-balancer-api-internal: resolved host name ac21a75dbc4f04b6aab1d67eb4022ce7-08ee3ca262adc8ac.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T15:15:20Z"
    - latency: 5.245728ms
      message: 'load-balancer-api-internal: tcp connection to ac21a75dbc4f04b6aab1d67eb4022ce7-08ee3ca262adc8ac.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T15:14:20Z"
    - latency: 9.630577ms
      message: 'load-balancer-api-internal: resolved host name ac21a75dbc4f04b6aab1d67eb4022ce7-08ee3ca262adc8ac.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T15:14:20Z"
    - latency: 3.67954ms
      message: 'load-balancer-api-internal: tcp connection to ac21a75dbc4f04b6aab1d67eb4022ce7-08ee3ca262adc8ac.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T15:13:20Z"
    - latency: 7.71477ms
      message: 'load-balancer-api-internal: resolved host name ac21a75dbc4f04b6aab1d67eb4022ce7-08ee3ca262adc8ac.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T15:13:20Z"
    - latency: 4.711773ms
      message: 'load-balancer-api-internal: tcp connection to ac21a75dbc4f04b6aab1d67eb4022ce7-08ee3ca262adc8ac.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T15:12:20Z"
    - latency: 8.485837ms
      message: 'load-balancer-api-internal: resolved host name ac21a75dbc4f04b6aab1d67eb4022ce7-08ee3ca262adc8ac.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T15:12:20Z"
    - latency: 4.270555ms
      message: 'load-balancer-api-internal: tcp connection to ac21a75dbc4f04b6aab1d67eb4022ce7-08ee3ca262adc8ac.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T15:11:20Z"
    - latency: 8.034489ms
      message: 'load-balancer-api-internal: resolved host name ac21a75dbc4f04b6aab1d67eb4022ce7-08ee3ca262adc8ac.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T15:11:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T14:39:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-124-to-network-check-target-ip-10-0-128-123
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-124.ec2.internal
      uid: b2a0a9c7-da89-41fd-8b10-770e66ca0964
    resourceVersion: "68305"
    uid: 7a089fd3-ebdf-4366-82c1-2fc1f94925fa
  spec:
    sourcePod: network-check-source-6f8b768455-fd89k
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T14:46:20Z"
      message: 'network-check-target-ip-10-0-128-123: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.221276ms
      message: 'network-check-target-ip-10-0-128-123: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T15:14:20Z"
    - latency: 2.343882ms
      message: 'network-check-target-ip-10-0-128-123: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T15:13:20Z"
    - latency: 2.452618ms
      message: 'network-check-target-ip-10-0-128-123: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T15:12:20Z"
    - latency: 2.405105ms
      message: 'network-check-target-ip-10-0-128-123: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T15:11:20Z"
    - latency: 2.412962ms
      message: 'network-check-target-ip-10-0-128-123: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T15:10:20Z"
    - latency: 2.575906ms
      message: 'network-check-target-ip-10-0-128-123: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T15:09:20Z"
    - latency: 2.452377ms
      message: 'network-check-target-ip-10-0-128-123: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T15:08:20Z"
    - latency: 2.709218ms
      message: 'network-check-target-ip-10-0-128-123: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T15:07:20Z"
    - latency: 2.148465ms
      message: 'network-check-target-ip-10-0-128-123: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T15:06:20Z"
    - latency: 2.393792ms
      message: 'network-check-target-ip-10-0-128-123: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T15:05:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T14:39:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-124-to-network-check-target-ip-10-0-132-120
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-124.ec2.internal
      uid: b2a0a9c7-da89-41fd-8b10-770e66ca0964
    resourceVersion: "68306"
    uid: 9f097ff3-4664-4014-b57c-d37539121fb1
  spec:
    sourcePod: network-check-source-6f8b768455-fd89k
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T14:46:20Z"
      message: 'network-check-target-ip-10-0-132-120: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.374525ms
      message: 'network-check-target-ip-10-0-132-120: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T15:14:20Z"
    - latency: 2.223088ms
      message: 'network-check-target-ip-10-0-132-120: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T15:13:20Z"
    - latency: 2.719276ms
      message: 'network-check-target-ip-10-0-132-120: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T15:12:20Z"
    - latency: 2.548354ms
      message: 'network-check-target-ip-10-0-132-120: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T15:11:20Z"
    - latency: 2.295094ms
      message: 'network-check-target-ip-10-0-132-120: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T15:10:20Z"
    - latency: 2.458831ms
      message: 'network-check-target-ip-10-0-132-120: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T15:09:20Z"
    - latency: 2.212851ms
      message: 'network-check-target-ip-10-0-132-120: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T15:08:20Z"
    - latency: 2.162679ms
      message: 'network-check-target-ip-10-0-132-120: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T15:07:20Z"
    - latency: 2.394414ms
      message: 'network-check-target-ip-10-0-132-120: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T15:06:20Z"
    - latency: 2.353155ms
      message: 'network-check-target-ip-10-0-132-120: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T15:05:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T14:39:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-124-to-network-check-target-ip-10-0-136-124
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-124.ec2.internal
      uid: b2a0a9c7-da89-41fd-8b10-770e66ca0964
    resourceVersion: "68304"
    uid: f92b5eae-cddd-4eaf-8129-35423aebf9b7
  spec:
    sourcePod: network-check-source-6f8b768455-fd89k
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T14:46:20Z"
      message: 'network-check-target-ip-10-0-136-124: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 992.293µs
      message: 'network-check-target-ip-10-0-136-124: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T15:14:20Z"
    - latency: 952.515µs
      message: 'network-check-target-ip-10-0-136-124: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T15:13:20Z"
    - latency: 1.298816ms
      message: 'network-check-target-ip-10-0-136-124: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T15:12:20Z"
    - latency: 892.769µs
      message: 'network-check-target-ip-10-0-136-124: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T15:11:20Z"
    - latency: 1.095073ms
      message: 'network-check-target-ip-10-0-136-124: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T15:10:20Z"
    - latency: 898.621µs
      message: 'network-check-target-ip-10-0-136-124: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T15:09:20Z"
    - latency: 1.101963ms
      message: 'network-check-target-ip-10-0-136-124: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T15:08:20Z"
    - latency: 1.05892ms
      message: 'network-check-target-ip-10-0-136-124: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T15:07:20Z"
    - latency: 1.052673ms
      message: 'network-check-target-ip-10-0-136-124: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T15:06:20Z"
    - latency: 915.621µs
      message: 'network-check-target-ip-10-0-136-124: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T15:05:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T14:39:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-124-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-124.ec2.internal
      uid: b2a0a9c7-da89-41fd-8b10-770e66ca0964
    resourceVersion: "69256"
    uid: 7813f0e8-7424-4fbe-b1c7-3a46fa198cf7
  spec:
    sourcePod: network-check-source-6f8b768455-fd89k
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T14:45:20Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.104894ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T15:15:20Z"
    - latency: 1.827047ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T15:15:20Z"
    - latency: 982.397µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T15:14:20Z"
    - latency: 1.844083ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T15:14:20Z"
    - latency: 909.422µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T15:13:20Z"
    - latency: 2.132767ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T15:13:20Z"
    - latency: 1.188548ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T15:12:20Z"
    - latency: 1.794375ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T15:12:20Z"
    - latency: 1.082004ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T15:11:20Z"
    - latency: 1.68649ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T15:11:20Z"
kind: List
metadata:
  resourceVersion: ""