apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T03:22:14Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-95-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-95.ec2.internal
      uid: ff67601a-aae4-4d67-8f18-45c4cd8a2625
    resourceVersion: "37751"
    uid: d88f36fc-0d7e-49a1-96d6-b0faceacbd3d
  spec:
    sourcePod: network-check-source-7d88cb55d8-zt8zt
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T03:29:15Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 794.178µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T03:43:15Z"
    - latency: 899.947µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T03:42:15Z"
    - latency: 1.208633ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T03:41:15Z"
    - latency: 1.347595ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T03:40:15Z"
    - latency: 1.136216ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T03:39:15Z"
    - latency: 1.762201ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T03:38:15Z"
    - latency: 984.641µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T03:37:15Z"
    - latency: 894.163µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T03:36:15Z"
    - latency: 1.218434ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T03:35:15Z"
    - latency: 1.349621ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T03:34:15Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T03:22:14Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-95-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-95.ec2.internal
      uid: ff67601a-aae4-4d67-8f18-45c4cd8a2625
    resourceVersion: "34393"
    uid: b69f7988-2174-4e1b-8c28-f6830a1f6f0a
  spec:
    sourcePod: network-check-source-7d88cb55d8-zt8zt
    targetEndpoint: aa5b5c10d238c4eac9b5bf8e0365e2cc-cc5dcb10d0192483.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T03:28:15Z"
      message: 'load-balancer-api-external: tcp connection to aa5b5c10d238c4eac9b5bf8e0365e2cc-cc5dcb10d0192483.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.381999ms
      message: 'load-balancer-api-external: tcp connection to aa5b5c10d238c4eac9b5bf8e0365e2cc-cc5dcb10d0192483.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T03:40:15Z"
    - latency: 7.240947ms
      message: 'load-balancer-api-external: resolved host name aa5b5c10d238c4eac9b5bf8e0365e2cc-cc5dcb10d0192483.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T03:40:15Z"
    - latency: 3.699841ms
      message: 'load-balancer-api-external: tcp connection to aa5b5c10d238c4eac9b5bf8e0365e2cc-cc5dcb10d0192483.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T03:39:15Z"
    - latency: 8.729093ms
      message: 'load-balancer-api-external: resolved host name aa5b5c10d238c4eac9b5bf8e0365e2cc-cc5dcb10d0192483.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T03:39:15Z"
    - latency: 4.865704ms
      message: 'load-balancer-api-external: tcp connection to aa5b5c10d238c4eac9b5bf8e0365e2cc-cc5dcb10d0192483.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T03:38:15Z"
    - latency: 7.43577ms
      message: 'load-balancer-api-external: resolved host name aa5b5c10d238c4eac9b5bf8e0365e2cc-cc5dcb10d0192483.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T03:38:15Z"
    - latency: 5.004636ms
      message: 'load-balancer-api-external: tcp connection to aa5b5c10d238c4eac9b5bf8e0365e2cc-cc5dcb10d0192483.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T03:37:15Z"
    - latency: 7.052379ms
      message: 'load-balancer-api-external: resolved host name aa5b5c10d238c4eac9b5bf8e0365e2cc-cc5dcb10d0192483.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T03:37:15Z"
    - latency: 6.646141ms
      message: 'load-balancer-api-external: tcp connection to aa5b5c10d238c4eac9b5bf8e0365e2cc-cc5dcb10d0192483.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T03:36:15Z"
    - latency: 9.198254ms
      message: 'load-balancer-api-external: resolved host name aa5b5c10d238c4eac9b5bf8e0365e2cc-cc5dcb10d0192483.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T03:36:15Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T03:22:14Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-95-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-95.ec2.internal
      uid: ff67601a-aae4-4d67-8f18-45c4cd8a2625
    resourceVersion: "34392"
    uid: b28211fc-7f2a-4f18-af59-74429e4a0a5e
  spec:
    sourcePod: network-check-source-7d88cb55d8-zt8zt
    targetEndpoint: aa5b5c10d238c4eac9b5bf8e0365e2cc-cc5dcb10d0192483.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T03:28:15Z"
      message: 'load-balancer-api-internal: tcp connection to aa5b5c10d238c4eac9b5bf8e0365e2cc-cc5dcb10d0192483.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.394411ms
      message: 'load-balancer-api-internal: tcp connection to aa5b5c10d238c4eac9b5bf8e0365e2cc-cc5dcb10d0192483.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T03:40:15Z"
    - latency: 7.327169ms
      message: 'load-balancer-api-internal: resolved host name aa5b5c10d238c4eac9b5bf8e0365e2cc-cc5dcb10d0192483.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T03:40:15Z"
    - latency: 3.705846ms
      message: 'load-balancer-api-internal: tcp connection to aa5b5c10d238c4eac9b5bf8e0365e2cc-cc5dcb10d0192483.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T03:39:15Z"
    - latency: 8.787402ms
      message: 'load-balancer-api-internal: resolved host name aa5b5c10d238c4eac9b5bf8e0365e2cc-cc5dcb10d0192483.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T03:39:15Z"
    - latency: 4.793248ms
      message: 'load-balancer-api-internal: tcp connection to aa5b5c10d238c4eac9b5bf8e0365e2cc-cc5dcb10d0192483.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T03:38:15Z"
    - latency: 7.523774ms
      message: 'load-balancer-api-internal: resolved host name aa5b5c10d238c4eac9b5bf8e0365e2cc-cc5dcb10d0192483.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T03:38:15Z"
    - latency: 5.461943ms
      message: 'load-balancer-api-internal: tcp connection to aa5b5c10d238c4eac9b5bf8e0365e2cc-cc5dcb10d0192483.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T03:37:15Z"
    - latency: 7.016349ms
      message: 'load-balancer-api-internal: resolved host name aa5b5c10d238c4eac9b5bf8e0365e2cc-cc5dcb10d0192483.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T03:37:15Z"
    - latency: 6.545521ms
      message: 'load-balancer-api-internal: tcp connection to aa5b5c10d238c4eac9b5bf8e0365e2cc-cc5dcb10d0192483.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T03:36:15Z"
    - latency: 9.249982ms
      message: 'load-balancer-api-internal: resolved host name aa5b5c10d238c4eac9b5bf8e0365e2cc-cc5dcb10d0192483.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T03:36:15Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T03:22:14Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-95-to-network-check-target-ip-10-0-134-231
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-95.ec2.internal
      uid: ff67601a-aae4-4d67-8f18-45c4cd8a2625
    resourceVersion: "37750"
    uid: 56de12f5-92d7-42dc-8ad1-e96e776dd50c
  spec:
    sourcePod: network-check-source-7d88cb55d8-zt8zt
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T03:29:15Z"
      message: 'network-check-target-ip-10-0-134-231: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.933915ms
      message: 'network-check-target-ip-10-0-134-231: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T03:43:15Z"
    - latency: 2.233412ms
      message: 'network-check-target-ip-10-0-134-231: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T03:42:15Z"
    - latency: 2.344502ms
      message: 'network-check-target-ip-10-0-134-231: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T03:41:15Z"
    - latency: 2.382514ms
      message: 'network-check-target-ip-10-0-134-231: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T03:40:15Z"
    - latency: 2.306901ms
      message: 'network-check-target-ip-10-0-134-231: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T03:39:15Z"
    - latency: 2.410225ms
      message: 'network-check-target-ip-10-0-134-231: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T03:38:15Z"
    - latency: 2.237145ms
      message: 'network-check-target-ip-10-0-134-231: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T03:37:15Z"
    - latency: 2.325419ms
      message: 'network-check-target-ip-10-0-134-231: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T03:36:15Z"
    - latency: 1.947856ms
      message: 'network-check-target-ip-10-0-134-231: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T03:35:15Z"
    - latency: 2.23728ms
      message: 'network-check-target-ip-10-0-134-231: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T03:34:15Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T03:22:14Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-95-to-network-check-target-ip-10-0-139-134
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-95.ec2.internal
      uid: ff67601a-aae4-4d67-8f18-45c4cd8a2625
    resourceVersion: "37749"
    uid: 2502a3bd-c339-4cc9-a6f3-361fa3cbab3f
  spec:
    sourcePod: network-check-source-7d88cb55d8-zt8zt
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T03:29:15Z"
      message: 'network-check-target-ip-10-0-139-134: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.916815ms
      message: 'network-check-target-ip-10-0-139-134: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T03:43:15Z"
    - latency: 1.654548ms
      message: 'network-check-target-ip-10-0-139-134: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T03:42:15Z"
    - latency: 1.814009ms
      message: 'network-check-target-ip-10-0-139-134: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T03:41:15Z"
    - latency: 1.965422ms
      message: 'network-check-target-ip-10-0-139-134: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T03:40:15Z"
    - latency: 2.000798ms
      message: 'network-check-target-ip-10-0-139-134: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T03:39:15Z"
    - latency: 2.040518ms
      message: 'network-check-target-ip-10-0-139-134: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T03:38:15Z"
    - latency: 1.926937ms
      message: 'network-check-target-ip-10-0-139-134: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T03:37:15Z"
    - latency: 1.725477ms
      message: 'network-check-target-ip-10-0-139-134: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T03:36:15Z"
    - latency: 2.036278ms
      message: 'network-check-target-ip-10-0-139-134: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T03:35:15Z"
    - latency: 1.806477ms
      message: 'network-check-target-ip-10-0-139-134: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T03:34:15Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T03:22:14Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-95-to-network-check-target-ip-10-0-142-95
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-95.ec2.internal
      uid: ff67601a-aae4-4d67-8f18-45c4cd8a2625
    resourceVersion: "37748"
    uid: 12c8dd1d-8272-43f5-bb75-022150c05bc6
  spec:
    sourcePod: network-check-source-7d88cb55d8-zt8zt
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T03:29:15Z"
      message: 'network-check-target-ip-10-0-142-95: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 985.428µs
      message: 'network-check-target-ip-10-0-142-95: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T03:43:15Z"
    - latency: 1.059117ms
      message: 'network-check-target-ip-10-0-142-95: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T03:42:15Z"
    - latency: 928.485µs
      message: 'network-check-target-ip-10-0-142-95: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T03:41:15Z"
    - latency: 1.485913ms
      message: 'network-check-target-ip-10-0-142-95: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T03:40:15Z"
    - latency: 860.501µs
      message: 'network-check-target-ip-10-0-142-95: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T03:39:15Z"
    - latency: 1.443616ms
      message: 'network-check-target-ip-10-0-142-95: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T03:38:15Z"
    - latency: 857.815µs
      message: 'network-check-target-ip-10-0-142-95: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T03:37:15Z"
    - latency: 846.96µs
      message: 'network-check-target-ip-10-0-142-95: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T03:36:15Z"
    - latency: 1.397271ms
      message: 'network-check-target-ip-10-0-142-95: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T03:35:15Z"
    - latency: 1.208752ms
      message: 'network-check-target-ip-10-0-142-95: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T03:34:15Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T03:22:14Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-95-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-95.ec2.internal
      uid: ff67601a-aae4-4d67-8f18-45c4cd8a2625
    resourceVersion: "34391"
    uid: 91a6bdbb-bb90-4d46-a96d-c7cf9666c957
  spec:
    sourcePod: network-check-source-7d88cb55d8-zt8zt
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T03:28:15Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 792.432µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T03:40:15Z"
    - latency: 1.908962ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T03:40:15Z"
    - latency: 893.818µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T03:39:15Z"
    - latency: 1.615376ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T03:39:15Z"
    - latency: 855.034µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T03:38:15Z"
    - latency: 2.415417ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T03:38:15Z"
    - latency: 1.074897ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T03:37:15Z"
    - latency: 1.618891ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T03:37:15Z"
    - latency: 975.407µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T03:36:15Z"
    - latency: 2.033833ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T03:36:15Z"
kind: List
metadata:
  resourceVersion: ""