stern VS powerlevel10k

deploy: stage: deploy image: alpine/k8s:1.29.1 variables: NAMESPACE: $CI_COMMIT_REF_SLUG before_script: # init namespace - kubectl config use-context $KUBE_CONTEXT - kubectl create namespace $NAMESPACE || true # download tools - curl --show-error --silent --location https://github.com/stern/stern/releases/download/v1.22.0/stern_1.22.0_linux_amd64.tar.gz | tar zx --directory /usr/bin/ stern && chmod 755 /usr/bin/stern && stern --version - curl --show-error --silent --location https://github.com/kubernetes/kompose/releases/download/v1.32.0/kompose-linux-amd64 -o /usr/local/bin/kompose && chmod a+x /usr/local/bin/kompose && kompose version # show logs asynchronously. Timeout to avoid hanging indefinitely when an error occurs in script section - timeout 1200 stern -n $NAMESPACE "app-" --tail=0 --color=always & # in background, tail new logs if any (current and incoming) pod with this regex as name - timeout 1200 kubectl -n $NAMESPACE get events --watch-only & # in background, tail new events in background script: # first delete CrashLoopBackOff pods, polluting logs - kubectl -n $NAMESPACE delete pod `kubectl -n $NAMESPACE get pods --selector app.kubernetes.io/component=$MODULE | awk '$3 == "CrashLoopBackOff" {print $1}'` || true # now deploying - kompose convert --out k8s/ - kubectl apply -n $NAMESPACE -f k8s/ - echo -e "\e[93;1mWaiting for the new app version to be fully operational...\e[0m" # waiting for successful deployment - kubectl -n $NAMESPACE rollout status deploy/app-db - kubectl -n $NAMESPACE rollout status deploy/app-back - kubectl -n $NAMESPACE rollout status deploy/app-front # on any error before this line, the script will still wait for these threads to complete, so the initial timeout is important. Adding these commands to after_script does not help - pkill stern || true - pkill kubectl || true after_script: # show namespace content - kubectl config use-context $KUBE_CONTEXT - kubectl -n $NAMESPACE get deploy,service,ingress,pod

The old repo is dead

node-and-git: image: node:18.10-alpine before_script: - apk --no-cache add git kubectl-and-stern: image: alpine/k8s:1.22.13 before_script: # install stern - curl --show-error --silent --location https://github.com/stern/stern/releases/download/v1.22.0/stern_1.22.0_linux_amd64.tar.gz | tar zx --directory /usr/bin/ stern && chmod 755 /usr/bin/stern playwright-and-kubectl: image: mcr.microsoft.com/playwright:v1.35.1-focal before_script: # install kubectl - curl --show-error --silent --location --remote-name https://storage.googleapis.com/kubernetes-release/release/v1.25.3/bin/linux/amd64/kubectl && chmod +x ./kubectl && mv ./kubectl /usr/local/bin/

I'll add stern (https://github.com/stern/stern) to that - follow logs from multiple pods easily.

Multi pod and container log tailing for Kubernetes https://github.com/stern/stern

stern v1.22.0

Link to GitHub Repository

If you are using Kubernetes, I highly recommend using https://github.com/stern/stern

Stern: https://github.com/stern/stern for log streaming

That’s the minimum terminal setup. You can modify the look and add plugins such as autocompletion to your terminal by installing ohmyzsh and using themes such as powerlevel10k. I am already using them.

I used ohmyzsh with powerlevel10k/powerlevel10k[0] for years though recently i've settled on fish [1]

[0] https://github.com/romkatv/powerlevel10k

I had just gone through a fun tutorial for setting up oh-my-zsh with a nice color scheme from iterm2colorschemes.com and a decent prompt and I was wondering: can I make my oblique strategy look nice? how can you actually use the colors from your scheme in the output in your cli?

A more robust way to do this would be to add simple wrappers that clone any external Zsh plugins you use regularly and store them in your own $ZSH_CUSTOM. For example, you say you like Powerlevel10k, so make that an OMZ plugin:

Looks like PowerLevel10 theme for Zsh shell

git clone --depth=1 https://github.com/romkatv/powerlevel10k.git ${ZSH_CUSTOM:-$HOME/.oh-my-zsh/custom}/themes/powerlevel10k

Am i the only one who feels fish is not worth it despite of hype? Don't get me wrong. I think that fish is really good shell.

BUT...

After adding the following plugins to zsh(before you chime in, it's just adding these lines,not anything configuring much. also it auto bootstraps on new install), I found out that fish is no where near configured zsh.

1) https://github.com/zdharma-continuum/zinit (plugin manager)

2) https://github.com/zdharma-continuum/fast-syntax-highlightin...

3) https://github.com/zdharma-continuum/history-search-multi-wo...

4) https://github.com/zsh-users/zsh-autosuggestions

5) https://github.com/zsh-users/zsh-completions

6) https://github.com/Aloxaf/fzf-tab

7) any good shell prompt generator like https://github.com/romkatv/powerlevel10k

For example, I use fzf integration for tab completion. Fish's fzf integration is nowhere as good as that of zsh's. Also, posix compat and almost bash compat of zsh is plus.

I acknowledge that zsh isn't perfect shell either and I have tried and failed few times in past to switch to fish. If you provide me compelling reason/s to switch to fish, I am all ears.

To build upon that concept, you can even have your shell prompt display a symbol if you have a backgrounded job. I use https://github.com/romkatv/powerlevel10k and the background_jobs handles it for me.

I also use PowerLevel10k. Themes up your zsh to make it look nice, pretty customisable.

start here: https://github.com/romkatv/powerlevel10k