Welcome
Install and deploy DevOps Plan
Find information about installing and deploying DevOps Plan.
Getting started with DevOps Plan Helm Chart
This quick start guide shows you how to deploy DevOps Plan Helm Chart.
DevOps Plan Helm chart reference
Information about using the DevOps Plan Helm chart.
Parameters for Liveness and Readiness
This topic shows the liveness and readiness parameters for setting up the DevOps Plan helm chart.

Overview
Learn general information about the product.
Install and deploy DevOps Plan
Find information about installing and deploying DevOps Plan.
- Hardware, software, and database requirements
  Review the requirements information to identify operating system, file system, and compatibility requirements, prerequisite tasks, and other information that is required to install or upgrade DevOps Plan.
- Vendor database configuration
  DevOps Plan requires a PostGreSQL database to create TeamSpace and Applications.
- Getting started with DevOps Plan Helm Chart
  This quick start guide shows you how to deploy DevOps Plan Helm Chart.
  - Creating the DevOps Plan REST API SSL Certificate
    DevOps Plan uses SSL to secure access to its user interface and REST APIs. A self signed certificate is provided out of the box, but some proxies and gateways will accept self-signed certificates.
  - Installing SSL certificates
    You can install SSL certificates to ensure secure and reliable communication with the DevOps Plan application.
  - Enabling Swagger UI
    By default, the Swagger user interface (UI) is disabled. However, you can enable it two ways: by using the helm install command or by modifying the custom values YAML file.
  - Installing DevOps Plan with external databases and optional email server settings
    DevOps Plan requires a PostgreSQL database to create TeamSpace and Applications. The PostgreSQL database may be running in your cluster or on hardware that resides outside of your cluster. The values used to connect to the database are required when installing DevOps Plan. The DevOps Plan helm chart provides the PostgreSQL database by default settings. You can disable it and use your own PostgreSQL database.
  - Enabling the DevOps Plan Keycloak Single Sign On feature
    By default, the DevOps Plan Helm Chart comes configured with the Keycloak single sign on feature enabled. You can disable the Keycloak that is installed with the helm chart and use an external Keycloak instance that is installed outside of the helm chart.
  - Installing DevOps Plan with Emissary-ingress Load Balancer
    You can install DevOps Plan with Emissary-ingress load balancer when you plan to scale up hcl-devopsplan pods by running multiple instances. The Emissary-ingress load balancer distributes network traffic to all hcl-devopsplan pods. Once you have multiple instances of hcl-devopsplan running, you can perform rolling updates without downtime.
  - Installing DevOps Plan with DevOps Control
    DevOps Control provides Git hosting, code review, and team collaboration. It is similar to GitHub, Bitbucket, and GitLab. DevOps Control is based on the open-source Gitea project.
  - Backing up and restoring Kubernetes Cluster and PVC using Velero and MinIO
    You can configure and use Velero and MinIO to backup and restore your Kubernetes Clusters, including Persistent Volume Claims (PVCs). Velero manages backups while MinIO provides S3-compatible storage.
  - DevOps Plan Helm chart reference
    Information about using the DevOps Plan Helm chart.
    - DevOps Plan analytics feature and dashboards for business analytics helm chart reference
      Business analytics and dashboard support is offered as part of a technical preview. Support will be provided on a best effort basis.
    - DevOps Plan for Single Sign On support with Keycloak
      Single Sign-On support is offered by using Keycloak.
    - Parameters for PostgreSQL, TeamSpace, and Applications
      This topic shows the settings of the PostgreSQL database and the settings for TeamSpace and Application creation.
    - Parameters for Liveness and Readiness
      This topic shows the liveness and readiness parameters for setting up the DevOps Plan helm chart.
    - Values for mounting the DevOps Plan Windows package into the REST API Server
      Use the following values to enable to disable the DevOps Plan Windows package into the REST API server.
  - DevOps Plan persistent volumes
    Learn the default value settings for persistent volumes in DevOps Plan.
  - Updating OpenSearch and OpenSearch Dashboards password
    You can update the OpenSearch Dashboard password.
  - Performing helm upgrades to DevOps Plan
    You can upgrade DevOps Plan to the newest release using the helm upgrade command.
  - Performing helm roll backs to DevOps Plan
    You can roll back DevOps Plan to the previous release using the helm rollback command.
  - Troubleshooting
    Information about troubleshooting errors when deploying DevOps Plan.
