- Deploy and Configure Ops Manager Resources >
- Deploy an Ops Manager Resource
Deploy an Ops Manager Resource¶
On this page
You can deploy Ops Manager as a resource in a Kubernetes container using the Kubernetes Operator.
Considerations¶
The following considerations apply:
Encrypting Connections¶
When you configure your Ops Manager deployment, you must choose whether to run connections over HTTPS or HTTP.
The following HTTPS procedure:
- Establishes TLS-encrypted connections to/from the Ops Manager application.
- Establishes TLS-encrypted connections between the application database’s replica set members.
- Requires valid certificates for TLS encryption.
The following HTTP procedure:
- Doesn’t encrypt connections to or from the Ops Manager application.
- Doesn’t encrypt connections between the application database’s replica set members.
- Has fewer setup requirements.
When running over HTTPS, Ops Manager runs on port 8443
by
default.
Select the appropriate tab based on whether you want to encrypt your Ops Manager and application database connections with TLS.
Deploying on the Central Cluster in a Multi-Kubernetes-Cluster Deployment¶
To deploy an Ops Manager instance in the central cluster and connect to it, use the following procedures:
- Review the Ops Manager resource architecture
- Review the Ops Manager resource considerations and prerequisites
- Deploy an Ops Manager instance on the central cluster with TLS encryption
These procedures are the same as the procedures for single clusters deployed with the Kubernetes Operator with the following exceptions:
Set the context and the namespace.
If you are deploying an Ops Manager resource in a multi-Kubernetes-cluster deployment:
- Set the
context
to the name of the central cluster, such as:kubectl config set context "$MDB_CENTRAL_CLUSTER_FULL_NAME"
. - Set the
--namespace
to the same scope that you used for your multi-Kubernetes-cluster deployment, such as:kubectl config --namespace "mongodb"
.
- Set the
Configure external connectivity for Ops Manager.
To connect member clusters to the Ops Manager resource’s deployment in the central cluster in a multi-Kubernetes-cluster deployment, use one of the following methods:
Set the
spec.externalConnectivity
totrue
and specify the Ops Manager port in it. Use the ops-manager-external.yaml example script, modify it to your needs, and apply the configuration. For example, run:Add the central cluster and all member clusters to the same service mesh. The service mesh establishes communication from the the central and all member clusters to the Ops Manager instance. To learn more, see the Multi-Kubernetes-Cluster Quick Start procedures and see the step that references the
istio-injection=enabled
label for Istio. Also, see Automatic sidecar injection in the Istio documentation.
Deploy Ops Manager and the Application Database on the central cluster.
You can choose to deploy Ops Manager and the Application Database only on the central cluster, using the same procedure as for single Kubernetes clusters. To learn more, see Deploy an Ops Manager instance on the central cluster with TLS encryption.
Deploy Ops Manager on the central cluster and the Application Database on selected member clusters.
You can choose to deploy Ops Manager on the central cluster and the Application Database on a subset of selected member clusters, to increase the Application Database’s resilience and availability in Ops Manager. Configure the following settings in the Ops Manager CRD:
- Use
topology
to specify theMultiCluster
value. - Specify the
clusterSpecList
and include in it theclusterName
of each selected Kubernetes member cluster on which you want to deploy the Application Database, and the number ofmembers
(MongoDB nodes) in each Kubernetes member cluster.
Note
If you deploy the Application Database on selected member clusters in your multi-Kubernetes-cluster deployment, you must include the central cluster and member clusters in the same service mesh configuration. This enables bi-directional communication from Ops Manager to the Application Database.
To learn more, see Deploy Ops Manager, review the multi-Kubernetes-cluster deployment example and specify
MultiCluster
fortopology
.- Use
Prerequisites¶
- TLS-Encrypted Connections (HTTPS)
- Non-Encrypted Connections (HTTP)
Complete the Prerequisites.
Read the Considerations.
Create one TLS certificate for the Application Database’s replica set.
This TLS certificate requires the following attributes:
DNS Names Ensure that you add SANs or Subject Names for each Pod that hosts a member of the Application Database replica set. The SAN for each pod must use the following format:
Key Usages Ensure that the TLS certificates include the following key-usages (5280):
- “server auth”
- “client auth”
Important
The Kubernetes Operator uses kubernetes.io/tls secrets to store TLS certificates and private keys for Ops Manager and MongoDB resources. Starting in Kubernetes Operator version 1.17.0, the Kubernetes Operator doesn’t support concatenated PEM files stored as Opaque secrets.
Before you deploy an Ops Manager resource, make sure you plan for your Ops Manager resource:
- Complete the Prerequisites
- Read the Considerations.
Procedure¶
- TLS-Encrypted Connection (HTTPS)
- Non-Encrypted Connection (HTTP)
Follow these steps to deploy the Ops Manager resource to run over HTTPS and secure the application database using TLS.
Configure kubectl
to default to your namespace.¶
If you have not already, run the following command to execute all
kubectl
commands in the namespace you created.
Note
If you are deploying an Ops Manager resource in a multi-Kubernetes-cluster deployment:
- Set the
context
to the name of the central cluster, such as:kubectl config set context "$MDB_CENTRAL_CLUSTER_FULL_NAME"
. - Set the
--namespace
to the same scope that you used for your multi-Kubernetes-cluster deployment, such as:kubectl config --namespace "mongodb"
.
Create secrets for your certificates.¶
If you’re using HashiCorp Vault as your secret storage tool, you can Create a Vault Secret instead.
To learn about your options for secret storage, see Configure Secret Storage.
If necessary, validate your TLS certificates.¶
If your Ops Manager TLS certificate or your application database TLS certificate is signed by a custom CA, you must provide a CA certificate to validate the TLS certificate(s). To validate the TLS certificate(s), create a ConfigMap to hold the CA certificate:
Warning
You must concatenate your custom CA file and the entire
TLS certificate chain from downloads.mongodb.com
to prevent
Ops Manager from becoming inoperable if the application database
restarts.
Important
The Kubernetes Operator requires that:
- Your Ops Manager certificate is named
mms-ca.crt
in the ConfigMap. - Your application database certficate is named
ca-pem
in the ConfigMap.
Obtain the entire TLS certificate chain for both Ops Manager and the application database from
downloads.mongodb.com
. The followingopenssl
command outputs each certificate in the chain to your current working directory, in.crt
format:Concatenate your CA’s certificate file for Ops Manager with the entire TLS certificate chain from
downloads.mongodb.com
that you obtained in the previous step:Concatenate your CA’s certificate file for the application database with the entire TLS certificate chain from
downloads.mongodb.com
that you obtained in the previous step:Create the ConfigMap for Ops Manager:
Create the ConfigMap for the application database:
Configure the settings specific to your deployment.¶
Key | Type | Description | Example |
---|---|---|---|
metadata.name |
string | Name for this Kubernetes Ops Manager object. Resource names must be 44 characters or less. See also
|
om |
spec.replicas |
number | Number of Ops Manager instances to run in parallel. The minimum valid value is Highly Available Ops Manager Resources For high availability, set this value to more than |
1 |
spec.version |
string | Version of Ops Manager to be installed. The format should be X.Y.Z. To view available Ops Manager versions, view the container registry. |
6.0.0 |
spec.adminCredentials |
string | Name of the secret you created for the Ops Manager admin user. Note Configure the secret to use the same namespace as the Ops Manager resource. |
om-admin-secret |
string | Required. Text to prefix to the name of the secret that contains Ops Managers TLS certificates. |
om-prod |
|
string | Name of the ConfigMap you created to verify your Ops Manager TLS certificates signed using a custom CA. Important This field is required if you signed your Ops Manager TLS certificates using a custom CA. |
om-http-cert-ca |
|
string | The Kubernetes service ServiceType that exposes Ops Manager outside of Kubernetes. Note Exclude the
|
LoadBalancer |
|
integer | Number of members of the Ops Manager Application Database replica set. | 3 |
|
string | Required. Version of MongoDB that the Ops Manager Application Database should run. The format should be
Important Ensure that you choose a compatible MongoDB Server version. Compatible versions differ depending on the base image that the MongoDB database resource uses. To learn more about MongoDB versioning, see MongoDB Versioning in the MongoDB Manual. |
For best results, use the latest available enterprise MongoDB version that is compatible with your Ops Manager version. | |
string | Optional. The type of the Kubernetes deployment for the Application Database.
If omitted, the default is If you specify Note You can’t convert a single cluster Ops Manager instance to a
multi-Kubernetes-cluster deployment instance by modifying the
See also the example of the resource specification. |
MultiCluster |
|
string | Required. Text to prefix to the name of the secret that contains the application database’s TLS certificates. |
appdb-prod |
|
string | Name of the ConfigMap you created to verify your application database TLS certificates signed using a custom CA. Important This field is required if you signed your application database TLS certificates using a custom CA. |
ca |
Note
The Kubernetes Operator mounts the CA you add using the
spec.applicationDatabase.security.tls.ca
setting to
both the Ops Manager and the Application Database Pods.
Optional: Configure Backup settings.¶
To configure backup, you must enable it, and then:
- Choose to configure an S3 snapshot store or a blockstore. If you deploy both an S3 snapshot store and a blockstore, Ops Manager randomly choses one to use for backup.
- Choose to configure an oplog store or an S3 oplog store. If you deploy both an oplog store and an S3 oplog store, Ops Manager randomly choses one of them to use for the oplog backup.
Key | Type | Description | Example |
---|---|---|---|
boolean | Flag that indicates that Backup is enabled. You must
specify spec.backup.enabled: true to configure settings
for the head database, oplog store, and snapshot store. |
true |
|
spec .backup .headDB |
collection | A collection of configuration settings for the
head database. For descriptions of the individual
settings in the collection, see
spec.backup.headDB . |
|
string | Name of the oplog store. | oplog1 |
|
spec .backup .s3opLogStores . name |
string | Name of the S3 oplog store. | my-s3-oplog-store |
string | Name of the MongoDB resource or MongoDBMultiCluster resource for the oplog store.
The resource’s metadata.name must match this name. |
my-oplog-db |
|
spec .backup .s3opLogStores .mongodbResourceRef . name |
string | Name of the MongoDB resource or MongoDBMultiCluster resource for the S3 oplog store.
The resource’s metadata.name must match this name. |
my-s3-oplog-db |
You must also configure an S3 snapshot store or a blockstore.
Note
If you deploy both an S3 snapshot store and a blockstore, Ops Manager randomly choses one to use for Backup.
To configure a snapshot store, configure the following settings:
Key | Type | Description | Example |
---|---|---|---|
string | Name of the S3 snapshot store. | s3store1 |
|
string | Name of the secret that contains the accessKey and
secretKey fields. The Backup Daemon Service uses the
values of these fields as credentials to access the S3 or
S3-compatible bucket. |
my-s3-credentials |
|
string | URL of the S3 or S3-compatible bucket that stores the database Backup snapshots. | s3.us-east-1.amazonaws.com |
|
string | Name of the S3 or S3-compatible bucket that stores the database Backup snapshots. | my-bucket |
To configure a blockstore, configure the following settings:
Key | Type | Description | Example |
---|---|---|---|
string | Name of the blockstore. | blockStore1 |
|
string | Name of the MongoDB resource that you create for the blockstore. You must
deploy this database resource in the same namespace as the Ops Manager resource. |
my-mongodb-blockstore |
Optional: Configure any additional settings for an Ops Manager backup.¶
Add any optional settings for backups
that you want to apply to your deployment to the object specification
file. For example, for each type of backup store, and for Ops Manager backup
daemon processes, you can assign labels to associate particular backup
stores or backup daemon processes with specific projects.
Use spec.backup.[*].assignmentLabels
elements of the OpsManager
resources.
Optional: Configure any additional settings for an Ops Manager deployment.¶
Add any optional settings that you want to apply to your deployment to the object specification file.
Save this file with a .yaml
file extension.¶
Create your Ops Manager instance.¶
Run the following kubectl
command on the filename of the
Ops Manager resource definition:
Note
If you are deploying an Ops Manager resource on a multi-Kubernetes-cluster deployment, run:
Track the status of your Ops Manager instance.¶
To check the status of your Ops Manager resource, invoke the following command:
The command returns the output similar to the following under the status
field while the resource deploys:
The Kubernetes Operator reconciles the resources in the following order:
- Application Database.
- Ops Manager.
- Backup.
The Kubernetes Operator doesn’t reconcile a resource until the preceding
one enters the Running
phase.
After the Ops Manager resource completes the Pending
phase, the
command returns output similar to the following under the status
field if you enabled Backup:
Backup remains in a Pending
state until you configure the Backup
databases.
Tip
The status.opsManager.url
field states the resource’s
connection URL. Using this URL, you can reach Ops Manager from
inside the Kubernetes cluster or create a project using a
ConfigMap.
After the resource completes the Pending
phase, the command
returns output similar to the following under the status
field:
Backup remains in a Pending
state until you configure the Backup
databases.
Tip
The status.opsManager.url
field states the resource’s
connection URL. Using this URL, you can reach Ops Manager from
inside the Kubernetes cluster or create a project using a
ConfigMap.
Access the Ops Manager application.¶
The steps you take differ based on how you are routing traffic to the Ops Manager application in Kubernetes. If you configured the Kubernetes Operator to create a Kubernetes service for you, or you created a Kubernetes service manually, use one of the following methods to access the Ops Manager application:
- External Traffic Routes Using LoadBalancer Service
- External Traffic Routed Using NodePort Service
Query your cloud provider to get the FQDN of the load balancer service. See your cloud provider’s documentation for details.
Open a browser window and navigate to the Ops Manager application using the FQDN and port number of your load balancer service.
Log in to Ops Manager using the admin user credentials.
Set your firewall rules to allow access from the Internet to the
spec.externalConnectivity.
port
on the host on which your Kubernetes cluster is running.Open a browser window and navigate to the Ops Manager application using the FQDN and the
spec.externalConnectivity.
port
.Log in to Ops Manager using the admin user credentials.
To learn how to access the Ops Manager application using a third-party service, refer to the documentation for your solution.
Create credentials for the Kubernetes Operator.¶
To configure credentials, you must create an Ops Manager organization, generate programmatic API keys, and create a secret. These activities follow the prerequisites and procedure on the Create Credentials for the Kubernetes Operator page.
Create a project using a ConfigMap.¶
To create a project, follow the prerequisites and procedure on the Create One Project using a ConfigMap page.
Set the following fields in your project ConfigMap:
Set
data.baseUrl
in the ConfigMap to the Ops Manager Application’s URL. To find this URL, invoke the following command:The command returns the URL of the Ops Manager Application in the
status.opsManager.url
field, similar to the following example:Important
If you deploy Ops Manager with the Kubernetes Operator and Ops Manager will manage MongoDB database resources deployed outside of the Kubernetes cluster it’s deployed to, you must set
data.baseUrl
to the same value of thespec.configuration.mms.centralUrl
setting in the Ops Manager resource specification.Set
data.sslMMSCAConfigMap
to the name of your ConfigMap containing the root CA certificate used to sign the Ops Manager host’s certificate. The Kubernetes Operator requires that you name this Ops Manager resource’s certificatemms-ca.crt
in the ConfigMap.
Deploy MongoDB database resources to complete the backup configuration.¶
By default, Ops Manager enables Backup. Create a MongoDB database resource for the oplog and snapshot stores to complete the configuration.
Deploy a MongoDB database resource for the oplog store in the same namespace as the Ops Manager resource.
Note
Create this database as a three-member replica set.
Match the
metadata.name
of the resource with thespec.backup.opLogStores.mongodbResourceRef.name
that you specified in your Ops Manager resource definition.Deploy a MongoDB database resource for the S3 snapshot store in the same namespace as the Ops Manager resource.
Note
Create the S3 snapshot store as a replica set.
Match the
metadata.name
of the resource to thespec.backup.s3Stores.mongodbResourceRef.name
that you specified in your Ops Manager resource definition.
Confirm that the Ops Manager resource is running.¶
To check the status of your Ops Manager resource, invoke the following command:
When Ops Manager is running, the command returns the output similar to the
following, under the status
field:
See Troubleshoot the Kubernetes Operator for information about the resource deployment statuses.
Follow these steps to deploy the Ops Manager resource to run over HTTP:
Configure kubectl
to default to your namespace.¶
If you have not already, run the following command to execute all
kubectl
commands in the namespace you created.
Note
If you are deploying an Ops Manager resource in a multi-Kubernetes-cluster deployment:
- Set the
context
to the name of the central cluster, such as:kubectl config set context "$MDB_CENTRAL_CLUSTER_FULL_NAME"
. - Set the
--namespace
to the same scope that you used for your multi-Kubernetes-cluster deployment, such as:kubectl config --namespace "mongodb"
.
Configure the settings included in the previous example.¶
Key | Type | Description | Example |
---|---|---|---|
metadata.name |
string | Name for this Kubernetes Ops Manager object. Resource names must be 44 characters or less. See also
|
om |
spec.replicas |
number | Number of Ops Manager instances to run in parallel. The minimum valid value is Highly Available Ops Manager Resources For high availability, set this value to more than |
1 |
spec.version |
string | Version of Ops Manager to be installed. The format should be X.Y.Z. For the list of available Ops Manager versions, view the container registry. |
6.0.0 |
spec.adminCredentials |
string | Name of the secret you created for the Ops Manager admin user. Note Configure the secret to use the same namespace as the Ops Manager resource. |
om-admin-secret |
string | Optional. The Kubernetes service ServiceType that exposes Ops Manager outside of Kubernetes. Note Exclude the
|
LoadBalancer |
|
integer | Number of members of the Ops Manager Application Database replica set. | 3 |
|
string | Required. Version of MongoDB that the Ops Manager Application Database should run. The format should be Important Ensure that you choose a compatible MongoDB Server version. Compatible versions differ depending on the base image that the MongoDB database resource uses. To learn more about MongoDB versioning, see MongoDB Versioning in the MongoDB Manual. |
For best results, use the latest available enterprise MongoDB version that is compatible with your Ops Manager version. | |
string | Optional. The type of the Kubernetes deployment for the Application Database.
If omitted, the default is If you specify Instead, you must specify the Note You can’t convert a single cluster Ops Manager instance to a
multi-Kubernetes-cluster deployment instance by modifying the
See also the example of the resource specification. |
MultiCluster |
Optional: Configure backup settings.¶
To configure backup, you must enable it, and then:
- Choose to configure an S3 snapshot store or a blockstore. If you deploy both an S3 snapshot store and a blockstore, Ops Manager randomly choses one to use for backup.
- Choose to configure an oplog store or an S3 oplog store. If you deploy both an oplog store and an S3 oplog store, Ops Manager randomly choses one of them to use for the oplog backup.
Key | Type | Description | Example |
---|---|---|---|
boolean | Flag that indicates that backup is enabled. You must specify
spec.backup.enabled: true to configure settings
for the head database, oplog store, S3 oplog store, and snapshot store. |
true |
|
spec .backup .headDB |
collection | A collection of configuration settings for the
head database. For descriptions of the individual
settings in the collection, see
spec.backup.headDB . |
|
string | Name of the oplog store. | oplog1 |
|
spec .backup .s3opLogStores . name |
string | Name of the S3 oplog store. | my-s3-oplog-store |
string | Name of the MongoDB resource or MongoDBMultiCluster resource for the oplog store.
The resource’s metadata.name must match this name. |
my-oplog-db |
|
spec .backup .s3opLogStores .mongodbResourceRef . name |
string | Name of the MongoDB database resource for the S3 oplog store. | my-s3-oplog-db |
You must also configure an S3 snapshot store or a blockstore.
Note
If you deploy both an S3 snapshot store and a blockstore, Ops Manager randomly choses one to use for backup.
To configure an S3 snapshot store, configure the following settings:
Key | Type | Description | Example |
---|---|---|---|
string | Name of the S3 snapshot store. | s3store1 |
|
string | Name of the secret that contains the accessKey and
secretKey fields. The Backup Daemon Service uses the
values of these fields as credentials to access the S3 or
S3-compatible bucket. |
my-s3-credentials |
|
string | URL of the S3 or S3-compatible bucket that stores the database backup snapshots. | s3.us-east-1.amazonaws.com |
|
string | Name of the S3 or S3-compatible bucket that stores the database backup snapshots. | my-bucket |
|
string | Region where your S3-compatible bucket resides. Use this
field only if your S3 store’s
s3BucketEndpoint
doesn’t include a region in its URL. Don’t use this field with AWS S3 buckets. |
us-east-1 |
To configure a blockstore, configure the following settings:
Key | Type | Description | Example |
---|---|---|---|
string | Name of the blockstore. | blockStore1 |
|
string | Name of the MongoDB resource that you create for the blockstore.
You must deploy this database resource in the same namespace as
the Ops Manager resource. The resource’s metadata.name must match this name. |
my-mongodb-blockstore |
Optional: Configure any additional settings for an Ops Manager backup.¶
Add any optional settings for backups
that you want to apply to your deployment to the object specification
file. For example, for each type of backup store, and for Ops Manager backup
daemon processes, you can assign labels to associate particular backup
backup stores or backup daemon processes with specific projects.
Use spec.backup.[*].assignmentLabels
elements of the OpsManager
resources.
Optional: Configure any additional settings for an Ops Manager deployment.¶
Add any optional settings that you want to apply to your deployment to the object specification file.
Save this file with a .yaml
file extension.¶
Create your Ops Manager instance.¶
Run the following kubectl
command on the filename of the Ops Manager resource definition:
Note
If you are deploying an Ops Manager resource on a multi-Kubernetes-cluster deployment, run:
Track the status of your Ops Manager instance.¶
To check the status of your Ops Manager resource, invoke the following command:
The command returns output similar to the following, under the status
field
while the resource deploys:
The Kubernetes Operator reconciles the resources in the following order:
- Application Database.
- Ops Manager.
- Backup.
The Kubernetes Operator doesn’t reconcile a resource until the preceding
one enters the Running
phase.
After the Ops Manager resource completes the Pending
phase, the
command returns the output similar to the following under the status
field if you enabled backup:
Backup remains in a Pending
state until you configure the backup
databases.
Tip
The status.opsManager.url
field states the resource’s
connection URL. Using this URL, you can reach Ops Manager from
inside the Kubernetes cluster or create a project using a
ConfigMap.
Access the Ops Manager application.¶
The steps you take differ based on how you are routing traffic to the Ops Manager application in Kubernetes. If you configured the Kubernetes Operator to create a Kubernetes service for you, or you created a Kubernetes service manually, use one of the following methods to access the Ops Manager application:
- External Traffic Routes Using LoadBalancer Service
- External Traffic Routed Using NodePort Service
Query your cloud provider to get the FQDN of the load balancer service. See your cloud provider’s documentation for details.
Open a browser window and navigate to the Ops Manager application using the FQDN and port number of your load balancer service.
Log in to Ops Manager using the admin user credentials.
Set your firewall rules to allow access from the Internet to the
spec.externalConnectivity.
port
on the host on which your Kubernetes cluster is running.Open a browser window and navigate to the Ops Manager application using the FQDN and the
spec.externalConnectivity.
port
.Log in to Ops Manager using the admin user credentials.
To learn how to access the Ops Manager application using a third-party service, refer to the documentation for your solution.
Optional: Create credentials for the Kubernetes Operator.¶
If you enabled backup, you must create an Ops Manager organization, generate programmatic API keys, and create a secret in your secret-storage-tool. These activities follow the prerequisites and procedure on the Create Credentials for the Kubernetes Operator page.
Optional: Create a project using a ConfigMap.¶
If you enabled backup, create a project by following the prerequisites and procedure on the Create One Project using a ConfigMap page.
You must set data.baseUrl
in the ConfigMap to the Ops Manager Application’s URL. To find this URL, invoke the following command:
The command returns the URL of the Ops Manager Application in the
status.opsManager.url
field, similar to the following example:
Important
If you deploy Ops Manager with the Kubernetes Operator and Ops Manager will
manage MongoDB database resources deployed outside of the Kubernetes
cluster it’s deployed to, you must set data.baseUrl
to the same
value of the
spec.configuration.mms.centralUrl
setting in the Ops Manager resource specification.
Optional: Deploy MongoDB database resources to complete the backup configuration.¶
If you enabled Backup, create a MongoDB database resource for the oplog and snapshot stores to complete the configuration.
Deploy a MongoDB database resource for the oplog store in the same namespace as the Ops Manager resource.
Note
Create this database as a replica set.
Match the
metadata.name
of the resource with thespec.backup.opLogStores.mongodbResourceRef.name
that you specified in your Ops Manager resource definition.Choose one of the following:
Deploy a MongoDB database resource for the blockstore in the same namespace as the Ops Manager resource.
Match the
metadata.name
of the resource to thespec.backup.blockStores.mongodbResourceRef.name
that you specified in your Ops Manager resource definition.Configure an S3 bucket to use as the S3 snapshot store.
Ensure that you can access the S3 bucket using the details that you specified in your Ops Manager resource definition.
Optional: Confirm that the Ops Manager resource is running.¶
If you enabled backup, check the status of your Ops Manager resource by invoking the following command:
When Ops Manager is running, the command returns the following
output under the status
field:
See Troubleshoot the Kubernetes Operator for information about the resource deployment statuses.