OpenAI see.

OpenAI ignore.

OpenAI train.

You joke... but https://www.npmjs.com/package/is-odd-or-even

even (https://www.npmjs.com/package/even?activeTab=dependencies) pulls is-even.

is-even (https://www.npmjs.com/package/is-even?activeTab=dependencies) pulls is-odd.

is-odd (https://www.npmjs.com/package/is-odd?activeTab=dependencies) pulls is-number.

sigh

If Google lets LaMDA out in the open, they will see their margins shrink. Lose-lose for Google. Great move by Microsoft.

It's in the article: https://archive.md/pxG5o

https://archive.md/pxG5o/62269879416fb0636f7f390f94242675498...

You could probably do something like (for django):

  python manage.py migrate

on pod startup. If there are no changes, it'll do nothing. If there are changes, it'll do the migration.

Yeah, it's basically this. I'm running this as an initContainer for my K8s-based deployments. Took me a bit to get everything going, but my stack is pretty much similar to OP's article, although not quite as advanced in the automated-deployment of containers and monitoring. I'm not at a position where usage needs heavy monitoring because I'm still in the pre-launch phase of things and I'm using this side project to learn stuff I've yet to get experience with at multiple companies.

In the authors case, terraform will create the EKS (kubernetes) cluster, which then is responsible for creating the EC2 instances. The actual application containers are then created by EKS.

Thanks for a great post! It was super detailed and I loved reading it. I had a quick question about your pg setup. You mentioned that you use EBS for your persistence storage, which is locked by zone . You can't have an EC2 instance in Zone 1 mount a storage in Zone 3. Does this cause issues with your db? Especially as you have HPA and ClusterAutoscaler, your k8s nodes could be spun up in Zone 1 for pg autoscaling but your data is in Zone 3.

Yeah, they have dredgers around for maintenance of the canal. This clip was from at least 6 months ago. https://youtu.be/P6st0k7KJmk

From the YouTube clip, it def seems like it's normal to see them when passing through the canal.

Some lessons I took from this retro:

- Disable autoscaling if appropriate during outage. For example if the web server is degraded, it's probably best to make sure that the backends don't autoscale down.

- Panic mode in Envoy is amazing!

- Ability to quickly scale your services is important, but that metric should also take into account how quickly the underlying infrastructure can scale. Your pods could spin up in 15 seconds but k8s nodes will not!