Congratulations, you’re set up to iterate on your Ship application. By now you’ve hopefully got a good grasp on the basics of using ship, and its time to dig into the features that Ship exposes for packaging your application.
The goal of this chapter is to help you transition into using the Technical Deep Dives and Reference Docs as you expand your starter project into a production-ready Ship application. Topics covered are:
- Docker Image Management and Airgap
- Deliver end-to-end Infrastructure with Terraform
- Support and Troubleshoot your Appliation
- Features for Cluster Operators
- Explore Reference Docs
Learn about how to pull images from the Replicated Private Registry, and bundle image archives for deployment into airgapped clusters.
Learn about how to allow end customers to opt-in to a more black-box appliance experience by bundling Terraform manifests and having Ship manage infrastructure provisioning and state. Distribute a hands-off, managed instance of your application into a private cloud with the same workflow and manifests you use for delivering into opinionated, existing cluster environments.
One of the biggest challenges when distributing on-prem software is troubleshooting applications on infrastructure you don’t control. Replicated knows this problem well, and we’ve built powerful general-purpose tools for collecting and analyzing information from on-prem instances of your application.
This guide focuses on application distributors, but there are a lot of Ship features that make it a great solution for cluster operators too. A primary goal of Ship is to allow Cluster Operators to deliver 3rd party applications to their cluster the same way they manage their internal owned and written applications. Ship facilitates rollouts via existing automation systems with deep Kustomize integration, primitives like
ship watch and
ship update. Ship Cloud allows for a zero-ops solution to ensuring third party software is up to date
- Ship For Cluster Operators
- Ship Cloud/Ship Hosted
- Ship OSS
- Ship OSS – How it works
- Migrating Existing Deployments to Ship with “Unfork”
The generated reference documentation is a good resource for exploring all possible inputs for each Ship YAML section.