orkivaKUBERNETES CONSOLE Discuss an evaluation ↗

FROM FIRST QUESTION TO YOUR FIRST CLUSTER

Evaluate and install Orkiva.

Choose the software package and support scope around your environment. Your team hosts the installation and controls access to it.

01 / EVALUATE

Start with your workflow.

Tell us which clusters you manage, how your team investigates workloads and how you deliver changes. Ask sales about evaluation options and agree what you need to validate.

  • Cluster visibility and day-to-day troubleshooting
  • GitOps review and approval workflows
  • Authentication and team access

02 / AGREE THE PACKAGE

Know what you are buying.

Confirm the software version, delivery format, pricing, usage terms and support scope before purchase.

  • Installation responsibilities and assistance
  • Future-version access and update terms
  • Support coverage and response commitments

03 / INSTALL & VALIDATE

Run it in your environment.

Install the agreed package, configure persistence and HTTPS, and connect a test cluster. Validate the workflows and permissions your team intends to use before expanding access.

04 / MAINTAIN

Keep ownership after launch.

Your team operates its infrastructure. Plan backups, review new-version requirements and test upgrades before rollout. Contact product support under your agreed package when you need help.

INSTALLATION CHECKLIST

Prepare your environment.

Requirements depend on the package and deployment profile. Confirm the exact version and sizing with us before purchase.

Compute & persistence

The current Helm configuration requests 100m CPU and 256 MiB memory for the main console, with limits of 1 CPU and 1 GiB. These are configuration defaults, not a measured minimum or capacity guarantee. Database, delivery workers and other enabled services need separate resources.

Keep database and delivery artifact storage persistent. Size storage around retention, backups and the workload you plan to run.

Network & access

Provide browser access to Orkiva over HTTPS and the cluster connectivity required by your chosen connection method. Configure credentials and permissions for the Kubernetes operations your team needs.

GitOps sources, chart repositories, registries and optional integrations require access to their configured endpoints.

Deployment profile

For a standard installation, confirm database and storage settings before deployment. The high-availability profile adds PostgreSQL, multiple console instances and separate delivery services with shared artifact storage.

Review the complete profile with the supplied package; this checklist is not an installation command set.

Version compatibility

Share your Kubernetes version, host architecture, database and ingress setup during evaluation. Ask us to confirm the combination for the package you will receive.

We do not publish a guaranteed Kubernetes version range here without completed qualification for that release.