k9s | 🐶 Kubernetes CLI To Manage Your Clusters In Style | Identity Management library

I've tried to run the following commands as part of a bash script runs in BashOperator:

When there's more than one search result from / filter command, how do you navigate to next item? Basically I'm looking for F3 (next search result) equivalent in k9s. Commands listed here does not seem to include what I'm looking for...

Summary in one sentence

I want to deploy Mattermost locally on a Kubernetes cluster using Minikube

Steps to reproduce

I used this tutorial and the Github documentation:

• https://mattermost.com/blog/how-to-get-started-with-mattermost-on-kubernetes-in-just-a-few-minutes/
• https://github.com/mattermost/mattermost-operator/tree/v1.15.0

1. To start minikube: minikube start --kubernetes-version=v1.21.5
2. To start ingress; minikube addons enable ingress
3. I cloned the Github repo with tag v1.15.0 (second link)
4. In the Github documentation (second link) they state that you need to install Custom Resources by running: kubectl apply -f ./config/crd/bases
5. Afterwards I installed MinIO and MySQL operators by running: make mysql-minio-operators
6. Started the Mattermost-operator locally by running: go run .
7. In the end I deployed Mattermost (I followed step 2, 7 and 9 from the first link)

Observed behavior

Unfortunately I keep getting the following error in the mattermost-operator:

I use k9s to access the bash from the pod where I keep the logs of my project.

Reading the logs with a cat is annoying, so I want to send them to my pc.

How can I do this?

I followed the first possible solution in this page: Checking kubernetes pod CPU and memory

I tried the command:

kubectl exec pod_name -- /bin/bash

But it didn't work therefore I tried the command:

kubectl exec -n [namespace] [pod_name] -- cat test.log

I know this because when I run the command:

kubectl get pods --all-namespaces | grep [pod_name]

This is what I see:

POD_NAME

But I get this error message:

As beginener, I have tried k9s and kubernetes 'kubectl top nodes',for the cpu and memory usage and values are matched.Meanwhile I tried with prometheus UI, with 'avg(container_cpu_user_seconds_total{node="dev-node01"})' and 'avg(container_cpu_usage_seconds_total{node="dev-node01"})' for dev-node01. I cant get matching values.Any help will be appreciated as I am beginner.please any help would be appreciated.

Recently I have built several microservices within a k8s cluster with Nginx ingress controller and they are working normally.

When dealing with communications among microservices, I attempted gRPC and it worked. Then I discover when microservice A -> gRPC -> microservice B, all requests were only occurred at 1 pod of microservice B (e.g. total 10 pods available for microservice B). In order to load balance the requests to all pods of microservice B, I attempted linkerd and it worked. However, I realized gRPC sometimes will produce internal error (e.g. 1 error out of 100 requests), making me changed to using the k8s DNS way (e.g. my-svc.my-namespace.svc.cluster-domain.example). Then, the requests never fail. I started to hold up gRPC and linkerd.

Later, I was interested in istio. I successfully deployed it to the cluster. However, I observe it always creates its own load balancer, which is not so matching with the existing Nginx ingress controller.

Furthermore, I attempted prometheus and grafana, as well as k9s. These tools let me have better understanding on cpu and memory usage of the pods.

Here I have several questions that I wish to understand:-

1. If I need to monitor cluster resources, we have prometheus, grafana and k9s. Are they doing the same monitoring role as service mesh (e.g. linkerd, istio)?
2. if k8s DNS can already achieve load balancing, do we still need service mesh?
3. if using k8s without service mesh, is it lag behind the normal practice?

Actually I also want to use service mesh every day.

I have an ordinary

I am having some issues with a fairly new cluster where a couple of nodes (always seems to happen in pairs but potentially just a coincidence) will become NotReady and a kubectl describe will say that the Kubelet stopped posting node status for memory, disk, PID and ready.

All of the running pods are stuck in Terminating (can use k9s to connect to the cluster and see this) and the only solution I have found is to cordon and drain the nodes. After a few hours they seem to be being deleted and new ones created. Alternatively I can delete them using kubectl.

They are completely inaccessible via ssh (timeout) but AWS reports the EC2 instances as having no issues.

This has now happened three times in the past week. Everything does recover fine but there is clearly some issue and I would like to get to the bottom of it.

How would I go about finding out what has gone on if I cannot get onto the boxes at all? (Actually just occurred to me to maybe take a snapshot of the volume and mount it so will try that if it happens again, but any other suggestions welcome)

Running kubernetes v1.18.8