/explore
|
You are here 
|
external-secrets.io | ||
| | | | |
particule.io
|
|
| | | | | [AI summary] A technical guide demonstrating how to integrate AWS Secrets Manager with Kubernetes using the Secrets Store CSI driver to securely manage and inject application credentials. | |
| | | | |
developer-friendly.blog
|
|
| | | | | What does the immutable flag on External Secrets operator entails and how it can affect your secret management in the Kubernetes cluster. | |
| | | | |
blog.nuculabs.de
|
|
| | | | | Hi ?, In this article I will talk about how to authenticate your applications to the Kubernetes API via the service accounts feature. Citing the Kubernetes docs, a service account for a pod: "provides an identity for processes that run in a Pod. When you (a human) access the cluster (for example, using kubectl), you are authenticated by the apiserver as a particular User Account (currently this is usually admin, unless your cluster administrator has customized your cluster). Processes in containers inside pods can also contact the apiserver. When they do, they are authenticated as a particular Service Account (for example, default)." | |
| | | | |
blog.nobugware.com
|
|
| | | Following my earlier post about Traefik 2 and Kubernetes, here are some advanced configuration examples and a full yaml example at the end of this post: Protecting a route with a password Create an htpasswd file named users for a user admin htpasswd -c users admin Use kubectl to create the secret (easier for multi lines file). kubectl create secret generic admin-authsecret --from-file=users Create a middleware for authentication: apiVersion: traefik.containo.us/v1alpha1 kind: Middleware metadata: name: a... | ||
