Explore >> Select a destination
|
You are here 
|
rguske.github.io | ||
| | | | |
arveknudsen.com
|
|
| | | | | In my previous blog post I showed how to use the Kops tool to create a production ready Kubernetes cluster on Amazon Web Services (AWS). In this follow-up post I will show how to install Elasticsearch and its graphical counterpart Kibana in the cluster, in order to be able to collect and store logs from your cluster and search/read them. We will also install Fluentd as this component is responsible for transmitting the standard Kubernetes logs to Elasticsearch. | |
| | | | |
nodogmablog.bryanhogan.net
|
|
| | | | | In my previous post I showed how to run a single instance of a Web API application in Kubernetes using Minikube. In this post, I will show you how to deploy the same application, but this time there will be 3 instances of the application, with a load balancer routing traffic to each of the instances. | |
| | | | |
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)." ?? | |
| | | | |
benbrougher.tech
|
|
| | | How to use microk8s to create an ingress using MetalLB and the NGINX ingress controller | ||
