kubetail VS kops

There is an existing project named kubetail, which is quite popular 3.2K starts https://github.com/johanhaleby/kubetail

Kubetail

Thanos - Highly available Prometheus setup with long term storage capabilities. CNCF Sandbox project. https://thanos.io Prometheus - The Prometheus monitoring system and time series database. Grafana - The tool for beautiful monitoring and metric analytics & dashboards for Graphite, InfluxDB & Prometheus & More Kubetail - Bash script to tail Kubernetes logs from multiple pods at the same time Searchlight - Alerts for Kubernetes linkerd2 Monitoring Mixin for Grafana - Grafana dashboards for linkerd2 monitoring and can work in standalone (default) or in multi cluster setup kuberhaus - Kubernetes resource dashboard with node/pod layout and resource requests Kubernetes Job/CronJob Notifier - This tool sends an alert to slack whenever there is a Kubernetes cronJob/Job failure/success Argus - This tool monitors changes in the filesystem on specified paths

Kubetail is really nice: https://github.com/johanhaleby/kubetail.

Is this the gui version of kubetail?

The general problem of patching resource definitions that are not fully under your control has also been recognized for some time. This is true of default resources created and updated by cluster maintenance tools (e.g. kOps), or by public helm charts that you use to install common services and operators (e.g. nginx-ingress, cert-manager, and so on). High quality charts will allow you to override the configuration of important components such as service account references, but some simpler charts offer much less configuration.

The kops documentation is not very clear about this.

Very fast progress and great article with lots of useful information. I found myself nodding a lot having recently seen GitLab Dedicated https://docs.gitlab.com/ee/subscriptions/gitlab_dedicated/ being developed that had my similar challenges. I wonder what other people think of Kops https://kops.sigs.k8s.io/

note: I work with kube on a daily basis. All current clusters under my care use a managed backplane service though there are a number of small (3+ years-old) clusters that I still keep an eye on that were initialized using kops.

kOps with your own instances.

Companies run their own clusters (sometimes for cost reasons), using tools like kops, and kubeadm to set up their own clusters.

curl -Lo kops https://github.com/kubernetes/kops/releases/download/$(curl -s https://api.github.com/repos/kubernetes/kops/releases/latest | grep tag_name | cut -d '"' -f 4)/kops-linux-amd64 chmod +x kops sudo mv kops /usr/local/bin/

Kops is a cluster setup and management command line tool that deploys a Kubernetes cluster to AWS. It provides configuration abstractions such as manifest YAML files that facilitate node and components configuration. And like Ansible, it will provide dry-run capabilities and ensures idempotency of changing the nodes.