Developing
Learn how to develop schemas by using the DevOps Plan Designer.
Integrating
You can integrate DevOps Plan with other software by adding packages to existing schema.
Extending product function
Learn how to extend the product.
Reference
Review reference information for the product.

Parameters for Liveness and Readiness

This topic shows the liveness and readiness parameters for setting up the DevOps Plan helm chart.

The below table shows lievness and readiness parameters for the devopsplan pod.

Table 1. devopsplan pod liveness and readiness parameters
Parameter	Description	Default value
probes.liveness.ccm.enabled	Enables liveness probe.	true
probes.liveness.ccm.initialDelaySeconds	Delay in seconds for initial liveness probe.	90
probes.liveness.ccm.periodSeconds	Duration in seconds between liveness probes.	10
probes.liveness.ccm.timeoutSeconds	Liveness probe timeout.	3
probes.liveness.ccm.successThreshold	Liveness probe success threshold.	1
probes.liveness.ccm.failureThreshold	Liveness probe failure threshold.	5
probes.readiness.ccm.enabled	Enables readiness probe.	true
probes.readiness.ccm.initialDelaySeconds	Delay in seconds for initial readiness probe.	90
probes.readiness.ccm.periodSeconds	Duration in seconds between readiness probes.	60
probes.readiness.ccm.timeoutSeconds	Readiness probe timeout.	3
probes.readiness.ccm.successThreshold	Readiness probe success threshold.	1
probes.readiness.ccm.failureThreshold	Readiness probe failure threshold.	3

Table 2. devopsplan-analytics pod liveness and readiness parameters
Parameter	Description	Default value
probes.liveness.analytics.enabled	Enables liveness probe.	true
probes.liveness.analytics.initialDelaySeconds	Delay in seconds for initial liveness probe.	90
probes.liveness.analytics.periodSeconds	Duration in seconds between liveness probes.	10
probes.liveness.analytics.timeoutSeconds	Liveness probe timeout.	3
probes.liveness.analytics.successThreshold	Liveness probe success threshold.	1
probes.liveness.analytics.failureThreshold	Liveness probe failure threshold.	5
probes.readiness.analytics.enabled	Enables readiness probe.	true
probes.readiness.analytics.initialDelaySeconds	Delay in seconds for initial readiness probe.	90
probes.readiness.analytics.periodSeconds	Duration in seconds between readiness probes.	60
probes.readiness.analytics.timeoutSeconds	Readiness probe timeout.	3
probes.readiness.analytics.successThreshold	Readiness probe success threshold.	1
probes.readiness.analytics.failureThreshold	Readiness probe failure threshold.	3

Table 3. devopsplan-postgresql pod liveness and readiness parameters
Parameter	Description	Default value
probes.liveness.postgresql.enabled	Enables liveness probe.	true
probes.liveness.postgresql.initialDelaySeconds	Delay in seconds for initial liveness probe.	90
probes.liveness.postgresql.periodSeconds	Duration in seconds between liveness probes.	10
probes.liveness.postgresql.timeoutSeconds	Liveness probe timeout.	3
probes.liveness.postgresql.successThreshold	Liveness probe success threshold.	1
probes.liveness.postgresql.failureThreshold	Liveness probe failure threshold.	5
probes.readinesspostgresql.enabled	Enables readiness probe.	true
probes.readiness.postgresql.initialDelaySeconds	Delay in seconds for initial readiness probe.	90
probes.readiness.postgresql.periodSeconds	Duration in seconds between readiness probes.	60
probes.readiness.postgresql.timeoutSeconds	Readiness probe timeout.	3
probes.readiness.postgresql.successThreshold	Readiness probe success threshold.	1
probes.readiness.postgresql.failureThreshold	Readiness probe failure threshold.	3