apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T22:36:41Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-200-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-200.ec2.internal
      uid: 91f7b7b5-10ea-4790-b227-b225c35e743c
    resourceVersion: "48380"
    uid: 4f7afd3a-1385-48a6-a55a-47cc8629e597
  spec:
    sourcePod: network-check-source-989f8b8dc-nc496
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T22:43:42Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.323969ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T23:04:42Z"
    - latency: 1.100868ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T23:03:42Z"
    - latency: 1.060239ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T23:02:42Z"
    - latency: 1.156561ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T23:01:42Z"
    - latency: 1.237377ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T23:00:42Z"
    - latency: 1.024989ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T22:59:42Z"
    - latency: 1.255279ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T22:58:42Z"
    - latency: 1.125775ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T22:57:42Z"
    - latency: 862.019µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T22:56:42Z"
    - latency: 1.075097ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T22:55:42Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T22:36:41Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-200-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-200.ec2.internal
      uid: 91f7b7b5-10ea-4790-b227-b225c35e743c
    resourceVersion: "50815"
    uid: de5d5a2b-fdca-43e6-a0f1-d7b8cc86b678
  spec:
    sourcePod: network-check-source-989f8b8dc-nc496
    targetEndpoint: a0ee1c97603fe4291a1f5e36af7608b8-7d3b0ce4f110cfb5.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T22:42:42Z"
      message: 'load-balancer-api-external: tcp connection to a0ee1c97603fe4291a1f5e36af7608b8-7d3b0ce4f110cfb5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.762929ms
      message: 'load-balancer-api-external: tcp connection to a0ee1c97603fe4291a1f5e36af7608b8-7d3b0ce4f110cfb5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T23:06:42Z"
    - latency: 6.943357ms
      message: 'load-balancer-api-external: resolved host name a0ee1c97603fe4291a1f5e36af7608b8-7d3b0ce4f110cfb5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T23:06:42Z"
    - latency: 4.559665ms
      message: 'load-balancer-api-external: tcp connection to a0ee1c97603fe4291a1f5e36af7608b8-7d3b0ce4f110cfb5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T23:05:42Z"
    - latency: 7.660068ms
      message: 'load-balancer-api-external: resolved host name a0ee1c97603fe4291a1f5e36af7608b8-7d3b0ce4f110cfb5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T23:05:42Z"
    - latency: 3.666568ms
      message: 'load-balancer-api-external: tcp connection to a0ee1c97603fe4291a1f5e36af7608b8-7d3b0ce4f110cfb5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T23:04:42Z"
    - latency: 6.872528ms
      message: 'load-balancer-api-external: resolved host name a0ee1c97603fe4291a1f5e36af7608b8-7d3b0ce4f110cfb5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T23:04:42Z"
    - latency: 3.517937ms
      message: 'load-balancer-api-external: tcp connection to a0ee1c97603fe4291a1f5e36af7608b8-7d3b0ce4f110cfb5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T23:03:42Z"
    - latency: 7.484864ms
      message: 'load-balancer-api-external: resolved host name a0ee1c97603fe4291a1f5e36af7608b8-7d3b0ce4f110cfb5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T23:03:42Z"
    - latency: 6.697774ms
      message: 'load-balancer-api-external: tcp connection to a0ee1c97603fe4291a1f5e36af7608b8-7d3b0ce4f110cfb5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T23:02:42Z"
    - latency: 8.055961ms
      message: 'load-balancer-api-external: resolved host name a0ee1c97603fe4291a1f5e36af7608b8-7d3b0ce4f110cfb5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T23:02:42Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T22:36:41Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-200-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-200.ec2.internal
      uid: 91f7b7b5-10ea-4790-b227-b225c35e743c
    resourceVersion: "50816"
    uid: c767b147-c909-416d-af0f-ef4c010214f6
  spec:
    sourcePod: network-check-source-989f8b8dc-nc496
    targetEndpoint: a0ee1c97603fe4291a1f5e36af7608b8-7d3b0ce4f110cfb5.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T22:42:42Z"
      message: 'load-balancer-api-internal: tcp connection to a0ee1c97603fe4291a1f5e36af7608b8-7d3b0ce4f110cfb5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.821817ms
      message: 'load-balancer-api-internal: tcp connection to a0ee1c97603fe4291a1f5e36af7608b8-7d3b0ce4f110cfb5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T23:06:42Z"
    - latency: 6.868329ms
      message: 'load-balancer-api-internal: resolved host name a0ee1c97603fe4291a1f5e36af7608b8-7d3b0ce4f110cfb5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T23:06:42Z"
    - latency: 4.640097ms
      message: 'load-balancer-api-internal: tcp connection to a0ee1c97603fe4291a1f5e36af7608b8-7d3b0ce4f110cfb5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T23:05:42Z"
    - latency: 7.600558ms
      message: 'load-balancer-api-internal: resolved host name a0ee1c97603fe4291a1f5e36af7608b8-7d3b0ce4f110cfb5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T23:05:42Z"
    - latency: 4.946126ms
      message: 'load-balancer-api-internal: tcp connection to a0ee1c97603fe4291a1f5e36af7608b8-7d3b0ce4f110cfb5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T23:04:42Z"
    - latency: 6.775597ms
      message: 'load-balancer-api-internal: resolved host name a0ee1c97603fe4291a1f5e36af7608b8-7d3b0ce4f110cfb5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T23:04:42Z"
    - latency: 4.899796ms
      message: 'load-balancer-api-internal: tcp connection to a0ee1c97603fe4291a1f5e36af7608b8-7d3b0ce4f110cfb5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T23:03:42Z"
    - latency: 7.431556ms
      message: 'load-balancer-api-internal: resolved host name a0ee1c97603fe4291a1f5e36af7608b8-7d3b0ce4f110cfb5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T23:03:42Z"
    - latency: 5.633177ms
      message: 'load-balancer-api-internal: tcp connection to a0ee1c97603fe4291a1f5e36af7608b8-7d3b0ce4f110cfb5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T23:02:42Z"
    - latency: 7.978323ms
      message: 'load-balancer-api-internal: resolved host name a0ee1c97603fe4291a1f5e36af7608b8-7d3b0ce4f110cfb5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T23:02:42Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T22:36:41Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-200-to-network-check-target-ip-10-0-131-200
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-200.ec2.internal
      uid: 91f7b7b5-10ea-4790-b227-b225c35e743c
    resourceVersion: "48377"
    uid: e8d9adb3-f958-40d7-af48-8de3b966884d
  spec:
    sourcePod: network-check-source-989f8b8dc-nc496
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T22:43:42Z"
      message: 'network-check-target-ip-10-0-131-200: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 945.513µs
      message: 'network-check-target-ip-10-0-131-200: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T23:04:42Z"
    - latency: 1.038848ms
      message: 'network-check-target-ip-10-0-131-200: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T23:03:42Z"
    - latency: 900.251µs
      message: 'network-check-target-ip-10-0-131-200: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T23:02:42Z"
    - latency: 1.131039ms
      message: 'network-check-target-ip-10-0-131-200: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T23:01:42Z"
    - latency: 966.785µs
      message: 'network-check-target-ip-10-0-131-200: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T23:00:42Z"
    - latency: 1.617067ms
      message: 'network-check-target-ip-10-0-131-200: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T22:59:42Z"
    - latency: 915.729µs
      message: 'network-check-target-ip-10-0-131-200: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T22:58:42Z"
    - latency: 904.472µs
      message: 'network-check-target-ip-10-0-131-200: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T22:57:42Z"
    - latency: 1.47739ms
      message: 'network-check-target-ip-10-0-131-200: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T22:56:42Z"
    - latency: 1.006731ms
      message: 'network-check-target-ip-10-0-131-200: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T22:55:42Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T22:36:41Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-200-to-network-check-target-ip-10-0-132-195
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-200.ec2.internal
      uid: 91f7b7b5-10ea-4790-b227-b225c35e743c
    resourceVersion: "48378"
    uid: a556244e-e189-4163-bc5a-f7674ed13fcc
  spec:
    sourcePod: network-check-source-989f8b8dc-nc496
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T22:43:42Z"
      message: 'network-check-target-ip-10-0-132-195: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.850575ms
      message: 'network-check-target-ip-10-0-132-195: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T23:04:42Z"
    - latency: 1.872372ms
      message: 'network-check-target-ip-10-0-132-195: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T23:03:42Z"
    - latency: 1.895639ms
      message: 'network-check-target-ip-10-0-132-195: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T23:02:42Z"
    - latency: 2.073269ms
      message: 'network-check-target-ip-10-0-132-195: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T23:01:42Z"
    - latency: 1.84426ms
      message: 'network-check-target-ip-10-0-132-195: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T23:00:42Z"
    - latency: 2.391395ms
      message: 'network-check-target-ip-10-0-132-195: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T22:59:42Z"
    - latency: 1.905494ms
      message: 'network-check-target-ip-10-0-132-195: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T22:58:42Z"
    - latency: 2.012688ms
      message: 'network-check-target-ip-10-0-132-195: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T22:57:42Z"
    - latency: 2.205761ms
      message: 'network-check-target-ip-10-0-132-195: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T22:56:42Z"
    - latency: 1.863751ms
      message: 'network-check-target-ip-10-0-132-195: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T22:55:42Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T22:36:41Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-200-to-network-check-target-ip-10-0-136-6
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-200.ec2.internal
      uid: 91f7b7b5-10ea-4790-b227-b225c35e743c
    resourceVersion: "48379"
    uid: f13ae111-f4aa-4c39-bc25-e6949618bf8d
  spec:
    sourcePod: network-check-source-989f8b8dc-nc496
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T22:43:42Z"
      message: 'network-check-target-ip-10-0-136-6: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.295409ms
      message: 'network-check-target-ip-10-0-136-6: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T23:04:42Z"
    - latency: 2.211229ms
      message: 'network-check-target-ip-10-0-136-6: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T23:03:42Z"
    - latency: 2.337928ms
      message: 'network-check-target-ip-10-0-136-6: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T23:02:42Z"
    - latency: 2.464938ms
      message: 'network-check-target-ip-10-0-136-6: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T23:01:42Z"
    - latency: 2.457354ms
      message: 'network-check-target-ip-10-0-136-6: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T23:00:42Z"
    - latency: 2.545379ms
      message: 'network-check-target-ip-10-0-136-6: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T22:59:42Z"
    - latency: 2.349866ms
      message: 'network-check-target-ip-10-0-136-6: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T22:58:42Z"
    - latency: 2.245932ms
      message: 'network-check-target-ip-10-0-136-6: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T22:57:42Z"
    - latency: 2.616719ms
      message: 'network-check-target-ip-10-0-136-6: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T22:56:42Z"
    - latency: 2.048032ms
      message: 'network-check-target-ip-10-0-136-6: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T22:55:42Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T22:36:41Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-200-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-200.ec2.internal
      uid: 91f7b7b5-10ea-4790-b227-b225c35e743c
    resourceVersion: "50814"
    uid: aa43cc3c-342e-4761-af32-447ee69cde47
  spec:
    sourcePod: network-check-source-989f8b8dc-nc496
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T22:42:42Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 977.113µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T23:06:42Z"
    - latency: 1.949369ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T23:06:42Z"
    - latency: 944.964µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T23:05:42Z"
    - latency: 1.942122ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T23:05:42Z"
    - latency: 922.467µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T23:04:42Z"
    - latency: 2.244258ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T23:04:42Z"
    - latency: 897.175µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T23:03:42Z"
    - latency: 1.854895ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T23:03:42Z"
    - latency: 914.409µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T23:02:42Z"
    - latency: 1.679765ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T23:02:42Z"
kind: List
metadata:
  resourceVersion: ""