Skip to main content
Version: 2.15.X

Verifying Deployments

This section covers how to verify that you have successfully installed Cogynt into your Kubernetes cluster.

note

For the purposes of this guide, instructions are provided only for the Kubernetes Dashboard. However, other tools are available that serve similar purposes, such as Lens, or kubectl from the command line. You may use whatever tool is most suitable for your workflow. The strategies outlined in this guide apply regardless of the tool used.

Identifying Healthy Deployments​

Cogynt uses the Kubernetes Dashboard to track the status of deployment components. This section provides a brief overview of how to access the Kubernetes Dashboard, and how to use it to determine whether a deployment is healthy.

For more information about the Kubernetes Dashboard, refer to the official Kubernetes documentation.

Accessing the Kubernetes Dashboard​

In Cogynt, the Kubernetes Dashboard can be accessed from a web browser. The access URL follows the syntax https://kubedash-[environment].[domain_name].[domain_suffix], where:

  • [environment] is the cluster to access. Customers may have access to different clusters (such as development, staging, or production).
  • [domain name] is the customer's domain (for example, cogility).
  • [domain suffix] is the customer's domain suffix (for instance, com, io, org).
tip

Consider the following hypothetical scenario:

  • The production cluster is named prod.
  • The customer's domain is named example.
  • The customer's domain suffix is com.

Given this information, navigating to https://kubedash-prod.example.com accesses the Kubernetes Dashboard in the production environment.

Reading the Kubernetes Dashboard​

A healthy cluster typically means that Cogynt was successfully installed.

On the Kubernetes Dashboard, a healthy cluster tends to behave as follows:

  • All cluster components are running, with their status showing green.
  • No components are in the "Not Started" state.
  • No components are caught in crash loops.

If the cluster is not behaving this way, it may indicate a problem with the deployment. For strategies regarding how to resolve deployment problems, see Diagnosing Deployment Issues.

Diagnosing Deployment Issues​

Since technical problems can arise from any number of sources, there is no single method for diagnosing issues with a deployment. That said, Cogility recommends the following strategies for identifying root problems.

Inspecting Namespaces​

Cogynt organizes its components by namespace. Checking the individual namespaces can help determine where problems are occurring.

To look for problems by namespace using the Kubernetes Dashboard:

  1. Access the Kubernetes Dashboard. For more information, see Accessing the Kubernetes Dashboard.
  2. In the upper-left of the screen, select a namespace from the dropdown menu. (For example, cogynt.)
  3. Look for applications with persistent startup failures or crash loops.
  4. If an application has problems, it may indicate an issue with one of the connected databases. Refer to the appropriate user guide for more information about which databases connect to the application.

If you are unable to diagnose or solve issues, contact Cogility Support.

Identifying Persistent Startup Failures​

Nodes and applications regularly restart during standard Kubernetes cluster operations. However, an excessive number of restarts likely indicates a problem with the node or application.

If a node or application shows a restart count of approximately 50 or more, then there is an issue with the node/application or its connected databases.

Identifying Crash Loops​

If a node or application appears to start, stop, and restart repeatedly, then it is caught in a "crash loop."

A node or application in a crash loop likely indicates a problem with its connected databases.

Contacting Cogility Support​

If none of the preceding methods help diagnose the problem, or if your organization is unable to solve the issue, contact Cogility Support for assistance.