I have recently been researching open-source Kubernetes management platforms. The requirement is to manage hundreds of clusters on an intranet. The functional positioning is to assist operations and provide capabilities to the application layer, rather than serving end users directly. 1. Kubernetes Dashboard Project address: https://github.com/kubernetes/dashboard Tech stack: Angular + Go

Below is a list comparing Jenkins and Tekton: Feature Jenkins Tekton Programming language Java Golang Language for developing plugins Java Shell, Yaml Pipeline description language Groovy, Shell Yaml, Shell Plugin ecosystem Many plugins, LDAP, GitLab Lacking Number of plugins 1500+ 100+ Compatibility between plugins May conflict, cannot be upgraded freely Fully compatible Secondary development Wrapping the API Composing Tasks High availability Integrates Gearman, master-slave mode Relies on Kubernetes’ high availability Concurrent build scale per instance A few hundred concurrent builds Relies on Kubernetes’ Pod management capability, so it can be very large Data storage Local disk Etcd Supports automatic triggering Yes Yes Has commercial support No No

Helm 3 is finally released. We can say goodbye to Tiller, but Helm 3’s changes do not stop there. Let’s continue exploring the other changes. 1. Saying Goodbye to Tiller Removing Tiller in Helm 3 was a good decision. But to understand why it is good, we first need to understand the background that produced Tiller.

1. Differences Between Python 2 and 3 Feature \ Version Python 2 Python 3 print as a function print"abc" print(“abc”) Unified class Old-style and new-style classes New-style classes only Floating-point division 1/2=0 1/2=0.5 String formatting %, Format Format,% xrange replaces range xrange range long renamed to int Long,int Int Package imports Relative imports Absolute imports Source file encoding Ascii utf8 The official Python recommendation is strongly in favor of learning Python 3 directly, since Python 2 is only maintained through 2020.