Starting and Stopping ESS Services
Stopping a component
To stop a component, such as Synapse
, it is necessary to stop the operator:
Once the operator is stopped, you can delete the Synapse resource to remove all Synapse workloads:
To get a list of resources that you can remove, you can look at the following command:
kubectl get elementdeployment/first-element-deployment -n element-onprem --template='{{range $key, $value := .status.dependentCRs}}{{$key}}{{"\n"}}{{end}}'
Example:
kubectl get elementdeployment/first-element-deployment -n element-onprem --template='{{range $key, $value := .status.dependentCRs}}{{$key}}{{"\n"}}{{end}}'
ElementWeb/first-element-deployment
Hookshot/first-element-deployment
Integrator/first-element-deployment
MatrixAuthenticationService/first-element-deployment
Synapse/first-element-deployment
SynapseAdminUI/first-element-deployment
SynapseUser/first-element-deployment-adminuser-donotdelete
SynapseUser/first-element-deployment-telemetry-donotdelete
WellKnownDelegation/first-element-deployment
Starting a component
To stop a component, such as Synapse
, it is necessary to start the operator:
Because the Synapse
resource will automatically have been recreated by the updater
, the operator on startup will automatically detect it and recreate all synapse workloads.