Chalice-PynamoDB-Docker-Starter-Kit
Helm-Chart-Boilerplates
Our great sponsors
Chalice-PynamoDB-Docker-Starter-Kit | Helm-Chart-Boilerplates | |
---|---|---|
5 | 12 | |
7 | 8 | |
- | - | |
1.5 | 0.0 | |
12 months ago | over 1 year ago | |
Python | Makefile | |
GNU General Public License v3.0 only | - |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Chalice-PynamoDB-Docker-Starter-Kit
-
Is there a typical setup for building and deploying python to lambda using terraform?
If you want a starter kit to get running faster with it you might want to check out my Chalice PynamoDB starter kit which uses docker to have a great local development experience which is pretty lacking elsewhere.
-
Serverless Lambda Rest-API is good?
Check it out: https://github.com/DevOps-Nirvana/Chalice-PynamoDB-Docker-Starter-Kit
-
AWS Lambda, a good host for a rest API?
If you want to get started with this framework, I've made a simple Docker and Docker Compose starter-kit I invite you to play with. It is Python, however. Check it out if it helps: https://github.com/DevOps-Nirvana/Chalice-PynamoDB-Docker-Starter-Kit
-
How do you guys on Mac M1's get around the annoying port forwarding issues with k8s + docker?
Here's an example Docker-compose file on an open-source example/best practices repo for using AWS, Chalice, DynamoDB, PynamoDB, and more. I guarantee this will work on your mac, because this works on both of mine. Once I run it, I can jump into my browser and use http://localhost:8001 to review the admin interface for DynamoDB. This works perfectly!
-
Monthly 'Shameless Self Promotion' thread - 2023/01
(just authored yesterday) A repository that is a starter-kit for folks to get into authoring REST APIs via AWS Lambda at very low-cost with Python and DynamoDB with my Chalice PynamoDB Docker Starter-Kit. This is something I've been playing with and using at various microservices and startups recently and figured I should open source something.
Helm-Chart-Boilerplates
-
Dedpulication standards of Helm Charts values file for a global chart with subcharts for our app. What's the right way to only need to specify a value once?
I would point you to what I call the "Universal Helm Charts" and some examples of how to use them.
-
Monitoring many cluster k8s
Shameless Plug: Here's one of my dashboards I made for Ingress-Nginx, which is my recommended border router/gateway into all the services. It adds deep robust metrics and configurability, and if you've got years of experience with Nginx also, it allows you rich complex customization via nginx's configuration structure via kubernetes annotations. Besides that I have open-source helm charts which are easy to use, boilerplates showing how to use them, a volume autoscaler to automatically resize your disks as they get full, and a blog where I share various of my experience which is a companion blog to my upcoming book of the same name. Hope this helps! Feel free to ask if you have any further questions.
-
Best way of managing Helm?
Here is an example of a repo that uses an sub-chart: https://github.com/DevOps-Nirvana/Helm-Chart-Boilerplates/tree/master/boilerplate-apache-with-configmap-template/deployment
-
Helm makes it overly complex, or is it just me?
Use multi-values files with helm ALWAYS. Allowing an env-specific overlay to tweak your default values files. See: https://github.com/DevOps-Nirvana/Helm-Chart-Boilerplates/tree/master/boilerplate-echoserver/deployment/boilerplate-echoserver
-
The Helmet is a Helm Library Chart that defines many chart templates like Deployment, Service, Ingress, etc which can used in other application charts.
Helm charts - https://github.com/DevOps-Nirvana/Universal-Kubernetes-Helm-Charts Example using helm charts as sub charts - https://github.com/DevOps-Nirvana/Helm-Chart-Boilerplates/tree/master/boilerplate-echoserver
- How do you guys manage your deployment pipelines?
-
Monthly 'Shameless Self Promotion' thread - 2023/01
Helm Chart Boilerplates are examples of usage of the above Universal Helm Charts to help people understand how to use them more, a stop-gap until I add more documentation
- Deploying with Helm - extra manifests?
-
Creating Kubernetes Templates
Helm Chart Usage Boilerplates (Examples of using these helm chart)
-
Use Kubernetes to load test my product.
To help you on deploying your service, I've created open source generic/universal Helm Charts to make it easy to do the above. Here are the Universal Helm Charts and here's some boilerplate examples of using them. These built-in have support for HPAs, services, ingresses, etc, making it as easy as autoscaling.enable: true I haven't gotten around to documenting the helm charts yet, but there's lots of comments in the values.yaml file explaining everything.
What are some alternatives?
Universal-Kubernetes-Helm-Charts - Some universal helm charts used for deploying services onto Kubernetes. All-in-one best-practices
playwright-testing
argocd-autopilot - Argo-CD Autopilot
Kubernetes-Volume-Autoscaler - Autoscaling volumes for Kubernetes (with the help of Prometheus)
helm-charts - A collection of Helm charts
kube-reqsizer - A Kubernetes controller for automatically optimizing pod requests based on their continuous usage. VPA alternative that can work with HPA.
helmfile - Declaratively deploy your Kubernetes manifests, Kustomize configs, and Charts as Helm releases. Generate all-in-one manifests for use with ArgoCD.
dyrectorio - dyrector.io is a self-hosted continuous delivery & deployment platform with version management.
featbit - A feature flags service written in .NET
eksctl - The official CLI for Amazon EKS