Single Instance Deployment
Version: 17.07
Supported Since: 17.01
A single instance deployment is one where the workers are deployed into a single K8s minion node.
| The demo IPS installer only supports single-instance deployments by design, as it is a single K8s node (acting as a master as well as a minion). |
While a single instance deployment has no special significance from the IPS point of view (i.e. the deployment composition, monitoring, statistics, troubleshooting etc are identical to a multi-node deployment), it has the disadvantage of lack of physical high availability (since, even if you require multiple worker instances, they would all be running in the same physical (or virtual) machine, and any system, resource or network disruption of the host would lead to complete malfunction or unavailability of all your deployed services).
Since IPS management components already require a K8s minion as their runtime host, the fact that you have a running IPS set-up usually indicates that your existing resources are good enough for a single instance deployment. You can also enforce workers to be deployed on a single instance by forcing them into a zone or node group containing only a single node.
In order to create a single node deployment,
-
Ensure one of the following:
-
You are on a single-instance IPS deployment.
-
You have defined a node group having only a single node.
-
You have defined your PDC zone to include a single node.
-
-
Create a cluster (including only the single-node group in case you had to define one in the previous step).
-
If you have not done so already, upload one or more projects to be deployed in the cluster.
-
Select the projects for deployment into the new cluster.
-
Create and submit a deployment with any required port mappings and configuration artifacts.
-
Once the deployment is successful, you will have an active single-instance deployment of the selected project(s).
In this topic
In this topic