apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-04T01:57:53Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-204-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-204.us-west-1.compute.internal
      uid: a886dcee-5669-4e84-b3c2-688303321273
    resourceVersion: "49604"
    uid: f58065f8-14ea-4b4a-9650-22bae04bcf77
  spec:
    sourcePod: network-check-source-6f78d59f99-p2kf6
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-11-04T02:04:53Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 958.765µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T02:25:53Z"
    - latency: 1.116698ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T02:24:53Z"
    - latency: 918.768µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T02:23:53Z"
    - latency: 948.547µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T02:22:53Z"
    - latency: 1.032709ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T02:21:53Z"
    - latency: 943.65µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T02:20:53Z"
    - latency: 1.09655ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T02:19:53Z"
    - latency: 1.629201ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T02:18:53Z"
    - latency: 1.243726ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T02:17:53Z"
    - latency: 1.400322ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T02:16:53Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-04T01:57:53Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-204-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-204.us-west-1.compute.internal
      uid: a886dcee-5669-4e84-b3c2-688303321273
    resourceVersion: "51687"
    uid: 20153e2c-8bad-455b-839d-654b49a351fc
  spec:
    sourcePod: network-check-source-6f78d59f99-p2kf6
    targetEndpoint: ab045e258af594899a140baaafc158e1-d72efd8280e6925c.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-11-04T02:03:54Z"
      message: 'load-balancer-api-external: tcp connection to ab045e258af594899a140baaafc158e1-d72efd8280e6925c.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 53.91064ms
      message: 'load-balancer-api-external: tcp connection to ab045e258af594899a140baaafc158e1-d72efd8280e6925c.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T02:27:53Z"
    - latency: 6.187888ms
      message: 'load-balancer-api-external: resolved host name ab045e258af594899a140baaafc158e1-d72efd8280e6925c.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T02:27:53Z"
    - latency: 54.127303ms
      message: 'load-balancer-api-external: tcp connection to ab045e258af594899a140baaafc158e1-d72efd8280e6925c.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T02:26:53Z"
    - latency: 6.477153ms
      message: 'load-balancer-api-external: resolved host name ab045e258af594899a140baaafc158e1-d72efd8280e6925c.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T02:26:53Z"
    - latency: 54.11409ms
      message: 'load-balancer-api-external: tcp connection to ab045e258af594899a140baaafc158e1-d72efd8280e6925c.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T02:25:53Z"
    - latency: 7.170338ms
      message: 'load-balancer-api-external: resolved host name ab045e258af594899a140baaafc158e1-d72efd8280e6925c.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T02:25:53Z"
    - latency: 68.292408ms
      message: 'load-balancer-api-external: tcp connection to ab045e258af594899a140baaafc158e1-d72efd8280e6925c.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T02:24:53Z"
    - latency: 6.405688ms
      message: 'load-balancer-api-external: resolved host name ab045e258af594899a140baaafc158e1-d72efd8280e6925c.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T02:24:53Z"
    - latency: 55.159707ms
      message: 'load-balancer-api-external: tcp connection to ab045e258af594899a140baaafc158e1-d72efd8280e6925c.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T02:23:53Z"
    - latency: 6.165737ms
      message: 'load-balancer-api-external: resolved host name ab045e258af594899a140baaafc158e1-d72efd8280e6925c.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T02:23:53Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-04T01:57:53Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-204-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-204.us-west-1.compute.internal
      uid: a886dcee-5669-4e84-b3c2-688303321273
    resourceVersion: "51686"
    uid: 4ce09fbe-bcef-40a5-836c-7132cbc72583
  spec:
    sourcePod: network-check-source-6f78d59f99-p2kf6
    targetEndpoint: ab045e258af594899a140baaafc158e1-d72efd8280e6925c.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-11-04T02:03:53Z"
      message: 'load-balancer-api-internal: tcp connection to ab045e258af594899a140baaafc158e1-d72efd8280e6925c.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 53.968699ms
      message: 'load-balancer-api-internal: tcp connection to ab045e258af594899a140baaafc158e1-d72efd8280e6925c.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T02:27:53Z"
    - latency: 6.227238ms
      message: 'load-balancer-api-internal: resolved host name ab045e258af594899a140baaafc158e1-d72efd8280e6925c.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T02:27:53Z"
    - latency: 54.143658ms
      message: 'load-balancer-api-internal: tcp connection to ab045e258af594899a140baaafc158e1-d72efd8280e6925c.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T02:26:53Z"
    - latency: 6.387566ms
      message: 'load-balancer-api-internal: resolved host name ab045e258af594899a140baaafc158e1-d72efd8280e6925c.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T02:26:53Z"
    - latency: 54.162581ms
      message: 'load-balancer-api-internal: tcp connection to ab045e258af594899a140baaafc158e1-d72efd8280e6925c.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T02:25:53Z"
    - latency: 7.130409ms
      message: 'load-balancer-api-internal: resolved host name ab045e258af594899a140baaafc158e1-d72efd8280e6925c.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T02:25:53Z"
    - latency: 68.288132ms
      message: 'load-balancer-api-internal: tcp connection to ab045e258af594899a140baaafc158e1-d72efd8280e6925c.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T02:24:53Z"
    - latency: 6.46993ms
      message: 'load-balancer-api-internal: resolved host name ab045e258af594899a140baaafc158e1-d72efd8280e6925c.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T02:24:53Z"
    - latency: 55.149262ms
      message: 'load-balancer-api-internal: tcp connection to ab045e258af594899a140baaafc158e1-d72efd8280e6925c.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T02:23:53Z"
    - latency: 6.106448ms
      message: 'load-balancer-api-internal: resolved host name ab045e258af594899a140baaafc158e1-d72efd8280e6925c.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T02:23:53Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-04T01:57:53Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-204-to-network-check-target-ip-10-0-134-176
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-204.us-west-1.compute.internal
      uid: a886dcee-5669-4e84-b3c2-688303321273
    resourceVersion: "49593"
    uid: e6651a66-60de-4156-b221-4eefa15f109a
  spec:
    sourcePod: network-check-source-6f78d59f99-p2kf6
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-04T02:04:53Z"
      message: 'network-check-target-ip-10-0-134-176: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.060149ms
      message: 'network-check-target-ip-10-0-134-176: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T02:25:53Z"
    - latency: 2.440662ms
      message: 'network-check-target-ip-10-0-134-176: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T02:24:53Z"
    - latency: 1.99199ms
      message: 'network-check-target-ip-10-0-134-176: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T02:23:53Z"
    - latency: 2.049418ms
      message: 'network-check-target-ip-10-0-134-176: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T02:22:53Z"
    - latency: 2.513392ms
      message: 'network-check-target-ip-10-0-134-176: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T02:21:53Z"
    - latency: 2.183201ms
      message: 'network-check-target-ip-10-0-134-176: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T02:20:53Z"
    - latency: 2.295092ms
      message: 'network-check-target-ip-10-0-134-176: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T02:19:53Z"
    - latency: 2.627102ms
      message: 'network-check-target-ip-10-0-134-176: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T02:18:53Z"
    - latency: 2.66119ms
      message: 'network-check-target-ip-10-0-134-176: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T02:17:53Z"
    - latency: 2.598476ms
      message: 'network-check-target-ip-10-0-134-176: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T02:16:53Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-04T01:57:53Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-204-to-network-check-target-ip-10-0-134-204
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-204.us-west-1.compute.internal
      uid: a886dcee-5669-4e84-b3c2-688303321273
    resourceVersion: "49592"
    uid: 92451d0b-5394-46dd-a48a-4d6f9e8db76f
  spec:
    sourcePod: network-check-source-6f78d59f99-p2kf6
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-04T02:04:53Z"
      message: 'network-check-target-ip-10-0-134-204: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 921.639µs
      message: 'network-check-target-ip-10-0-134-204: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T02:25:53Z"
    - latency: 1.204741ms
      message: 'network-check-target-ip-10-0-134-204: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T02:24:53Z"
    - latency: 1.04359ms
      message: 'network-check-target-ip-10-0-134-204: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T02:23:53Z"
    - latency: 1.410182ms
      message: 'network-check-target-ip-10-0-134-204: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T02:22:53Z"
    - latency: 1.096634ms
      message: 'network-check-target-ip-10-0-134-204: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T02:21:53Z"
    - latency: 1.183919ms
      message: 'network-check-target-ip-10-0-134-204: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T02:20:53Z"
    - latency: 1.102201ms
      message: 'network-check-target-ip-10-0-134-204: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T02:19:53Z"
    - latency: 1.248395ms
      message: 'network-check-target-ip-10-0-134-204: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T02:18:53Z"
    - latency: 1.320865ms
      message: 'network-check-target-ip-10-0-134-204: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T02:17:53Z"
    - latency: 1.126682ms
      message: 'network-check-target-ip-10-0-134-204: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T02:16:53Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-04T01:57:53Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-204-to-network-check-target-ip-10-0-142-191
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-204.us-west-1.compute.internal
      uid: a886dcee-5669-4e84-b3c2-688303321273
    resourceVersion: "49594"
    uid: ac9b2d6e-244f-439a-bb8d-79b80aa9e5ca
  spec:
    sourcePod: network-check-source-6f78d59f99-p2kf6
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-04T02:04:53Z"
      message: 'network-check-target-ip-10-0-142-191: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.071848ms
      message: 'network-check-target-ip-10-0-142-191: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T02:25:53Z"
    - latency: 2.40501ms
      message: 'network-check-target-ip-10-0-142-191: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T02:24:53Z"
    - latency: 2.566097ms
      message: 'network-check-target-ip-10-0-142-191: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T02:23:53Z"
    - latency: 2.433481ms
      message: 'network-check-target-ip-10-0-142-191: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T02:22:53Z"
    - latency: 2.962273ms
      message: 'network-check-target-ip-10-0-142-191: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T02:21:53Z"
    - latency: 2.193222ms
      message: 'network-check-target-ip-10-0-142-191: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T02:20:53Z"
    - latency: 2.399518ms
      message: 'network-check-target-ip-10-0-142-191: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T02:19:53Z"
    - latency: 2.167602ms
      message: 'network-check-target-ip-10-0-142-191: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T02:18:53Z"
    - latency: 2.521403ms
      message: 'network-check-target-ip-10-0-142-191: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T02:17:53Z"
    - latency: 2.908644ms
      message: 'network-check-target-ip-10-0-142-191: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T02:16:53Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-04T01:57:53Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-204-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-204.us-west-1.compute.internal
      uid: a886dcee-5669-4e84-b3c2-688303321273
    resourceVersion: "51683"
    uid: 3afe2e74-78ab-4428-8f1a-527aae45d9c5
  spec:
    sourcePod: network-check-source-6f78d59f99-p2kf6
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-11-04T02:03:53Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 898.919µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T02:27:53Z"
    - latency: 1.758265ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T02:27:53Z"
    - latency: 1.176533ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T02:26:53Z"
    - latency: 1.867923ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T02:26:53Z"
    - latency: 917.752µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T02:25:53Z"
    - latency: 2.028748ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T02:25:53Z"
    - latency: 945.78µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T02:24:53Z"
    - latency: 1.948423ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T02:24:53Z"
    - latency: 972.686µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T02:23:53Z"
    - latency: 1.672594ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T02:23:53Z"
kind: List
metadata:
  resourceVersion: ""