|
You are here |
serverascode.com | ||
| | | | |
haylinmoore.com
|
|
| | | | | [AI summary] The article explains how to use GitHub Actions to deploy and manage Kubernetes deployments, including setting up service accounts, creating kubeconfig files, and implementing hitless deployments. | |
| | | | |
ghvsted.com
|
|
| | | | | Before a request is sent to the Kube-API server, some sort of client-side validation occurs. During this client-side validation, Kubectl validates requests and ensures that bad requests[ bad resource names, malformed image names, etc] do not go through to the API server. After the client-side validation, requests to the server are then authenticated. The authentication aims to ensure that the user making the request has the right to access that cluster. | |
| | | | |
pliutau.com
|
|
| | | | | Software Engineering Lead passionate about Backend, Cloud, DevOps, APIs, Kubernetes, Go. Currently leading an engineering team at Solsten. | |
| | | | |
nguyenhuythanh.com
|
|
| | | I named this post "Good" Practices, not "Best", since I believe that there is hardly a silver bullet that can be used to solve everything, technology oriented or not. The practices are good since they fit my case, and I hope that it would give you (or my future self) some useful insights. Monorepo Development Style Normally, we are used to Angular CLI's new command: ng new The style is normal for a "multi-repo" development style, where we split our projects into multiple repositories (Git repository to be precise). | ||