Explore >> Select a destination
|
You are here 
|
vegard.blog.engen.priv.no | ||
| | | | |
api7.ai
|
|
| | | | | API7 Enterprise integrates with Kubernetes Service Discovery to help users proxy applications deployed in the Kubernetes cluster conveniently. | |
| | | | |
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)." ?? | |
| | | | |
brunoscheufler.com
|
|
| | | | | Welcome back to the short series about getting started with Kubernetes, the practical way! If you haven't read the first post on provisioning a cluster and haven't set up your first cluster yet, please do that first and come back here. If you're running your cluster on Google's Kubernetes Engine, chances are that integrated metrics and services like Stackdriver are already great for monitoring your Kubernetes cluster, in that case, you might not actually need to deploy the following application.... | |
| | | | |
rolisz.ro
|
|
| | | I often need to set up a VM with a server to run some ML models. While I could package things in Docker and deploy them like that, whenever possible, I like to do things more directly, using systemd services. To create a systemd service, create a file called /etc/ | ||
