but it is different in a lot of ways. The main difference is that Flux uses the Helm Golang [2.6] package. Flux doesn’t render the YAML, but instead deals with Helm directly. This design gives users a familiar the basis of most structures and examples in this chapter. Helm Helm has become the de facto package manager for Kubernetes. If you’ve worked on a Kubernetes cluster previously, there is a good chance patching framework, Helm was built from the ground up as a templating engine. It also acts as a package manager, like DNF or apt-get. This means you can start treating Kubernetes as your “cloud operating

~]# unzip fit2cloud_tools.zip  安装 Python 依赖包 [root@admin-node ~]# cd /opt/fit2cloud-tools/rpm-package [root@admin-node ~]# sh python-paramiko.sh  修改部署配置文件 [root@admin-node ~]# cd /opt/fit2cloud-tools nginx-vip=1.6.6.6 #cmp-node ip and passwd cmp-master=1.7.7.7 cmp-backup=1.8.8.8 #cmp-package fit2cloud_package=/opt/fit2cloud-cmp-**.tar.gz  执行安装命令 usage： python Install-Tools.py -H [ ]

console Great for enterprise teams, not as good for independent applications Kubernetes focused package manager based on templates Templates enable prescribed customization, more difficult to customize

templated to make them customizable based on the requirement. Nowadays, it is viewed as the de facto package manager for the Kubernetes ecosystem. It acts just like APT/YUM/RPM packet manager but for Kubernetes

repository is scanned for changes. GitOps and Helm do not always work well together Helm is the package manager for Kubernetes and is typically seen as the de-facto standard for deploying 3rd party applications