Docs / Helm, GitOps and ecosystem tools
Helm, GitOps and ecosystem tools
Helm releases, installs and upgrades; Argo CD, Flux and Argo Rollouts actions; Gateway API, Karpenter, Istio and Linkerd views.
Helm
Releases are read straight from Helm's storage in the cluster (Secrets or ConfigMaps). Listing, values (yours, or computed with the chart's defaults), manifests, notes and history need no helm binary, and work with Helm 3 and 4.
Upgrade and rollback run your own helm, found on your login shell's PATH, with the same kubeconfig files and context Klystiq uses. Upgrades show a server-side dry-run diff first.
Install chart…, on the Helm page, searches the charts in your repositories (you can add a repository or update the indexes there too), or takes an oci:// reference, a URL or a local path. Pick a version, release name, namespace (created if missing) and context, then edit the values, starting from the chart's defaults. Review the objects and manifest of a server-side dry run, then install.
Without helm, these actions explain what to install, and everything else keeps working.
GitOps
Argo CD Applications, Flux Kustomizations, HelmReleases and sources appear in a GitOps section when their CRDs are installed. Their actions are in the actions menu and on detail pages:
- Argo CD: sync (optionally pruning), refresh, hard refresh.
- Flux: reconcile (with its source, for Kustomizations and HelmReleases), suspend, resume.
- Argo Rollouts: promote, promote fully, abort, retry, restart, pause.
Each action makes the same patch the tool's own CLI makes, so you don't need an argocd, flux or plugin login, and each confirmation shows the equivalent command. Read-only contexts refuse them.
Ecosystem views
These appear when their CRDs are installed, each with the columns that matter and a detail page:
- Argo Rollouts, under Workloads: status, strategy, canary step and weight.
- Gateway API Gateways and routes, under Networking.
- Karpenter NodePools and NodeClaims, under Cluster.
- Istio: VirtualServices, DestinationRules, Gateways, ServiceEntries, Sidecars, PeerAuthentications, AuthorizationPolicies and RequestAuthentications, with health colors from Istio's own validation messages.
- Linkerd: ServiceProfiles, Servers, AuthorizationPolicies, routes, MeshTLS and network authentications.
Topology's Traffic chip draws Istio Gateways, VirtualServices and the Services they route to, with the subset on each route.