14 lines
593 B
Markdown
14 lines
593 B
Markdown
|
|
# registry-deploy-on-push
|
||
|
|
|
||
|
|
This scenario verifies the Cloudly registry to Coreflow deploy-on-push path.
|
||
|
|
|
||
|
|
Assertions:
|
||
|
|
|
||
|
|
- Cloudly starts with isolated MongoDB and S3 helpers.
|
||
|
|
- Coreflow authenticates with the cluster machine token.
|
||
|
|
- Docker login and push to Cloudly's OCI registry work.
|
||
|
|
- Cloudly records the pushed image digest and pushes config to connected Coreflow.
|
||
|
|
- Coreflow creates the workload service from the registry-backed image.
|
||
|
|
- Coretraffic receives the route config and serves HTTPS traffic to the workload.
|
||
|
|
- Re-pushing `latest` with a new digest recreates the Docker service.
|