Conversation
支持制品配置文件自定义harbor版本， 支持创建仓库时自定义harbor版本。 不配置时走之前逻辑
|
This PR has multiple commits, and the default merge method is: squash. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
|
Adding the "do-not-merge/release-note-label-needed" label because no release-note block was detected, please follow our release note process to remove it. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: gjing1st The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
Welcome @gjing1st! It looks like this is your first PR to kubesphere/kubekey 🎉 |
kubesphere-prow
bot
added
the
size/L
|
|
新版kk （feature-gitops分支）可以解决你的问题 |
2 participants
● kk特性：kk不支持自定义harbor版本，manifest中定义的harbor版本无效，每个kk版本使用代码中的默认harbor版本。
● 导致的结果：老版本kk安装2.5.3，在漏洞扫描时出现Harbor 访问控制错误漏洞和弱口令漏洞。新版本kk安装2.10.1版本，该版本不再支持插件形式安装Helm Charts。如果自己项目使用了helm部署，需要使用Harbor中的Helm Charts，而2.10.1将无法使用，只能自己手动修复漏洞或者更改版本。
由于我司业务不同，需要频繁离线部署KubeSphere，每次部署KubeSphere时也需要部署Harbor，每次手动更改harbor，太过麻烦。于是修改KubeKey，使kk安装2.7.4(2.8版本后不再支持helm)版本Harbor。