We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
在安装阶段完成后,把安装过程配置参数复制一份到 ~/.hgctl/profiles/install.yaml , 升级从 ~/.hgctl/profiles/install.yaml 读取profile配置
如果helm 安装有 values.yaml 参数文件,可以手动传入values.yaml 文件 ,支持 -f 参数
``` hgctl install/upgrade --set profile=k8s -f values.yaml ```
安装完成后profile 保存位置调整 : 如果在k8s下安装, 保存在 k8s configmap 下, 本地docker安装还是保存在 ~/.hgctl/profiles/目录下, 当升级时候(hgctl upgrade ) 聚合列出本地 ~/.hgctl/profiles 和 k8s configmap 所有profile,如果有多个 profiles 让用户选择升级哪个profiles。
升级时通过 helm 命令 读取到 helm release 信息,自动转换成 profile, 参数支持 --from-helm
``` hgctl upgrade --from-helm ```
#229
The text was updated successfully, but these errors were encountered:
sjcsjc123
2456868764
Successfully merging a pull request may close this issue.
Why do you need it?
How could it be?
在安装阶段完成后,把安装过程配置参数复制一份到 ~/.hgctl/profiles/install.yaml , 升级从 ~/.hgctl/profiles/install.yaml 读取profile配置
如果helm 安装有 values.yaml 参数文件,可以手动传入values.yaml 文件 ,支持 -f 参数
安装完成后profile 保存位置调整 : 如果在k8s下安装, 保存在 k8s configmap 下, 本地docker安装还是保存在 ~/.hgctl/profiles/目录下, 当升级时候(hgctl upgrade ) 聚合列出本地 ~/.hgctl/profiles 和 k8s configmap 所有profile,如果有多个 profiles 让用户选择升级哪个profiles。
升级时通过 helm 命令 读取到 helm release 信息,自动转换成 profile, 参数支持 --from-helm
Other related information
#229
The text was updated successfully, but these errors were encountered: