Azure Service Fabric Cluster deployment targets allow you to reference existing Service Fabric Cluster apps that are available in your Azure subscription, that you can then reference by role during deployments.
This new target type was introduced in Octopus 2018.5. You can read more about all the new PaaS targets in our blog.
The Service Fabric SDK must be installed on the Octopus Server. If this SDK is missing, the step will fail with an error: "Could not find the Azure Service Fabric SDK on this server.".
PowerShell script execution may also need to be enabled. See the "Enable PowerShell script execution" section from the above link for more details.
After the above SDK has been installed, you will need to restart your Octopus service before the changes will take effect.
You will need to create a Service Fabric cluster (either in Azure, on-premises or in other clouds). Octopus needs an existing Service Fabric cluster to connect to in order to reference it as a deployment target.
To learn more about App Services, the Azure team provide useful documentation on Service Fabric that can help you get started.
Creating Service Fabric Cluster Targets
Once you have a Service Fabric Cluster application setup within your Azure subscription, you are then ready to map that to an Octopus deployment target.
To create an Azure Service Fabric Cluster target within Octopus:
- Go to Infrastructure > Deployment Targets > Add Deployment Target.
- Select Azure Service Fabric Cluster from the list of available targets and click Next.
- Fill out the necessary fields, being sure to provide a unique role that clearly identifies your Azure Service Fabric Cluster target.
- After clicking Save, your deployment target will be added and go through a health check to ensure Octopus can connect to it.
- If all goes well, you should see your newly created target in your Deployment Targets list, with a status of Healthy.
Deploying to Service Fabric Targets
See our documentation about this topic
If your Azure Service Fabric Cluster target is not completing a health check successfully, you may need to check that your Octopus Server can communicate with Azure. If your Octopus Server is behind a proxy or firewall, you will need to consult with your Systems Administrator to ensure it is able to communicate with Azure.
Alternatively, it could be the security settings of your Service Fabric Cluster denying access. Our deployments documentation discusses the various security modes of Service Fabric in greater detail.