Skip to main content

Deploy an app

Open Workloads > Applications and select Deploy application. The wizard walks you through each step; these are the ones to fill in.

  1. Name the app and pick the cluster. Type latency-app and choose the cluster it should run on.

    Open zoom view

    Deploy application, Name and cluster: application name latency-app, target cluster eks-prod

    Deploy application, Name and cluster: application name latency-app, target cluster eks-prodDeploy application, Name and cluster: application name latency-app, target cluster eks-prod

  2. Choose a profile. A profile holds the settings your apps share on a cluster. The first time, select Create New and call it latency-app-profile; later apps can reuse it.

    Open zoom view

    Deploy application, Profile: Create New, profile name latency-app-profile, Basic availability tier

    Deploy application, Profile: Create New, profile name latency-app-profile, Basic availability tierDeploy application, Profile: Create New, profile name latency-app-profile, Basic availability tier

  3. Say what to run. Choose Container image and enter astropulseinc/latency-app, tag v1.1.2 and port 8080. Select Validate, and AstroPulse checks that the image and tag exist.

    Open zoom view

    Deploy application, Image: astropulseinc/latency-app, tag v1.1.2, port 8080, source validation Valid

    Deploy application, Image: astropulseinc/latency-app, tag v1.1.2, port 8080, source validation ValidDeploy application, Image: astropulseinc/latency-app, tag v1.1.2, port 8080, source validation Valid

  4. Give it an address. Under External access, choose Serve on your domain and type latency-app. AstroPulse issues the HTTPS certificate and, with DNS Automation on, creates the DNS record. While DNS Automation is in dry run, this step says so and which record to point yourself.

    Open zoom view

    Deploy application, Access: served on example.com, subdomain latency-app, served at latency-app.example.com; a notice that DNS Automation is in dry run and writes no DNS records; TLS mode Add-on default

    Deploy application, Access: served on example.com, subdomain latency-app, served at latency-app.example.com; a notice that DNS Automation is in dry run and writes no DNS records; TLS mode Add-on defaultDeploy application, Access: served on example.com, subdomain latency-app, served at latency-app.example.com; a notice that DNS Automation is in dry run and writes no DNS records; TLS mode Add-on default

  5. Check and deploy. Review runs a dry run of the whole deployment first. When it passes, select Deploy.

    Open zoom view

    Deploy application, Review: the manifest to be deployed and Dry run passed

    Deploy application, Review: the manifest to be deployed and Dry run passedDeploy application, Review: the manifest to be deployed and Dry run passed

Within a minute or two the app shows Running and answers at https://latency-app.example.com. Its Spend and Security cards fill in after the first hour and the first scan.

NovaNova
Deploy astropulseinc/latency-app:v1.1.2 as latency-app, on port 8080, at latency-app.example.com.
Ask Nova

It shows the plan and deploys when you approve.

Next​

Scan for vulnerabilities