Description:
If there is no Authorizer for AWS::Serverless::Api resource and you set Authorizer: NONE at api event level sam doesn't throw proper errors.

Sample Template:

AWSTemplateFormatVersion: '2010-09-09'
Transform: AWS::Serverless-2016-10-31
Resources:
  HelloWorldFunction:
    Type: AWS::Serverless::Function
    Properties:
      InlineCode: |
        def handle

I think it's pretty powerful we have dask array support, we should not forget to document that.

Description

How can I expose the API documentation to external users?

Automated API documentation is definitely one of the best features provided. However, since it exposes all the endpoints and model structures automatically, it seems more facilitating internal users, and should be protected with some authentication.

What if I want to expose some of these endpoints to external cust

https://github.com/trekhleb/javascript-algorithms/blob/master/src/algorithms/sets/cartesian-product/cartesianProduct.js#L8

I think it makes more sense to return an empty array

// invalid input return null or throw an error
if (!setA || !setB) {
    return null;
}
if (!setA.length || !setB.length) {
    return []; 
}
// or do nothing since the for loop will not trigger anyway

From react docs

Note:
We recommend using React Testing Library which is designed to enable and encourage writing tests that use your components as the end users do.
Alternatively, Airbnb has released a testing utility called Enzyme, which makes it easy to assert, manipulate, and traverse your React Components’ output.

Currently to run hubble using a non standard GRPC port and namespace you need to generate the charts via helm and make the changes manually to the output. It would be helpful if these where exposed configuration variables.

/kind documentation
/good-first-issue

Clean up the documentation to provide support for etcd clusters created with https://kubernetes.io/docs/setup/production-environment/tools/kubeadm/setup-ha-etcd-with-kubeadm/. Right now the docs are etcdadm specific, namely the locations of certs. Be generic (say which certs are needed) and then provide default location examples for etcdadm and kubeadm et