mirror of
https://github.com/nubenetes/awesome-kubernetes.git
synced 2026-07-12 18:00:37 +00:00
Jan 26th
This commit is contained in:
Inaki Fernandez
@@ -66,6 +66,7 @@
|
||||
- [WebSocket](https://en.wikipedia.org/wiki/WebSocket)
|
||||
- [The State of Real-Time Web in 2016](https://banksco.de/p/state-of-realtime-web-2016.html)
|
||||
- [SPDY and WebSocket Support at Akamai](https://blogs.akamai.com/2012/07/spdy-and-websocket-support-at-akamai.html)
|
||||
- [spring.io: YMNNALFT: Websockets](https://spring.io/blog/2021/01/25/ymnnalft-websockets) Welcome to another installment of You May Not Need Another Library For That (YMNNALFT)!
|
||||
|
||||
---
|
||||
<center>
|
||||
|
||||
@@ -630,6 +630,7 @@ aws ec2 describe-instances --query 'Reservations[].Instances[].[Placement.Availa
|
||||
- [medium: Using Helm with Amazon EKS without kubeconfigs](https://medium.com/analytics-vidhya/using-helm-with-amazon-eks-without-a-kubeconfig-733f44a31b1d)
|
||||
- [linkedin.com: Amazon EKS Distro (EKS-D): The Kubernetes Distribution Used by Amazon EKS 🌟](https://www.linkedin.com/pulse/amazon-eks-distro-eks-d-kubernetes-distribution-used-gokul-chandra/)
|
||||
- [aws.amazon.com: Introducing Federated Amazon EKS Clusters on AWS](https://aws.amazon.com/about-aws/whats-new/2021/01/introducing-federated-amazon-eks-clusters-aws/)
|
||||
- [medium: How to Deploy an EKS stack in AWS?](https://medium.com/avmconsulting-blog/how-to-deploy-an-eks-stack-to-kubernetes-aws-5ec9c5a07247)
|
||||
|
||||
## AWS App Mesh
|
||||
- [AWS App Mesh Workshop](https://www.appmeshworkshop.com/)
|
||||
|
||||
@@ -89,6 +89,7 @@
|
||||
* [dockerlabs.collabnix.com: Cheatsheet - Kubectl 🌟](https://dockerlabs.collabnix.com/kubernetes/cheatsheets/kubectl.html)
|
||||
* [medium: Awesome Kubernetes Command-Line Hacks](https://medium.com/better-programming/awesome-kubernetes-command-line-hacks-8bd3604e394f) Tips for you to kubectl like a pro
|
||||
* [akhilsharma.work: kubectl Get Resource - Short Names](https://akhilsharma.work/kubectl-get-resource-short-names/)
|
||||
* [blog.mimacom.com: Kubernetes Cheat Sheet](https://blog.mimacom.com/kubernetes-cheat-sheet/)
|
||||
|
||||
## Docker Cheat Sheets
|
||||
- [dockerlux.github.io: Docker Cheat Sheet](http://dockerlux.github.io/pdfcheat-sheet-v2.pdf)
|
||||
|
||||
@@ -74,6 +74,7 @@ Here are some important things to consider while building a CI/CD pipeline:
|
||||
- [harness.io: Intro to Deployment Strategies: Blue-Green, Canary, and More 🌟](https://harness.io/blog/continuous-verification/blue-green-canary-deployment-strategies/)
|
||||
- [medium: Continuous Kubernetes blue-green deployments on Azure using Nginx, AppGateway or TrafficManager — part 2](https://medium.com/@denniszielke/continuous-kubernetes-blue-green-deployments-on-azure-using-nginx-appgateway-or-trafficmanager-4490bce29cb)
|
||||
- [gitconnected.com: Blue-Green with Canary Deployment — A Novel approach](https://levelup.gitconnected.com/blue-green-with-canary-deployment-a-novel-approach-2cee77ff564d)
|
||||
- [semaphoreci.com: Continuous Blue-Green Deployments With Kubernetes 🌟](https://semaphoreci.com/blog/continuous-blue-green-deployments-with-kubernetes)
|
||||
|
||||
|
||||
<center>
|
||||
|
||||
@@ -44,6 +44,7 @@
|
||||
- [Postman & Newman API Automated Tests](#postman--newman-api-automated-tests)
|
||||
- [Monitoring Jenkins with Grafana](#monitoring-jenkins-with-grafana)
|
||||
- [Jenkins X](#jenkins-x)
|
||||
- [Spinnaker](#spinnaker)
|
||||
- [Nexus3 on Kubernetes](#nexus3-on-kubernetes)
|
||||
- [GitLab](#gitlab)
|
||||
- [Spring PetClinic Sample Application](#spring-petclinic-sample-application)
|
||||
@@ -391,6 +392,18 @@ Grab them from here: [awesome-kubernetes/scripts](https://github.com/redhatspain
|
||||
- [blog.testproject.io: Jenkins X Cloud Native CI/CD with TestProject](https://blog.testproject.io/2020/07/09/jenkins-x-cloud-native-ci-cd-with-testproject/)
|
||||
- [Modernize Your CI/CD Pipeline Using Jenkins X with Amazon EKS](https://aws.amazon.com/blogs/apn/modernize-your-ci-cd-pipeline-using-jenkins-x-with-amazon-eks/)
|
||||
|
||||
## Spinnaker
|
||||
- [Demo/Evaluation Installations](https://spinnaker.io/setup/quickstart/)
|
||||
- [imperialwicket/spinnaker-demo](https://github.com/imperialwicket/spinnaker-demo)
|
||||
- [henrybell/spinnaker-demo-app](https://github.com/henrybell/spinnaker-demo-app)
|
||||
- [codeburst.io: Spinnaker by Example: Part 1](https://codeburst.io/spinnaker-by-example-part-1-c4de9180d689)
|
||||
- [codeburst.io: Spinnaker by Example: Part 2](https://codeburst.io/spinnaker-by-example-part-2-6f92a1fdaedf)
|
||||
- [codeburst.io: Spinnaker by Example: Part 3](https://codeburst.io/spinnaker-by-example-part-3-c6ed9ac5f8ce)
|
||||
- [dzone: Continuous Deployment on Kubernetes With Spinnaker](https://dzone.com/articles/continuous-deployment-on-kubernetes-with-spinnaker) In this article, learn how to setup Spinnaker and integrate it with Gitlab CI and Jenkins to build and run CI and CD pipelines.
|
||||
- [dzone: Continuous Delivery Pipeline for Kubernetes Using Spinnaker](https://dzone.com/articles/continuous-delivery-pipeline-for-kubernetes-using) This post will focus on pushing out new releases of the application to our Kubernetes cluster i.e. Continuous Delivery.
|
||||
- [armory.io: How to Set Up Liquibase in Spinnaker](https://www.armory.io/blog/how-to-set-up-liquibase-in-spinnaker/)
|
||||
- [armory.io: Build a Deployment Pipeline with Spinnaker on Kubernetes](https://www.armory.io/blog/build-a-deployment-pipeline-with-spinnaker-on-kubernetes/)
|
||||
|
||||
## Nexus3 on Kubernetes
|
||||
* [Proof of Concept: Nexus3 Chart configuration on Kubernetes](https://github.com/redhatspain/nexus3-helm-chart) A choerodon/nexus3 Helm 3 Sample Chart on Digital Ocean Kubernetes
|
||||
|
||||
|
||||
@@ -17,6 +17,7 @@
|
||||
- [Gloo Federation API Gateway Management](#gloo-federation-api-gateway-management)
|
||||
- [Backstage Developer Portal](#backstage-developer-portal)
|
||||
- [APISIX](#apisix)
|
||||
- [NGINX as an API Gateway](#nginx-as-an-api-gateway)
|
||||
- [Mobile Developer Portals](#mobile-developer-portals)
|
||||
- [Automotive](#automotive)
|
||||
- [Auto API](#auto-api)
|
||||
@@ -104,6 +105,9 @@
|
||||
- [apisix](https://github.com/apache/apisix)
|
||||
- [thenewstack.io - APISIX: An Open Source API Gateway for Microservices](https://thenewstack.io/apisix-an-open-source-api-gateway-for-microservices/)
|
||||
|
||||
### NGINX as an API Gateway
|
||||
- [nginx.com: Deploying NGINX as an API Gateway, Part 1 🌟](https://www.nginx.com/blog/deploying-nginx-plus-as-an-api-gateway-part-1/)
|
||||
|
||||
## Mobile Developer Portals
|
||||
- [developer.mobileconnect.io](https://developer.mobileconnect.io/)
|
||||
- [developer.android.com](https://developer.android.com/)
|
||||
|
||||
@@ -227,6 +227,7 @@ git push origin -f
|
||||
* [github.blog: Testing cloud apps with GitHub Actions and cloud-native open source tools](https://github.blog/2020-10-09-devops-cloud-testing/)
|
||||
* [theregister.com: Passwords begone: GitHub will ban them next year for authenticating Git operations](https://www.theregister.com/2020/12/17/github_bans_passwords/)
|
||||
* [github.blog: Learn about ghapi, a new third-party Python client for the GitHub API](https://github.blog/2020-12-18-learn-about-ghapi-a-new-third-party-python-client-for-the-github-api/)
|
||||
* [github.blog: Improving how we deploy GitHub](https://github.blog/2021-01-25-improving-how-we-deploy-github/)
|
||||
|
||||
## Git Tools
|
||||
* [Atlassian Sourcetree](https://www.sourcetreeapp.com/)
|
||||
|
||||
@@ -51,7 +51,7 @@
|
||||
* [youtube: Jenkins X: The Recipe For Continuous Delivery](https://www.youtube.com/watch?v=ihHr-iLfEGo)
|
||||
* [Book: The DevOps 2.6 Toolkit: Jenkins X](https://leanpub.com/the-devops-2-6-toolkit)
|
||||
* [spinnaker.io](https://www.spinnaker.io/)
|
||||
* [Deploy Spinnaker CD Pipelines in Kubernetes](https://www.opsmx.com/blog/deploy-spinnaker-cd-pipelines-in-kubernetes/)
|
||||
* [Deploy Spinnaker CD Pipelines in Kubernetes](https://www.opsmx.com/blog/deploy-spinnaker-cd-pipelines-in-kubernetes/)
|
||||
* [ArgoCD](https://argoproj.github.io/argo-cd/) Declarative GitOps CD for Kubernetes
|
||||
* [Cloud Native Computing Foundation Accepts Argo as an Incubator Project](https://www.intuit.com/blog/technology/cloud-native-computing-foundation-accepts-argo-as-an-incubator-project/)
|
||||
* [openshift.com: OpenShift Authentication Integration with ArgoCD](https://www.openshift.com/blog/openshift-authentication-integration-with-argocd)
|
||||
|
||||
@@ -863,6 +863,7 @@ kubectl get secret <secret-name> --namespace=<source> -o yaml | sed ‘s/names
|
||||
- [Tagger](https://github.com/ricardomaraschini/tagger) keeps references to externally hosted Docker images internally in a Kubernetes cluster by mapping their tags (such as latest) into their references by hash
|
||||
- [helm-ecr 🌟](https://github.com/vetyy/helm-ecr) is a Helm plugin that supports installing Charts from AWS ECR.
|
||||
- [PipeCD](https://github.com/pipe-cd/pipe) is a continuous delivery system for declarative Kubernetes, Serverless, and Infrastructure applications.
|
||||
- [kubecolor 🌟](https://github.com/dty1er/kubecolor) colorises your kubectl output
|
||||
|
||||
## Enforcing Policies and governance for kubernetes workloads with Conftest
|
||||
* [Accelerated Feedback Loops when Developing for Kubernetes with Conftest](https://engineering.plex.com/posts/kubernetes-policy-conftest) Learn how to validate Kubernetes resources with Conftest for faster feedback loops
|
||||
@@ -1117,6 +1118,7 @@ kubectl get secret <secret-name> --namespace=<source> -o yaml | sed ‘s/names
|
||||
* [howtoforge.com: Network Policy in Kubernetes 🌟](https://www.howtoforge.com/kubernetes_network_policy/) By default, pods accept traffic from any source. A network policy helps to specify how a group of pods can communicate with each other and other network endpoints.
|
||||
* [medium: How to Provision Network Policies in Kubernetes | AWS 🌟](https://medium.com/avmconsulting-blog/exploring-network-policies-in-kubernetes-c8a3d8ed00cb)
|
||||
* [learncloudnative.com: Kubernetes Network Policy](https://www.learncloudnative.com/blog/2020-10-07-network-policies)
|
||||
* [bionconsulting.com: Kubernetes Network Policies](https://www.bionconsulting.com/blog/kubernetes-network-policies)
|
||||
|
||||
|
||||
<center>
|
||||
|
||||
@@ -9,6 +9,7 @@
|
||||
- [Linux Commands and Tools](#linux-commands-and-tools)
|
||||
- [Bash](#bash)
|
||||
- [Linux processes](#linux-processes)
|
||||
- [Linux Memory](#linux-memory)
|
||||
- [Linux and Kubernetes](#linux-and-kubernetes)
|
||||
- [Systemd](#systemd)
|
||||
- [Blogs](#blogs)
|
||||
@@ -26,6 +27,7 @@
|
||||
- [cyberciti.biz: Red Hat introduces new no-cost RHEL option](https://www.cyberciti.biz/linux-news/red-hat-introduces-new-no-cost-rhel-option/)
|
||||
- [zdnet.com: Red Hat introduces free RHEL for small production workloads and development teams](https://www.zdnet.com/google-amp/article/red-hat-introduces-free-rhel-for-small-production-workloads-development-teams/) In response to complaints about Red Hat's latest plans for CentOS Linux, Red Hat will start offering no-cost Red Hat Enterprise Linux for small production workloads and customer development teams.
|
||||
- [enterpriseai.news: Red Hat’s Disruption of CentOS Unleashes Storm of Dissent](https://www.enterpriseai.news/2021/01/22/red-hats-disruption-of-centos-unleashes-storm-of-dissent/)
|
||||
- [arstechnica.com: Why Red Hat killed CentOS—a CentOS board member speaks](https://arstechnica.com/gadgets/2021/01/on-the-death-of-centos-red-hat-liaison-brian-exelbierd-speaks/) "The CentOS Board doesn't get to decide what Red Hat engineering teams do."
|
||||
|
||||
## VIM
|
||||
- [VimWiki](https://github.com/vimwiki/vimwiki)
|
||||
@@ -115,6 +117,9 @@
|
||||
## Linux processes
|
||||
- [percona.com: How Much Memory Does the Process Really Take on Linux? 🌟](https://www.percona.com/blog/2020/09/11/how-much-memory-does-the-process-really-take-on-linux/)
|
||||
|
||||
## Linux Memory
|
||||
- [learnsteps.com: Difference between minor page faults vs major page faults](https://www.learnsteps.com/difference-between-minor-page-faults-vs-major-page-faults/)
|
||||
|
||||
## Linux and Kubernetes
|
||||
- [How Linux PID namespaces work with containers 🌟](https://www.redhat.com/sysadmin/linux-pid-namespaces)
|
||||
|
||||
|
||||
@@ -85,6 +85,7 @@
|
||||
* [sysdig.com: How to monitor kube-proxy](https://sysdig.com/blog/monitor-kube-proxy/)
|
||||
* [thenewstack.io: Monitoring vs. Observability: What’s the Difference?](https://thenewstack.io/monitoring-vs-observability-whats-the-difference/)
|
||||
* [getenroute.io: TSDB, Prometheus, Grafana In Kubernetes: Tracing A Variable Across The OSS Monitoring Stack](https://getenroute.io/blog/leverage-open-source-oss-derive-insights-grafana-prometheus-tsdb-kubernetes-standalone-api-gateway/)
|
||||
* [grafana.com: A beginner's guide to distributed tracing and how it can increase an application's performance](https://grafana.com/blog/2021/01/25/a-beginners-guide-to-distributed-tracing-and-how-it-can-increase-an-applications-performance/)
|
||||
|
||||
### Key Performance Indicator (KPI)
|
||||
* [KPIs](https://kpi.org/KPI-Basics)
|
||||
|
||||
@@ -20,6 +20,10 @@
|
||||
- [youtube: Platform9’s Madhura Maskasky says observability is also essential for diagnosing and debugging in order for SREs to "get to the root cause quickly enough so that you can feed that back to the development teams." 🌟](https://www.youtube.com/watch?v=tgRPlAQpHYk&ab_channel=TheNewStack) Debugging remains complex. Debugging in "a world of microservices is a very difficult task," requiring the identification of which specific part in a microservices deployment must be fixed, says Platform9’s Madhura Maskasky.
|
||||
- "What's happening to the system administrator or is the system administrator becoming an SRE? Are they going into different roles? Are they taking multiple roles? How do they play a part in ensuring that reliability in these new roles?"
|
||||
- "The way Google defines SRE is that an SRE by nature needs to be someone who develops or writes code 50% of the time and only remaining 50% of the time they do the traditional ops/operations and this is because they want to do more through automation as part of the role of the requirements of the SRE himself, so that you can run apps that can serve billions of requests but that are still handled by a few dozens of SREs."
|
||||
- "Suddenly the role for SRE gets democratized and distributed among different roles (developers included)".
|
||||
- "Debugging remains complex. Debugging in "a world of microservices is a very difficult task", requiring the identification of which specific part in a microservices deployment must be fixed"
|
||||
- Observability is also essential for diagnosing and debugging in order for SREs to "get to the root cause quickly enough so that you can feed that back to the development teams."
|
||||
- [linkedin.com: SRE: Key Insights-"Done the right way”](https://www.linkedin.com/pulse/sre-key-insights-done-right-way-shankar-muniyappa/)
|
||||
|
||||
<center>
|
||||
[](https://devops.com/sre-devops-cloud-native-server-cage-match/)
|
||||
|
||||
@@ -9,6 +9,7 @@
|
||||
- [Terraform and CI/CD](#terraform-and-cicd)
|
||||
- [OpenShift and Terraform](#openshift-and-terraform)
|
||||
- [Terraform Kubernetes Operator](#terraform-kubernetes-operator)
|
||||
- [Terraform and GKE](#terraform-and-gke)
|
||||
- [Terraform and AWS](#terraform-and-aws)
|
||||
- [Gruntwork](#gruntwork)
|
||||
- [Terraform Modules](#terraform-modules)
|
||||
@@ -96,6 +97,13 @@
|
||||
### Terraform Kubernetes Operator
|
||||
* [infoq.com: Managing Infrastructure from Kubernetes with the HashiCorp Terraform Operator](https://www.infoq.com/news/2020/04/terraform-operator-kubernetes/)
|
||||
|
||||
### Terraform and GKE
|
||||
* [learnk8s.io: Provisioning Kubernetes clusters on GCP with Terraform and GKE 🌟](https://learnk8s.io/terraform-gke) Fully automated dev, test, prod environments with Google Kubernetes Engine (GKE) + container-native load balancing? The guide goes into the details of how you can provision your infrastructure with Terraform and how you can route live traffic with the GKE Ingress controller. By the end Kristijan M. will teach you how you can have:
|
||||
- The creation of 3 environments (dev, test, prod) automated
|
||||
- A cluster that can handle live traffic with the GKE Ingress controller.
|
||||
- GKE Ingress enabled with container-native load balancing.
|
||||
- All source code and knowledge to build your own infra.
|
||||
|
||||
### Terraform and AWS
|
||||
* [Dzone: terraform and AWS](https://dzone.com/articles/terraform-and-aws)
|
||||
* [Dzone: terraform with AWS](https://dzone.com/articles/terraform-with-aws)
|
||||
|
||||
@@ -99,6 +99,7 @@ A simple extension to make indentation more readable
|
||||
|
||||
#### More Extensions (Blogs)
|
||||
* [Become a VS Code Ninja with these Extensions and Tools [2020]](https://dev.to/vikrantnegi/become-a-vs-code-ninja-with-these-extensions-and-tools-2020-1119)
|
||||
* [blog.logrocket.com: Top 10 VS Code extensions for 2021](https://blog.logrocket.com/top-10-vs-code-extensions-2021/)
|
||||
|
||||
#### Themes
|
||||
* [Material Icon Theme](https://marketplace.visualstudio.com/items?itemName=PKief.material-icon-theme) Material Design Icons for Visual Studio Code
|
||||
|
||||
Reference in New Issue
Block a user