SELF-HOSTED KUBERNETES OPERATIONS
Bring cluster operations and GitOps delivery together. Investigate workloads, review changes and give your team a shared console—hosted on infrastructure you control.
01 / PLATFORM CAPABILITIES
From routine resource checks to deployment investigations, Orkiva keeps the next action close to the information you need.
01 / VISIBILITY
Navigate clusters and namespaces, search resources, and inspect the objects behind your applications. Move from an overview into the resource that needs attention.
02 / INVESTIGATION
Inspect deployments, pods and related resources. Read events and container logs, review YAML, and open terminal tools when your permissions allow it.
03 / APPLICATIONS
Browse configured chart repositories and inspect Helm releases. Manage application changes with visibility into release configuration and history.
04 / DELIVERY
Connect sources and targets, inspect rendered plans, and follow policy checks and approval gates. Keep the source revision and deployment result in context.
05 / ACCESS
Manage users and roles, configure authentication, and define access to Kubernetes operations. Review permissions as responsibilities change.
06 / CONTEXT
Explore services, configuration, storage and custom resources alongside workloads. Inspect resource details and relationships without losing the cluster context.
02 / EVERYDAY OPERATIONS
A failing application rarely tells its whole story in one place. Move through the resources, status and logs that help explain what happened.
03 / GITOPS DELIVERY
Bring sources, deployment targets, policies and approvals into a visible delivery process. Inspect what is proposed before applying it.
Choose a stage to explore the workflow and its related product view.
01 / FETCH
A delivery run starts with its configured source and revision. Keep repository access and the selected source clear before you render a deployment.
02 / RENDER
Rendering prepares Kubernetes resources from the configured project. Review project settings before planning what will change in the target environment.
03 / PLAN
Read the resource-level plan before allowing the run to proceed. Investigate additions, updates, risk indicators and resources with no proposed change.
04 / POLICY
Configure delivery policies to define the checks a run must satisfy. Review policy results alongside the plan before protected changes proceed.
05 / APPROVAL
Approval gates pause protected changes for review. Authorized reviewers can inspect the run before making the approval decision.
06 / APPLY
After required checks and approvals, the apply stage performs the planned changes. Use the run view to follow stage state and investigate failures.
07 / VERIFY
Verification follows apply. Review the run result and resource health, and investigate differences between declared and live configuration.
04 / YOUR INSTALLATION
Orkiva is software your team installs and operates. Choose your own servers or cloud infrastructure, define the network boundary, and connect your Kubernetes clusters.
Discuss an evaluation ↗Deploy in the environment you manage. Your team owns runtime configuration, storage and connectivity to your clusters.
Configure authentication, users and roles. Review permissions before connecting the console to production workloads.
Receive future versions under your agreed package. Validate changes in your environment before rolling them out.
05 / FROM PACKAGE TO DAILY OPERATIONS
Start with your environment and access requirements. Build an installation your team can maintain, with support scope agreed before purchase.
Confirm hosting, database and storage needs, network access, authentication, and which clusters the team will manage.
Install the supplied package. Set up persistence, TLS and credentials for your chosen deployment environment.
Add cluster connections, configure roles, and test common operations with the intended user permissions.
Plan backups and upgrades, monitor the installation, and use documentation and agreed support when needed.
Deployment overview. Connectivity and access depend on your configuration.
06 / OPERATE WITH A PLAN
A self-hosted product needs an operating routine. Set expectations for ownership, recovery and support from the start.
Keep operational access intentional as people and responsibilities change.
Protect the installation’s persistent data and configuration using the documented process.
Treat upgrades as a planned change to your operating environment.
Give your team a practical reference for daily work and escalation.
07 / BUILT FOR THE PEOPLE RUNNING IT
Bring the relevant information to the people investigating workloads, reviewing deployments and maintaining the installation.
Inspect workloads and manage application releases, with logs and resource details close at hand.
Provide a shared Kubernetes console with configured access and a visible GitOps delivery process.
Maintain the installation, cluster connections, authentication and operational configuration.
PLAN YOUR NEXT STEP
Understand the buying process, prepare your environment and confirm the version you will run.
Agree the software package, delivery format, update terms and support scope.
Read the buying guide ↗Review compute, persistence, connectivity and version compatibility before installation.
Prepare your environment ↗Read verified version highlights and discuss the right upgrade path for your installation.
View version history ↗ILLUSTRATIVE USE CASES
These are example scenarios, not customer testimonials or measured results.
EXAMPLE / PLATFORM TEAM
A team starts with the cluster overview, opens a deployment and checks pod logs and events to understand unexpected behavior.
EXAMPLE / DELIVERY TEAM
A reviewer inspects a proposed GitOps change and its policy results before deciding whether to approve the run.
EXAMPLE / ADMINISTRATOR
An administrator configures users and roles so team members work with the access appropriate to their responsibilities.
KNOW YOUR DATA FLOW
Review data storage, credential protection, optional external connections and the responsibilities of running your own installation.
Explore security & data ownership ↗08 / BEFORE YOU START
Understand what you install, what your team manages, and how to get started.
Orkiva is customer-hosted software. You install and operate it on infrastructure you control. Your hosting provider and cluster locations are your choices.
Orkiva connects to Kubernetes clusters and gives your team a web console for operating them. Your servers, Kubernetes platform and underlying networking remain part of your own infrastructure.
Software delivery, access to future versions and support are defined in your purchase agreement. Contact sales@orkiva.tech to discuss your environment and the scope you need.
Plan persistence, TLS, authentication, cluster credentials, permissions, backups and upgrades. Follow the deployment documentation and validate the setup in your own environment.
Yes. They show an Orkiva demonstration installation. Resource names, counts and run states are demonstration data, not customer results.
The documentation covers installation, Kubernetes resource operations, GitOps Delivery, administration and developer workflows. Contact support@orkiva.tech for help within your agreed support scope.
YOUR NEXT OPERATING SPACE
Tell us about your clusters, your team and how you want to deploy Orkiva.
orkiva