Deployment Targets

Last updated 2020-01-23T23:57:56.3153748+00:00

With Octopus Deploy, you can deploy software to Windows servers, Linux servers, Microsoft Azure, AWS, Kubernetes Clusters, Cloud Regions, or an Offline Package Drop. Regardless of where you're deploying your software, these machines and services are known as your deployment targets.

You can manage your deployment targets by navigating to Infrastructure ➜ Deployment Targets in the Octopus Web Portal:

From the Deployment Targets tab you can add new deployment targets, disable or delete deployment targets, check on the status of your targets, and run health checks.

Adding Deployment Targets

Deployment targets are added in different ways, depending on the type of target you are adding and how the target will communicate with the Octopus Deploy server. For instructions, see:

Accounts

In addition to the deployment targets above, you may also need to configure accounts to use in conjunction with your infrastructure during your deployments.

You can configure the following accounts:

Target Roles

Before you can deploy software your deployment targets, you need to tag them with target roles. This ensures you deploy the right software to the right deployment targets. Deployment targets can have multiple roles, but they must have at least one. Typical target roles include:

web-server
app-server
db-server

Using target roles means the infrastructure in each of your environments doesn't need to be identical. For instance, in the test environment, you might be using a single VM to test all of your software, and so you tag that VM with all of the target roles you use in your deployment process. However, in the production environment you might have one or more dedicated deployment targets per functional role, for instance, one deployment target for the database server which you would tag with the target role db-server, and another deployment target that performs the role of web server and is tagged with the target role web-server.

Deployment targets can have more than one role, and more than one deployment target can have the same role.

As you decide on the target roles for your infrastructure, try to name the target roles based on the function the deployment targets will serve rather than describing some attribute of the deployment targets.

Creating Target Roles

Roles are created and saved in the database as soon as you assign them to a deployment target.

Decide on the naming convention you will use before creating your first target role as it's not possible to change the case after the role has been created, for instance, all lowercase to camel case.

Register a deployment target or click on an already registered deployment target and go to Settings.
In the Target Roles field, enter the target role you'd like to use (no spaces).
Save the target settings.

The role has been created and assigned to the deployment target and can be added to other deployment targets.

You can check all the roles assigned to your deployment targets from the Infrastructure tab.

Dynamic Infrastructure

You can use scripts to create Azure Service Principal Accounts, Azure Web Apps, Azure Service Fabric, Azure Cloud Services and Kubernetes targets.

Learn about Managing resources with scripts.

Octopus Deploy Documentation