Per review feedback, create separate manifest files for different deployment targets instead of using templated values: - cozystack-operator.yaml (Talos): hardcoded localhost:7445 (KubePrism) - cozystack-operator-generic.yaml: reads from cozystack-operator-config ConfigMap (user must create before applying) - cozystack-operator-hosted.yaml: no env override (uses in-cluster SA) This keeps installation flow clean - users apply the manifest matching their deployment target without needing to modify original files. Build system updated to generate all three variants. Co-Authored-By: Claude <noreply@anthropic.com> Signed-off-by: Aleksei Sviridkin <f@lex.la>
16 lines
844 B
Bash
Executable file
16 lines
844 B
Bash
Executable file
#!/bin/bash
|
|
set -xe
|
|
|
|
version=${VERSION:-$(git describe --tags)}
|
|
|
|
gh release upload --clobber $version _out/assets/cozystack-crds.yaml
|
|
gh release upload --clobber $version _out/assets/cozystack-operator.yaml
|
|
gh release upload --clobber $version _out/assets/cozystack-operator-generic.yaml
|
|
gh release upload --clobber $version _out/assets/cozystack-operator-hosted.yaml
|
|
gh release upload --clobber $version _out/assets/metal-amd64.iso
|
|
gh release upload --clobber $version _out/assets/metal-amd64.raw.xz
|
|
gh release upload --clobber $version _out/assets/nocloud-amd64.raw.xz
|
|
gh release upload --clobber $version _out/assets/kernel-amd64
|
|
gh release upload --clobber $version _out/assets/initramfs-metal-amd64.xz
|
|
gh release upload --clobber $version _out/assets/cozypkg-*.tar.gz
|
|
gh release upload --clobber $version _out/assets/cozypkg-checksums.txt
|