apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T18:38:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-204-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-204.us-east-2.compute.internal
      uid: e5717a82-68fd-486e-8404-ab65345c02b7
    resourceVersion: "24787"
    uid: b34957e5-679d-4858-88da-6866869d5a26
  spec:
    sourcePod: network-check-source-6f78d59f99-jgqpm
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T18:45:40Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.771972ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:20:40Z"
    - latency: 863.038µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:19:40Z"
    - latency: 1.173474ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:18:40Z"
    - latency: 1.281307ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:17:40Z"
    - latency: 1.046144ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:16:40Z"
    - latency: 1.205519ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:15:40Z"
    - latency: 963.325µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:14:40Z"
    - latency: 1.145219ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:13:40Z"
    - latency: 1.145462ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:12:40Z"
    - latency: 1.064345ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:11:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T18:38:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-204-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-204.us-east-2.compute.internal
      uid: e5717a82-68fd-486e-8404-ab65345c02b7
    resourceVersion: "26423"
    uid: f1571716-0df4-4444-84bc-e6c7104f4e5e
  spec:
    sourcePod: network-check-source-6f78d59f99-jgqpm
    targetEndpoint: a71bc129ddd434d9489b2359e56d2ae6-89b5c295bf3e08c4.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T18:44:40Z"
      message: 'load-balancer-api-external: tcp connection to a71bc129ddd434d9489b2359e56d2ae6-89b5c295bf3e08c4.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.051495ms
      message: 'load-balancer-api-external: tcp connection to a71bc129ddd434d9489b2359e56d2ae6-89b5c295bf3e08c4.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:26:40Z"
    - latency: 8.615071ms
      message: 'load-balancer-api-external: resolved host name a71bc129ddd434d9489b2359e56d2ae6-89b5c295bf3e08c4.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T19:26:40Z"
    - latency: 5.391042ms
      message: 'load-balancer-api-external: tcp connection to a71bc129ddd434d9489b2359e56d2ae6-89b5c295bf3e08c4.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:25:40Z"
    - latency: 7.72149ms
      message: 'load-balancer-api-external: resolved host name a71bc129ddd434d9489b2359e56d2ae6-89b5c295bf3e08c4.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T19:25:40Z"
    - latency: 5.548874ms
      message: 'load-balancer-api-external: tcp connection to a71bc129ddd434d9489b2359e56d2ae6-89b5c295bf3e08c4.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:24:40Z"
    - latency: 8.431007ms
      message: 'load-balancer-api-external: resolved host name a71bc129ddd434d9489b2359e56d2ae6-89b5c295bf3e08c4.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T19:24:40Z"
    - latency: 5.077231ms
      message: 'load-balancer-api-external: tcp connection to a71bc129ddd434d9489b2359e56d2ae6-89b5c295bf3e08c4.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:23:40Z"
    - latency: 8.812396ms
      message: 'load-balancer-api-external: resolved host name a71bc129ddd434d9489b2359e56d2ae6-89b5c295bf3e08c4.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T19:23:40Z"
    - latency: 6.458168ms
      message: 'load-balancer-api-external: tcp connection to a71bc129ddd434d9489b2359e56d2ae6-89b5c295bf3e08c4.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:22:40Z"
    - latency: 8.478698ms
      message: 'load-balancer-api-external: resolved host name a71bc129ddd434d9489b2359e56d2ae6-89b5c295bf3e08c4.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T19:22:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T18:38:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-204-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-204.us-east-2.compute.internal
      uid: e5717a82-68fd-486e-8404-ab65345c02b7
    resourceVersion: "26422"
    uid: 06c83919-a611-4cdf-a343-ee65ebeada95
  spec:
    sourcePod: network-check-source-6f78d59f99-jgqpm
    targetEndpoint: a71bc129ddd434d9489b2359e56d2ae6-89b5c295bf3e08c4.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T18:44:40Z"
      message: 'load-balancer-api-internal: tcp connection to a71bc129ddd434d9489b2359e56d2ae6-89b5c295bf3e08c4.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.088151ms
      message: 'load-balancer-api-internal: tcp connection to a71bc129ddd434d9489b2359e56d2ae6-89b5c295bf3e08c4.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:26:40Z"
    - latency: 8.53837ms
      message: 'load-balancer-api-internal: resolved host name a71bc129ddd434d9489b2359e56d2ae6-89b5c295bf3e08c4.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T19:26:40Z"
    - latency: 5.402159ms
      message: 'load-balancer-api-internal: tcp connection to a71bc129ddd434d9489b2359e56d2ae6-89b5c295bf3e08c4.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:25:40Z"
    - latency: 7.622ms
      message: 'load-balancer-api-internal: resolved host name a71bc129ddd434d9489b2359e56d2ae6-89b5c295bf3e08c4.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T19:25:40Z"
    - latency: 5.559717ms
      message: 'load-balancer-api-internal: tcp connection to a71bc129ddd434d9489b2359e56d2ae6-89b5c295bf3e08c4.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:24:40Z"
    - latency: 8.327083ms
      message: 'load-balancer-api-internal: resolved host name a71bc129ddd434d9489b2359e56d2ae6-89b5c295bf3e08c4.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T19:24:40Z"
    - latency: 5.04401ms
      message: 'load-balancer-api-internal: tcp connection to a71bc129ddd434d9489b2359e56d2ae6-89b5c295bf3e08c4.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:23:40Z"
    - latency: 8.913343ms
      message: 'load-balancer-api-internal: resolved host name a71bc129ddd434d9489b2359e56d2ae6-89b5c295bf3e08c4.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T19:23:40Z"
    - latency: 5.373372ms
      message: 'load-balancer-api-internal: tcp connection to a71bc129ddd434d9489b2359e56d2ae6-89b5c295bf3e08c4.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:22:40Z"
    - latency: 8.425579ms
      message: 'load-balancer-api-internal: resolved host name a71bc129ddd434d9489b2359e56d2ae6-89b5c295bf3e08c4.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T19:22:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T18:38:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-204-to-network-check-target-ip-10-0-131-204
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-204.us-east-2.compute.internal
      uid: e5717a82-68fd-486e-8404-ab65345c02b7
    resourceVersion: "24783"
    uid: cea99cef-a864-4409-9c83-c596ff82cc6f
  spec:
    sourcePod: network-check-source-6f78d59f99-jgqpm
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T18:45:40Z"
      message: 'network-check-target-ip-10-0-131-204: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 827.192µs
      message: 'network-check-target-ip-10-0-131-204: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:20:40Z"
    - latency: 700.792µs
      message: 'network-check-target-ip-10-0-131-204: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:19:40Z"
    - latency: 796.139µs
      message: 'network-check-target-ip-10-0-131-204: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:18:40Z"
    - latency: 1.472947ms
      message: 'network-check-target-ip-10-0-131-204: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:17:40Z"
    - latency: 827.514µs
      message: 'network-check-target-ip-10-0-131-204: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:16:40Z"
    - latency: 792.548µs
      message: 'network-check-target-ip-10-0-131-204: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:15:40Z"
    - latency: 866.943µs
      message: 'network-check-target-ip-10-0-131-204: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:14:40Z"
    - latency: 785.78µs
      message: 'network-check-target-ip-10-0-131-204: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:13:40Z"
    - latency: 756.735µs
      message: 'network-check-target-ip-10-0-131-204: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:12:40Z"
    - latency: 935.575µs
      message: 'network-check-target-ip-10-0-131-204: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:11:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T18:38:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-204-to-network-check-target-ip-10-0-138-133
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-204.us-east-2.compute.internal
      uid: e5717a82-68fd-486e-8404-ab65345c02b7
    resourceVersion: "24784"
    uid: ffbf3539-5faa-4a24-a460-9abddd760305
  spec:
    sourcePod: network-check-source-6f78d59f99-jgqpm
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T18:45:40Z"
      message: 'network-check-target-ip-10-0-138-133: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.748317ms
      message: 'network-check-target-ip-10-0-138-133: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:20:40Z"
    - latency: 1.951398ms
      message: 'network-check-target-ip-10-0-138-133: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:19:40Z"
    - latency: 1.693779ms
      message: 'network-check-target-ip-10-0-138-133: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:18:40Z"
    - latency: 1.881411ms
      message: 'network-check-target-ip-10-0-138-133: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:17:40Z"
    - latency: 1.814817ms
      message: 'network-check-target-ip-10-0-138-133: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:16:40Z"
    - latency: 1.895375ms
      message: 'network-check-target-ip-10-0-138-133: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:15:40Z"
    - latency: 1.789015ms
      message: 'network-check-target-ip-10-0-138-133: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:14:40Z"
    - latency: 1.808807ms
      message: 'network-check-target-ip-10-0-138-133: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:13:40Z"
    - latency: 2.13436ms
      message: 'network-check-target-ip-10-0-138-133: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:12:40Z"
    - latency: 1.818835ms
      message: 'network-check-target-ip-10-0-138-133: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:11:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T18:38:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-204-to-network-check-target-ip-10-0-142-227
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-204.us-east-2.compute.internal
      uid: e5717a82-68fd-486e-8404-ab65345c02b7
    resourceVersion: "24785"
    uid: e9c458c3-70f3-44da-9482-c554b32100e8
  spec:
    sourcePod: network-check-source-6f78d59f99-jgqpm
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T18:45:40Z"
      message: 'network-check-target-ip-10-0-142-227: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.110934ms
      message: 'network-check-target-ip-10-0-142-227: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:20:40Z"
    - latency: 2.117243ms
      message: 'network-check-target-ip-10-0-142-227: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:19:40Z"
    - latency: 2.200772ms
      message: 'network-check-target-ip-10-0-142-227: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:18:40Z"
    - latency: 2.269149ms
      message: 'network-check-target-ip-10-0-142-227: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:17:40Z"
    - latency: 2.296795ms
      message: 'network-check-target-ip-10-0-142-227: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:16:40Z"
    - latency: 2.16757ms
      message: 'network-check-target-ip-10-0-142-227: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:15:40Z"
    - latency: 2.035046ms
      message: 'network-check-target-ip-10-0-142-227: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:14:40Z"
    - latency: 2.173726ms
      message: 'network-check-target-ip-10-0-142-227: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:13:40Z"
    - latency: 2.107008ms
      message: 'network-check-target-ip-10-0-142-227: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:12:40Z"
    - latency: 1.878035ms
      message: 'network-check-target-ip-10-0-142-227: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:11:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T18:38:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-204-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-204.us-east-2.compute.internal
      uid: e5717a82-68fd-486e-8404-ab65345c02b7
    resourceVersion: "26421"
    uid: 8f513abd-008c-4c6a-88fb-99dd06c458ab
  spec:
    sourcePod: network-check-source-6f78d59f99-jgqpm
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T18:44:40Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 897.747µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:26:40Z"
    - latency: 1.752756ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T19:26:40Z"
    - latency: 767.576µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:25:40Z"
    - latency: 1.749426ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T19:25:40Z"
    - latency: 947.461µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:24:40Z"
    - latency: 2.468854ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T19:24:40Z"
    - latency: 932.934µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:23:40Z"
    - latency: 2.182628ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T19:23:40Z"
    - latency: 1.152632ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:22:40Z"
    - latency: 2.262648ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T19:22:40Z"
kind: List
metadata:
  resourceVersion: ""