apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T17:18:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-219-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-219.us-west-2.compute.internal
      uid: 98f10cbf-7a24-44eb-b6b1-0f0cc5083e67
    resourceVersion: "138279"
    uid: 826a5cb6-5855-44f1-955d-84ff2d6ce3c7
  spec:
    sourcePod: network-check-source-6f78d59f99-lb8nj
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T17:25:07Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.096346ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T19:10:07Z"
    - latency: 1.039704ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T19:09:07Z"
    - latency: 1.418783ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T19:08:07Z"
    - latency: 1.306195ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T19:07:07Z"
    - latency: 1.086275ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T19:06:07Z"
    - latency: 1.072904ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T19:05:07Z"
    - latency: 1.502919ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T19:04:07Z"
    - latency: 1.047546ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T19:03:07Z"
    - latency: 1.26788ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T19:02:07Z"
    - latency: 1.335843ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T19:01:07Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T17:18:07Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-219-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-219.us-west-2.compute.internal
      uid: 98f10cbf-7a24-44eb-b6b1-0f0cc5083e67
    resourceVersion: "139797"
    uid: d10c4340-59f7-4df5-b49b-ef35f06bfcaf
  spec:
    sourcePod: network-check-source-6f78d59f99-lb8nj
    targetEndpoint: ae4f21c5985754fdab24e2f2e3e09060-2a5fa75794b3f366.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T17:24:07Z"
      message: 'load-balancer-api-external: tcp connection to ae4f21c5985754fdab24e2f2e3e09060-2a5fa75794b3f366.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 55.669192ms
      message: 'load-balancer-api-external: tcp connection to ae4f21c5985754fdab24e2f2e3e09060-2a5fa75794b3f366.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T19:12:07Z"
    - latency: 7.151272ms
      message: 'load-balancer-api-external: resolved host name ae4f21c5985754fdab24e2f2e3e09060-2a5fa75794b3f366.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T19:12:07Z"
    - latency: 55.701379ms
      message: 'load-balancer-api-external: tcp connection to ae4f21c5985754fdab24e2f2e3e09060-2a5fa75794b3f366.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T19:11:07Z"
    - latency: 7.287716ms
      message: 'load-balancer-api-external: resolved host name ae4f21c5985754fdab24e2f2e3e09060-2a5fa75794b3f366.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T19:11:07Z"
    - latency: 56.291775ms
      message: 'load-balancer-api-external: tcp connection to ae4f21c5985754fdab24e2f2e3e09060-2a5fa75794b3f366.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T19:10:07Z"
    - latency: 6.974734ms
      message: 'load-balancer-api-external: resolved host name ae4f21c5985754fdab24e2f2e3e09060-2a5fa75794b3f366.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T19:10:07Z"
    - latency: 57.610281ms
      message: 'load-balancer-api-external: tcp connection to ae4f21c5985754fdab24e2f2e3e09060-2a5fa75794b3f366.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T19:09:07Z"
    - latency: 7.029508ms
      message: 'load-balancer-api-external: resolved host name ae4f21c5985754fdab24e2f2e3e09060-2a5fa75794b3f366.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T19:09:07Z"
    - latency: 63.173345ms
      message: 'load-balancer-api-external: tcp connection to ae4f21c5985754fdab24e2f2e3e09060-2a5fa75794b3f366.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T19:08:07Z"
    - latency: 13.175505ms
      message: 'load-balancer-api-external: resolved host name ae4f21c5985754fdab24e2f2e3e09060-2a5fa75794b3f366.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T19:08:07Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T17:18:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-219-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-219.us-west-2.compute.internal
      uid: 98f10cbf-7a24-44eb-b6b1-0f0cc5083e67
    resourceVersion: "139796"
    uid: 19e4983c-d4b6-4f54-bbe3-69d9e30666dd
  spec:
    sourcePod: network-check-source-6f78d59f99-lb8nj
    targetEndpoint: ae4f21c5985754fdab24e2f2e3e09060-2a5fa75794b3f366.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T17:24:07Z"
      message: 'load-balancer-api-internal: tcp connection to ae4f21c5985754fdab24e2f2e3e09060-2a5fa75794b3f366.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 52.17659ms
      message: 'load-balancer-api-internal: tcp connection to ae4f21c5985754fdab24e2f2e3e09060-2a5fa75794b3f366.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T19:12:07Z"
    - latency: 7.173676ms
      message: 'load-balancer-api-internal: resolved host name ae4f21c5985754fdab24e2f2e3e09060-2a5fa75794b3f366.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T19:12:07Z"
    - latency: 54.778226ms
      message: 'load-balancer-api-internal: tcp connection to ae4f21c5985754fdab24e2f2e3e09060-2a5fa75794b3f366.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T19:11:07Z"
    - latency: 7.315067ms
      message: 'load-balancer-api-internal: resolved host name ae4f21c5985754fdab24e2f2e3e09060-2a5fa75794b3f366.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T19:11:07Z"
    - latency: 56.220854ms
      message: 'load-balancer-api-internal: tcp connection to ae4f21c5985754fdab24e2f2e3e09060-2a5fa75794b3f366.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T19:10:07Z"
    - latency: 7.031051ms
      message: 'load-balancer-api-internal: resolved host name ae4f21c5985754fdab24e2f2e3e09060-2a5fa75794b3f366.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T19:10:07Z"
    - latency: 57.989452ms
      message: 'load-balancer-api-internal: tcp connection to ae4f21c5985754fdab24e2f2e3e09060-2a5fa75794b3f366.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T19:09:07Z"
    - latency: 7.067073ms
      message: 'load-balancer-api-internal: resolved host name ae4f21c5985754fdab24e2f2e3e09060-2a5fa75794b3f366.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T19:09:07Z"
    - latency: 63.115843ms
      message: 'load-balancer-api-internal: tcp connection to ae4f21c5985754fdab24e2f2e3e09060-2a5fa75794b3f366.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T19:08:07Z"
    - latency: 13.259948ms
      message: 'load-balancer-api-internal: resolved host name ae4f21c5985754fdab24e2f2e3e09060-2a5fa75794b3f366.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T19:08:07Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T17:18:15Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-219-to-network-check-target-ip-10-0-129-76
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-219.us-west-2.compute.internal
      uid: 98f10cbf-7a24-44eb-b6b1-0f0cc5083e67
    resourceVersion: "138384"
    uid: 0be25a7a-9808-4181-91dc-861294d024c2
  spec:
    sourcePod: network-check-source-6f78d59f99-lb8nj
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T17:25:15Z"
      message: 'network-check-target-ip-10-0-129-76: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.369269ms
      message: 'network-check-target-ip-10-0-129-76: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T19:10:15Z"
    - latency: 2.349124ms
      message: 'network-check-target-ip-10-0-129-76: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T19:09:15Z"
    - latency: 1.248723ms
      message: 'network-check-target-ip-10-0-129-76: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T19:08:15Z"
    - latency: 2.526927ms
      message: 'network-check-target-ip-10-0-129-76: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T19:07:15Z"
    - latency: 2.651415ms
      message: 'network-check-target-ip-10-0-129-76: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T19:06:15Z"
    - latency: 2.640968ms
      message: 'network-check-target-ip-10-0-129-76: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T19:05:15Z"
    - latency: 2.255562ms
      message: 'network-check-target-ip-10-0-129-76: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T19:04:15Z"
    - latency: 2.463007ms
      message: 'network-check-target-ip-10-0-129-76: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T19:03:15Z"
    - latency: 2.619291ms
      message: 'network-check-target-ip-10-0-129-76: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T19:02:15Z"
    - latency: 1.119466ms
      message: 'network-check-target-ip-10-0-129-76: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T19:01:15Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T17:18:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-219-to-network-check-target-ip-10-0-137-219
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-219.us-west-2.compute.internal
      uid: 98f10cbf-7a24-44eb-b6b1-0f0cc5083e67
    resourceVersion: "138272"
    uid: e7bbe2ad-3f15-4923-ac51-e0973eac1964
  spec:
    sourcePod: network-check-source-6f78d59f99-lb8nj
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T17:25:07Z"
      message: 'network-check-target-ip-10-0-137-219: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.468285ms
      message: 'network-check-target-ip-10-0-137-219: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T19:10:07Z"
    - latency: 1.267648ms
      message: 'network-check-target-ip-10-0-137-219: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T19:09:07Z"
    - latency: 1.337589ms
      message: 'network-check-target-ip-10-0-137-219: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T19:08:07Z"
    - latency: 1.104659ms
      message: 'network-check-target-ip-10-0-137-219: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T19:07:07Z"
    - latency: 1.108091ms
      message: 'network-check-target-ip-10-0-137-219: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T19:06:07Z"
    - latency: 1.216413ms
      message: 'network-check-target-ip-10-0-137-219: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T19:05:07Z"
    - latency: 1.439783ms
      message: 'network-check-target-ip-10-0-137-219: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T19:04:07Z"
    - latency: 1.427924ms
      message: 'network-check-target-ip-10-0-137-219: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T19:03:07Z"
    - latency: 1.645247ms
      message: 'network-check-target-ip-10-0-137-219: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T19:02:07Z"
    - latency: 1.530218ms
      message: 'network-check-target-ip-10-0-137-219: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T19:01:07Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T17:18:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-219-to-network-check-target-ip-10-0-143-117
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-219.us-west-2.compute.internal
      uid: 98f10cbf-7a24-44eb-b6b1-0f0cc5083e67
    resourceVersion: "138418"
    uid: 4398d22b-f560-4f2a-9492-9a511f59c9fa
  spec:
    sourcePod: network-check-source-6f78d59f99-lb8nj
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T17:25:18Z"
      message: 'network-check-target-ip-10-0-143-117: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.609787ms
      message: 'network-check-target-ip-10-0-143-117: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T19:10:18Z"
    - latency: 2.95355ms
      message: 'network-check-target-ip-10-0-143-117: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T19:09:18Z"
    - latency: 2.554414ms
      message: 'network-check-target-ip-10-0-143-117: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T19:08:18Z"
    - latency: 2.764612ms
      message: 'network-check-target-ip-10-0-143-117: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T19:07:18Z"
    - latency: 2.462611ms
      message: 'network-check-target-ip-10-0-143-117: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T19:06:18Z"
    - latency: 2.541217ms
      message: 'network-check-target-ip-10-0-143-117: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T19:05:18Z"
    - latency: 2.449849ms
      message: 'network-check-target-ip-10-0-143-117: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T19:04:18Z"
    - latency: 2.239966ms
      message: 'network-check-target-ip-10-0-143-117: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T19:03:18Z"
    - latency: 2.315014ms
      message: 'network-check-target-ip-10-0-143-117: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T19:02:18Z"
    - latency: 2.251404ms
      message: 'network-check-target-ip-10-0-143-117: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T19:01:18Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T17:18:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-219-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-219.us-west-2.compute.internal
      uid: 98f10cbf-7a24-44eb-b6b1-0f0cc5083e67
    resourceVersion: "139794"
    uid: 1d1a2896-db5c-45df-992c-8d0aa19b3e05
  spec:
    sourcePod: network-check-source-6f78d59f99-lb8nj
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T17:24:07Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.006775ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T19:12:07Z"
    - latency: 1.791778ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T19:12:07Z"
    - latency: 2.754489ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T19:11:07Z"
    - latency: 2.654454ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T19:11:07Z"
    - latency: 2.327956ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T19:10:07Z"
    - latency: 1.929796ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T19:10:07Z"
    - latency: 2.089318ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T19:09:07Z"
    - latency: 1.921477ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T19:09:07Z"
    - latency: 5.126257ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T19:08:07Z"
    - latency: 2.711499ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T19:08:07Z"
kind: List
metadata:
  resourceVersion: ""