In this page, you will deploy an application to your platform in a simple way.
1-1. Edit configuration files of one platform under /src/deploy/ in your cloned repository as bellow.
Note
Each platform has a deployment config file (app.pipecd.yaml) + platform specific files.
- For Kubernetes:
- You will run a helloworld service.
- Use
kubernetes/simple/. You do not need to edit.
- For Google Cloud Run:
- You will run a helloworld service.
- Use
cloudrun/simple/. You do not need to edit.
- For Amazon ECS:
- You will run an nginx service.
- Edit
ecs/simple/as below.app.pipecd.yaml: EdittargetGroupArn.servicedef.yaml: Editcluster,securityGroups, andsubnets.taskdef.yaml: EditexecutionRoleArn.
- For AWS Lambda:
- You will create a function using a simple Python source code package.
- Edit
lambda/simple/as below.- Build the function package: Run
./build.sh(Linux/Mac) orbuild.bat(Windows) - Upload the generated zip file to your S3 bucket
function.yaml: Editrole,s3Bucket, ands3Key
- Build the function package: Run
- For Terraform:
- You will generate a file on local.
- Edit
terraform/simple/as below.main.tf: Editpathandfilename.
1-2. Commit and push the changes to remote.
2-1. Go to the applications page. http://localhost:8080
2-2. Click + ADD.
2-3. Enter values and click SAVE->SAVE.
Piped: Your PipedPlatform Provider: The platformApplication: The application you configured in 1.
2-4. If successful, you will see the dialog like the following image.
3-1. Go to the deployments page. http://localhost:8080/deployments
3-2. Wait until a new deployment automatically appears. Then click it to see details.
Note
You do NOT need to invoke a deployment by yourself since your Piped automatically starts it. This is GitOps.
3-3. Wait until the status becomes SUCCESS/FAILURE. If it shows FAILURE, check the log in the page.
3-4. When the status becomes SUCCESS, the deloyment is successfully finished.
3-5. Check your platform (Kubernetes cluster, cloud console, etc.) to confirm the result.
4-1. Edit the config file you deployed. (e.g. Change the image tag, sizing, etc.)
4-2. Commit and push the change to remote.
4-3. Go to the deployments page again. http://localhost:8080/deployments
4-4. A new deployment will start in a few minutes.





