apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-31T20:34:11Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-218-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-218.ec2.internal
      uid: 5a4d648c-e68d-4517-9050-d4a90d771a4c
    resourceVersion: "79437"
    uid: 7c6ebd29-67cb-49ad-a891-2e10ff2eea06
  spec:
    sourcePod: network-check-source-65bdbbff45-wt4mx
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-31T20:41:13Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 965.861µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T21:30:13Z"
    - latency: 1.665665ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T21:29:13Z"
    - latency: 1.06593ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T21:28:13Z"
    - latency: 1.285726ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T21:27:13Z"
    - latency: 986.983µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T21:26:13Z"
    - latency: 1.741319ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T21:25:13Z"
    - latency: 1.021729ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T21:24:13Z"
    - latency: 1.194716ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T21:23:13Z"
    - latency: 863.129µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T21:22:13Z"
    - latency: 1.219609ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T21:21:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-31T20:34:11Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-218-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-218.ec2.internal
      uid: 5a4d648c-e68d-4517-9050-d4a90d771a4c
    resourceVersion: "77464"
    uid: aa059665-38cf-4f96-a723-a40f405f134d
  spec:
    sourcePod: network-check-source-65bdbbff45-wt4mx
    targetEndpoint: a63cf96419de847f2b2b5026dac7930e-315f8b2eb65eb6de.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-31T20:40:13Z"
      message: 'load-balancer-api-external: tcp connection to a63cf96419de847f2b2b5026dac7930e-315f8b2eb65eb6de.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.694253ms
      message: 'load-balancer-api-external: tcp connection to a63cf96419de847f2b2b5026dac7930e-315f8b2eb65eb6de.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T21:28:13Z"
    - latency: 11.090204ms
      message: 'load-balancer-api-external: resolved host name a63cf96419de847f2b2b5026dac7930e-315f8b2eb65eb6de.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T21:28:13Z"
    - latency: 5.371046ms
      message: 'load-balancer-api-external: tcp connection to a63cf96419de847f2b2b5026dac7930e-315f8b2eb65eb6de.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T21:27:13Z"
    - latency: 9.693552ms
      message: 'load-balancer-api-external: resolved host name a63cf96419de847f2b2b5026dac7930e-315f8b2eb65eb6de.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T21:27:13Z"
    - latency: 3.431242ms
      message: 'load-balancer-api-external: tcp connection to a63cf96419de847f2b2b5026dac7930e-315f8b2eb65eb6de.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T21:26:13Z"
    - latency: 9.379015ms
      message: 'load-balancer-api-external: resolved host name a63cf96419de847f2b2b5026dac7930e-315f8b2eb65eb6de.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T21:26:13Z"
    - latency: 4.282774ms
      message: 'load-balancer-api-external: tcp connection to a63cf96419de847f2b2b5026dac7930e-315f8b2eb65eb6de.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T21:25:13Z"
    - latency: 7.605173ms
      message: 'load-balancer-api-external: resolved host name a63cf96419de847f2b2b5026dac7930e-315f8b2eb65eb6de.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T21:25:13Z"
    - latency: 4.073ms
      message: 'load-balancer-api-external: tcp connection to a63cf96419de847f2b2b5026dac7930e-315f8b2eb65eb6de.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T21:24:13Z"
    - latency: 8.481984ms
      message: 'load-balancer-api-external: resolved host name a63cf96419de847f2b2b5026dac7930e-315f8b2eb65eb6de.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T21:24:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-31T20:34:11Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-218-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-218.ec2.internal
      uid: 5a4d648c-e68d-4517-9050-d4a90d771a4c
    resourceVersion: "77465"
    uid: 34090688-3570-4f5f-bd56-ad6e1f52f6bb
  spec:
    sourcePod: network-check-source-65bdbbff45-wt4mx
    targetEndpoint: a63cf96419de847f2b2b5026dac7930e-315f8b2eb65eb6de.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-31T20:40:13Z"
      message: 'load-balancer-api-internal: tcp connection to a63cf96419de847f2b2b5026dac7930e-315f8b2eb65eb6de.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.656812ms
      message: 'load-balancer-api-internal: tcp connection to a63cf96419de847f2b2b5026dac7930e-315f8b2eb65eb6de.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T21:28:13Z"
    - latency: 11.145822ms
      message: 'load-balancer-api-internal: resolved host name a63cf96419de847f2b2b5026dac7930e-315f8b2eb65eb6de.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T21:28:13Z"
    - latency: 5.310733ms
      message: 'load-balancer-api-internal: tcp connection to a63cf96419de847f2b2b5026dac7930e-315f8b2eb65eb6de.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T21:27:13Z"
    - latency: 9.625599ms
      message: 'load-balancer-api-internal: resolved host name a63cf96419de847f2b2b5026dac7930e-315f8b2eb65eb6de.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T21:27:13Z"
    - latency: 3.597975ms
      message: 'load-balancer-api-internal: tcp connection to a63cf96419de847f2b2b5026dac7930e-315f8b2eb65eb6de.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T21:26:13Z"
    - latency: 9.357708ms
      message: 'load-balancer-api-internal: resolved host name a63cf96419de847f2b2b5026dac7930e-315f8b2eb65eb6de.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T21:26:13Z"
    - latency: 4.131685ms
      message: 'load-balancer-api-internal: tcp connection to a63cf96419de847f2b2b5026dac7930e-315f8b2eb65eb6de.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T21:25:13Z"
    - latency: 7.572436ms
      message: 'load-balancer-api-internal: resolved host name a63cf96419de847f2b2b5026dac7930e-315f8b2eb65eb6de.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T21:25:13Z"
    - latency: 4.082943ms
      message: 'load-balancer-api-internal: tcp connection to a63cf96419de847f2b2b5026dac7930e-315f8b2eb65eb6de.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T21:24:13Z"
    - latency: 8.438587ms
      message: 'load-balancer-api-internal: resolved host name a63cf96419de847f2b2b5026dac7930e-315f8b2eb65eb6de.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T21:24:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-31T20:34:11Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-218-to-network-check-target-ip-10-0-128-218
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-218.ec2.internal
      uid: 5a4d648c-e68d-4517-9050-d4a90d771a4c
    resourceVersion: "79435"
    uid: b96c8348-fbf7-4f20-91c9-772aa28211cc
  spec:
    sourcePod: network-check-source-65bdbbff45-wt4mx
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-31T20:41:13Z"
      message: 'network-check-target-ip-10-0-128-218: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.842ms
      message: 'network-check-target-ip-10-0-128-218: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T21:30:13Z"
    - latency: 1.843818ms
      message: 'network-check-target-ip-10-0-128-218: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T21:29:13Z"
    - latency: 1.539749ms
      message: 'network-check-target-ip-10-0-128-218: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T21:28:13Z"
    - latency: 1.038956ms
      message: 'network-check-target-ip-10-0-128-218: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T21:27:13Z"
    - latency: 1.131434ms
      message: 'network-check-target-ip-10-0-128-218: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T21:26:13Z"
    - latency: 1.25994ms
      message: 'network-check-target-ip-10-0-128-218: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T21:25:13Z"
    - latency: 1.500839ms
      message: 'network-check-target-ip-10-0-128-218: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T21:24:13Z"
    - latency: 1.107587ms
      message: 'network-check-target-ip-10-0-128-218: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T21:23:13Z"
    - latency: 993.319µs
      message: 'network-check-target-ip-10-0-128-218: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T21:22:13Z"
    - latency: 989.165µs
      message: 'network-check-target-ip-10-0-128-218: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T21:21:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-31T20:34:11Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-218-to-network-check-target-ip-10-0-132-89
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-218.ec2.internal
      uid: 5a4d648c-e68d-4517-9050-d4a90d771a4c
    resourceVersion: "79436"
    uid: 3b50e05d-4329-4434-8088-18ae634934a1
  spec:
    sourcePod: network-check-source-65bdbbff45-wt4mx
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-31T20:41:13Z"
      message: 'network-check-target-ip-10-0-132-89: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.698074ms
      message: 'network-check-target-ip-10-0-132-89: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T21:30:13Z"
    - latency: 2.634099ms
      message: 'network-check-target-ip-10-0-132-89: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T21:29:13Z"
    - latency: 2.296352ms
      message: 'network-check-target-ip-10-0-132-89: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T21:28:13Z"
    - latency: 2.157807ms
      message: 'network-check-target-ip-10-0-132-89: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T21:27:13Z"
    - latency: 2.26001ms
      message: 'network-check-target-ip-10-0-132-89: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T21:26:13Z"
    - latency: 2.097864ms
      message: 'network-check-target-ip-10-0-132-89: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T21:25:13Z"
    - latency: 2.433625ms
      message: 'network-check-target-ip-10-0-132-89: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T21:24:13Z"
    - latency: 2.521833ms
      message: 'network-check-target-ip-10-0-132-89: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T21:23:13Z"
    - latency: 2.563858ms
      message: 'network-check-target-ip-10-0-132-89: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T21:22:13Z"
    - latency: 2.440288ms
      message: 'network-check-target-ip-10-0-132-89: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T21:21:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-31T20:34:11Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-218-to-network-check-target-ip-10-0-141-177
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-218.ec2.internal
      uid: 5a4d648c-e68d-4517-9050-d4a90d771a4c
    resourceVersion: "79434"
    uid: 2c0d499e-94cf-401e-a447-3e8d70684ef1
  spec:
    sourcePod: network-check-source-65bdbbff45-wt4mx
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-31T20:41:13Z"
      message: 'network-check-target-ip-10-0-141-177: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.014893ms
      message: 'network-check-target-ip-10-0-141-177: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T21:30:13Z"
    - latency: 1.882076ms
      message: 'network-check-target-ip-10-0-141-177: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T21:29:13Z"
    - latency: 2.407069ms
      message: 'network-check-target-ip-10-0-141-177: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T21:28:13Z"
    - latency: 2.251796ms
      message: 'network-check-target-ip-10-0-141-177: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T21:27:13Z"
    - latency: 2.36242ms
      message: 'network-check-target-ip-10-0-141-177: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T21:26:13Z"
    - latency: 2.439816ms
      message: 'network-check-target-ip-10-0-141-177: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T21:25:13Z"
    - latency: 2.046604ms
      message: 'network-check-target-ip-10-0-141-177: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T21:24:13Z"
    - latency: 2.133832ms
      message: 'network-check-target-ip-10-0-141-177: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T21:23:13Z"
    - latency: 2.176184ms
      message: 'network-check-target-ip-10-0-141-177: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T21:22:13Z"
    - latency: 2.036895ms
      message: 'network-check-target-ip-10-0-141-177: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T21:21:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-31T20:34:11Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-218-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-218.ec2.internal
      uid: 5a4d648c-e68d-4517-9050-d4a90d771a4c
    resourceVersion: "77463"
    uid: d7cc1dd5-35c2-4cbe-a3b1-53cfe4a06aa8
  spec:
    sourcePod: network-check-source-65bdbbff45-wt4mx
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-31T20:40:13Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 894.984µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T21:28:13Z"
    - latency: 2.399606ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T21:28:13Z"
    - latency: 957.061µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T21:27:13Z"
    - latency: 2.303864ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T21:27:13Z"
    - latency: 1.01854ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T21:26:13Z"
    - latency: 2.155528ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T21:26:13Z"
    - latency: 1.075253ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T21:25:13Z"
    - latency: 2.365623ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T21:25:13Z"
    - latency: 1.003163ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T21:24:13Z"
    - latency: 2.663833ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T21:24:13Z"
kind: List
metadata:
  resourceVersion: ""