apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-05T19:36:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-7-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-7.ec2.internal
      uid: 97db5745-0866-40f8-b7f6-14d856ecb62f
    resourceVersion: "55338"
    uid: c7b0d201-1486-42f0-83e1-073c20bc677d
  spec:
    sourcePod: network-check-source-989f8b8dc-wkkdw
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-05T19:43:44Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 746.394µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T20:11:44Z"
    - latency: 759.215µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T20:10:44Z"
    - latency: 888.513µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T20:09:44Z"
    - latency: 974.209µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T20:08:44Z"
    - latency: 934.536µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T20:07:44Z"
    - latency: 896.896µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T20:06:44Z"
    - latency: 736.544µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T20:05:44Z"
    - latency: 1.37242ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T20:04:44Z"
    - latency: 986.473µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T20:03:44Z"
    - latency: 900.091µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T20:02:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-05T19:36:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-7-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-7.ec2.internal
      uid: 97db5745-0866-40f8-b7f6-14d856ecb62f
    resourceVersion: "56426"
    uid: 1652f5f3-bd23-4986-94de-29230ff25b85
  spec:
    sourcePod: network-check-source-989f8b8dc-wkkdw
    targetEndpoint: a28e5438b167b4cfaaa7ccb5b066a269-b3622ed7c8067e47.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-05T19:42:44Z"
      message: 'load-balancer-api-external: tcp connection to a28e5438b167b4cfaaa7ccb5b066a269-b3622ed7c8067e47.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.872854ms
      message: 'load-balancer-api-external: tcp connection to a28e5438b167b4cfaaa7ccb5b066a269-b3622ed7c8067e47.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T20:12:44Z"
    - latency: 6.981732ms
      message: 'load-balancer-api-external: resolved host name a28e5438b167b4cfaaa7ccb5b066a269-b3622ed7c8067e47.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-05T20:12:44Z"
    - latency: 5.670946ms
      message: 'load-balancer-api-external: tcp connection to a28e5438b167b4cfaaa7ccb5b066a269-b3622ed7c8067e47.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T20:11:44Z"
    - latency: 9.216488ms
      message: 'load-balancer-api-external: resolved host name a28e5438b167b4cfaaa7ccb5b066a269-b3622ed7c8067e47.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-05T20:11:44Z"
    - latency: 5.072968ms
      message: 'load-balancer-api-external: tcp connection to a28e5438b167b4cfaaa7ccb5b066a269-b3622ed7c8067e47.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T20:10:44Z"
    - latency: 7.355292ms
      message: 'load-balancer-api-external: resolved host name a28e5438b167b4cfaaa7ccb5b066a269-b3622ed7c8067e47.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-05T20:10:44Z"
    - latency: 4.522713ms
      message: 'load-balancer-api-external: tcp connection to a28e5438b167b4cfaaa7ccb5b066a269-b3622ed7c8067e47.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T20:09:44Z"
    - latency: 9.078946ms
      message: 'load-balancer-api-external: resolved host name a28e5438b167b4cfaaa7ccb5b066a269-b3622ed7c8067e47.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-05T20:09:44Z"
    - latency: 4.145122ms
      message: 'load-balancer-api-external: tcp connection to a28e5438b167b4cfaaa7ccb5b066a269-b3622ed7c8067e47.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T20:08:44Z"
    - latency: 9.066616ms
      message: 'load-balancer-api-external: resolved host name a28e5438b167b4cfaaa7ccb5b066a269-b3622ed7c8067e47.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-05T20:08:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-05T19:36:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-7-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-7.ec2.internal
      uid: 97db5745-0866-40f8-b7f6-14d856ecb62f
    resourceVersion: "56425"
    uid: 6dfa07e0-34de-4768-a485-42f883c25e4a
  spec:
    sourcePod: network-check-source-989f8b8dc-wkkdw
    targetEndpoint: a28e5438b167b4cfaaa7ccb5b066a269-b3622ed7c8067e47.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-05T19:42:44Z"
      message: 'load-balancer-api-internal: tcp connection to a28e5438b167b4cfaaa7ccb5b066a269-b3622ed7c8067e47.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.894626ms
      message: 'load-balancer-api-internal: tcp connection to a28e5438b167b4cfaaa7ccb5b066a269-b3622ed7c8067e47.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T20:12:44Z"
    - latency: 7.01178ms
      message: 'load-balancer-api-internal: resolved host name a28e5438b167b4cfaaa7ccb5b066a269-b3622ed7c8067e47.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-05T20:12:44Z"
    - latency: 4.805987ms
      message: 'load-balancer-api-internal: tcp connection to a28e5438b167b4cfaaa7ccb5b066a269-b3622ed7c8067e47.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T20:11:44Z"
    - latency: 9.171713ms
      message: 'load-balancer-api-internal: resolved host name a28e5438b167b4cfaaa7ccb5b066a269-b3622ed7c8067e47.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-05T20:11:44Z"
    - latency: 5.165335ms
      message: 'load-balancer-api-internal: tcp connection to a28e5438b167b4cfaaa7ccb5b066a269-b3622ed7c8067e47.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T20:10:44Z"
    - latency: 7.327412ms
      message: 'load-balancer-api-internal: resolved host name a28e5438b167b4cfaaa7ccb5b066a269-b3622ed7c8067e47.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-05T20:10:44Z"
    - latency: 4.213496ms
      message: 'load-balancer-api-internal: tcp connection to a28e5438b167b4cfaaa7ccb5b066a269-b3622ed7c8067e47.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T20:09:44Z"
    - latency: 9.01235ms
      message: 'load-balancer-api-internal: resolved host name a28e5438b167b4cfaaa7ccb5b066a269-b3622ed7c8067e47.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-05T20:09:44Z"
    - latency: 4.129956ms
      message: 'load-balancer-api-internal: tcp connection to a28e5438b167b4cfaaa7ccb5b066a269-b3622ed7c8067e47.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T20:08:44Z"
    - latency: 9.034037ms
      message: 'load-balancer-api-internal: resolved host name a28e5438b167b4cfaaa7ccb5b066a269-b3622ed7c8067e47.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-05T20:08:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-05T19:36:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-7-to-network-check-target-ip-10-0-133-7
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-7.ec2.internal
      uid: 97db5745-0866-40f8-b7f6-14d856ecb62f
    resourceVersion: "55336"
    uid: e0bedef0-9d4f-4a08-98c5-1424a43cea27
  spec:
    sourcePod: network-check-source-989f8b8dc-wkkdw
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-05T19:43:44Z"
      message: 'network-check-target-ip-10-0-133-7: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 937.336µs
      message: 'network-check-target-ip-10-0-133-7: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T20:11:44Z"
    - latency: 807.642µs
      message: 'network-check-target-ip-10-0-133-7: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T20:10:44Z"
    - latency: 896.537µs
      message: 'network-check-target-ip-10-0-133-7: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T20:09:44Z"
    - latency: 1.2187ms
      message: 'network-check-target-ip-10-0-133-7: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T20:08:44Z"
    - latency: 1.291647ms
      message: 'network-check-target-ip-10-0-133-7: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T20:07:44Z"
    - latency: 1.080366ms
      message: 'network-check-target-ip-10-0-133-7: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T20:06:44Z"
    - latency: 1.377898ms
      message: 'network-check-target-ip-10-0-133-7: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T20:05:44Z"
    - latency: 1.253298ms
      message: 'network-check-target-ip-10-0-133-7: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T20:04:44Z"
    - latency: 1.212713ms
      message: 'network-check-target-ip-10-0-133-7: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T20:03:44Z"
    - latency: 813.967µs
      message: 'network-check-target-ip-10-0-133-7: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T20:02:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-05T19:36:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-7-to-network-check-target-ip-10-0-134-29
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-7.ec2.internal
      uid: 97db5745-0866-40f8-b7f6-14d856ecb62f
    resourceVersion: "55335"
    uid: c5f2b053-0c7e-4da8-9f0c-312f7be820b9
  spec:
    sourcePod: network-check-source-989f8b8dc-wkkdw
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-05T19:43:44Z"
      message: 'network-check-target-ip-10-0-134-29: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.237538ms
      message: 'network-check-target-ip-10-0-134-29: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T20:11:44Z"
    - latency: 1.782429ms
      message: 'network-check-target-ip-10-0-134-29: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T20:10:44Z"
    - latency: 1.968936ms
      message: 'network-check-target-ip-10-0-134-29: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T20:09:44Z"
    - latency: 2.360444ms
      message: 'network-check-target-ip-10-0-134-29: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T20:08:44Z"
    - latency: 2.105932ms
      message: 'network-check-target-ip-10-0-134-29: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T20:07:44Z"
    - latency: 2.245848ms
      message: 'network-check-target-ip-10-0-134-29: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T20:06:44Z"
    - latency: 2.069241ms
      message: 'network-check-target-ip-10-0-134-29: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T20:05:44Z"
    - latency: 2.470364ms
      message: 'network-check-target-ip-10-0-134-29: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T20:04:44Z"
    - latency: 2.402241ms
      message: 'network-check-target-ip-10-0-134-29: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T20:03:44Z"
    - latency: 2.361139ms
      message: 'network-check-target-ip-10-0-134-29: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T20:02:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-05T19:36:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-7-to-network-check-target-ip-10-0-138-140
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-7.ec2.internal
      uid: 97db5745-0866-40f8-b7f6-14d856ecb62f
    resourceVersion: "55337"
    uid: fb7fc0c8-a8c1-4cbd-8b1c-6ce042597b74
  spec:
    sourcePod: network-check-source-989f8b8dc-wkkdw
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-05T19:43:44Z"
      message: 'network-check-target-ip-10-0-138-140: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.798096ms
      message: 'network-check-target-ip-10-0-138-140: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T20:11:44Z"
    - latency: 1.648337ms
      message: 'network-check-target-ip-10-0-138-140: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T20:10:44Z"
    - latency: 1.533595ms
      message: 'network-check-target-ip-10-0-138-140: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T20:09:44Z"
    - latency: 1.763848ms
      message: 'network-check-target-ip-10-0-138-140: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T20:08:44Z"
    - latency: 1.717819ms
      message: 'network-check-target-ip-10-0-138-140: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T20:07:44Z"
    - latency: 2.026754ms
      message: 'network-check-target-ip-10-0-138-140: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T20:06:44Z"
    - latency: 2.14112ms
      message: 'network-check-target-ip-10-0-138-140: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T20:05:44Z"
    - latency: 2.258381ms
      message: 'network-check-target-ip-10-0-138-140: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T20:04:44Z"
    - latency: 2.152814ms
      message: 'network-check-target-ip-10-0-138-140: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T20:03:44Z"
    - latency: 1.989454ms
      message: 'network-check-target-ip-10-0-138-140: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T20:02:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-05T19:36:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-7-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-7.ec2.internal
      uid: 97db5745-0866-40f8-b7f6-14d856ecb62f
    resourceVersion: "56424"
    uid: ed24acb5-7dc7-4b53-a903-3311fd10c8e1
  spec:
    sourcePod: network-check-source-989f8b8dc-wkkdw
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-05T19:42:44Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.099157ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T20:12:44Z"
    - latency: 1.852169ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-05T20:12:44Z"
    - latency: 926.726µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T20:11:44Z"
    - latency: 2.324432ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-05T20:11:44Z"
    - latency: 919.828µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T20:10:44Z"
    - latency: 1.935148ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-05T20:10:44Z"
    - latency: 887.09µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T20:09:44Z"
    - latency: 2.913364ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-05T20:09:44Z"
    - latency: 960.97µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T20:08:44Z"
    - latency: 1.965223ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-05T20:08:44Z"
kind: List
metadata:
  resourceVersion: ""