harbor-boshrelease
harbor-boshrelease copied to clipboard
CFF BOSH Release for Project Harbor
We ran into an issue while deploying the harbor container registry using s3 as the storage backend. Our S3 buckets are locked down to allow only authorized sts/iam profiles to...
``` releases: - name: harbor-container-registry version: 1.6.0 sha1: 5bb63d9b1cac2ae24e601d28c057af7dcb3abe8b url: https://storage.googleapis.com/harbor-bosh-releases/harbor-container-registry-1.6.2.tgz ``` there is a trouble between 1.6.0 version and tgz 1.6.2
There are lots of sed command to render config file, these commands will cause problem when reconfigure because these operation can not be revert For example in pre-start.erb ` sed...
**harbor boshrelease should support HA deployment structure, main idea:** * Remove docker-compose out of harbor boshrelease, directly run services on docker via images * Split harbor-app job into functional service...
We should setup CI to verify the merging code and make sure there is alway a workable bsohrelease existing
haproxy will be treated as internal LB, work together with keepalived this job can refer haproxy job in cf release
there might be different envs need to be verified: vSphere GCP AWS AZURE?