-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
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
Add How to start page, update developers guide cd and workflows pages #12
base: main
Are you sure you want to change the base?
Conversation
- **kaniko-s3-p-cwft**: Builds container tar-images with Kaniko and puts them to the S3. | ||
|
||
- **crane-s3-p-cwft** | ||
Tags and pushes built images from S3 to the Harbor container registry. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
AFAIR this step reads tar archive from blob storage (S3 in AWS case), builds image from it, and pushes it to the registry (Harbor). So this description is not 100% true. It's better to check with @vtsarfin
Also, please avoid using cloud provider specific service names, like S3 as it will be different on Azure and GCP.
Updates tags for unchanged services to keep them consistent with updated ones. | ||
|
||
- **version-changer-cwft** | ||
Updates the `version.yaml` file in the GitOps repository to reference the latest image versions. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For dev
environment only, as dev
considered to be starting point for promotion pipeline.
No description provided.