Michael S. Fischer

Hi everyone, Currently there is no official port of Chromium to Amazon Linux 2 for the arm64 architecture used by AWS Lambda. However, all is not lost! Since we can...

Hi @skmcgrail - I should note that the context provided when I built the `aws.Config` object was `context.TODO()`. I didn't add a deadline or anything like that. So if something...

@jayanthvn Understood - this suggestion is to make it log to standard output by default, as opposed to burdening the customer with making a change.

I think we can close this, as Emscripten is being built automatically for Arm64 via EC2.

Team: Having this functionality available will enable customers to use Cluster Autoscaler's [capacity autodiscovery feature](https://github.com/kubernetes/autoscaler/tree/master/cluster-autoscaler/cloudprovider/aws#auto-discovery-setup) instead of forcing them to maintain manual capacity mappings on the command line. The documentation...

@rtripat Understood. Perhaps I wasn't clear, but I was specifically referring to the ability to autodiscover specific capacity dimensions of an ASG such as cpu, memory, ephemeral storage, GPU, etc.

Hi everyone - you can find instructions for installing the node-local DNS cache here: https://kubernetes.io/docs/tasks/administer-cluster/nodelocaldns/

This is not possible at this time because `channels.leave` isn't available to bots per the API. I've filed a support request with Slack to find out why.

A related way to control Lita may be to have her ignore public (non-DM) messages sent to her via non-whitelisted channels. I'll file a separate issue for that.

I believe this issue can be resolved by offering the user the ability to require the same spot instance type as that of the on-demand instance being replaced.