大三角帆:如何将自定义材料放入大三角帆吊舱中,以便能够将其部署到空中?

时间:2019-03-01 15:37:55

标签: spinnaker spinnaker-halyard

我想为三角帆提供custom BOM (Bill of Materials),以便我可以根据需要配置仓库。我是k8,头盔和大三角帆的新手,请务必阅读文档,有些事情尚不完全清楚该怎么做...

问题

我无权访问gcs存储,也无权直接访问外部存储库。因此,我需要相应地配置artifactSources

根据the docu,我想我应该提供一种自定义的Bom,以便从文件系统中读取它们-因此在容器spinnaker-spinnaker-halyard-0

我的步骤

准备kubernetes集群

我会像头盔一样进行初始部署

helm install stable/spinnaker --name=spinnaker --namespace=spinnaker -f values.yml

连接到spinnaker-spinnaker-halyard-0窗格并运行

$ kubectl.exe exec -it spinnaker-spinnaker-halyard-0 -n spinnaker bash

部署大三角帆

根据文档herehere,我会做类似的事情

$ hal config version edit --version local:1.11.6
$ hal deploy apply

显然失败的原因是没有本地Bom文件

Problems in Global:
! ERROR Unable to retrieve the Spinnaker bill of materials for
  version "local:1.11.6": /home/spinnaker/.hal/.boms/bom/1.11.6.yml (No such file
  or directory)

- Failed to prep Spinnaker deployment

问题:如何提供自定义BOM?

根据文档记录,预计Bom将位于特定的目录和结构${HALCONFIG_DIR}/.boms/boms/${VERSION}.yml

那我该如何获取自定义POM?当我看着helm-chart时,我看不到(或不明白)我该怎么做,例如通过additional-config-maps

1 个答案:

答案 0 :(得分:0)

我找到了一种方法,但是它是在spinnaker-spinnaker-halyard容器中手动完成的。我敢肯定有更好的方法...

我将自定义Bom作为additionalConfigMap添加到values.yml文件

...
  additionalConfigMaps:
    create: true
    data:
      # https://storage.googleapis.com/halconfig/bom
      bom_1.12.4.yml: |
        version: 1.12.4
        timestamp: '2019-03-01 08:06:24'
        services:
          echo:
            version: 2.3.1-20190214121429
            commit: 5db9d437ca7f2fa374dcada17f77bbbb2965bd67
          clouddriver:
            version: 4.3.4-20190301030607
            commit: b5539c47aad309e24428abb8f8303aff45323b43
          deck:
            version: 2.7.4-20190228030607
            commit: dccdd730886a6beb0388e3622581d8da1ed8edbb
          fiat:
            version: 1.3.2-20190128153726
            commit: daf21b24330a5f22866601559aa0f7ac99590274
          front50:
            version: 0.15.2-20190222161456
            commit: 3105e86b8c084ad6ad78507e3a5e5a427f290b99
          gate:
            version: 1.5.2-20190301030607
            commit: b238ab993ab25381ce907260879548ed74a4953f
          igor:
            version: 1.1.1-20190213190226
            commit: 63d06a5c5d55f07443dd60a81035b35cf96238e7
          kayenta:
            version: 0.6.1-20190221030610
            commit: 81d906bf8307143f40fe88f8554baa318de25ef1
          orca:
            version: 2.3.1-20190220030610
            commit: bad45e78566449117b678a3317552cf53d0dd14e
          rosco:
            version: 0.9.0-20190123170846
            commit: 42f81a2501de6d40676d47661579a6106b5c3e8a
          defaultArtifact: {}
          monitoring-third-party:
            version: 0.11.2-20190222030609
            commit: 232c84a8a87cecbc17f157dd180643a8b2e6067a
          monitoring-daemon:
            version: 0.11.2-20190222030609
            commit: 232c84a8a87cecbc17f157dd180643a8b2e6067a
        dependencies:
          redis:
            version: 2:2.8.4-2
          consul:
            version: 0.7.5
          vault:
            version: 0.7.0
        artifactSources:
          debianRepository: https://nexus.intra/repository/spinnaker-releases/
          dockerRegistry: nexus.intra:5000/spinnaker-marketplace
          googleImageProject: marketplace-spinnaker-release
          gitPrefix: https://scm.intra/scm/SPIN/repos

然后将自定义Bom链接到halyard容器中,配置版本并运行部署

mkdir -p ~/.hal/.boms/bom
ln -s /opt/halyard/additionalConfigMaps/bom_1.12.4.yml ~/.hal/.boms/bom/1.12.4.yml
hal config version edit --version local:1.12.4
hal deploy apply