Outils
Lynx Patrii Cloud K8s Deploy
Deploy manifests and Helm charts to a Patrii Magnum cluster from Lynx
lynx_patrii_k8s_deploy
· v19.0.1.0.0
· Premium
What this solves
Lynx Patrii Cloud K8s Deploy
Deploy raw Kubernetes manifests and Helm charts into a Patrii Cloud Magnum cluster (and, in a coming release, into any bring-your-own kubeconfig) from inside Lynx, using the credentials already stored by the Patrii Cloud Connector.
A target points at one cluster — for v1, only Patrii Magnum clusters are supported, with the kubeconfig fetched on-save through the connector's authenticated API client. A deployment is one logical workload (a manifest or a Helm release) that the user can deploy, roll back, and refresh status on. Long-running operations are tracked by a cron poller, never by blocking the request — so a slow apply never freezes the UI.
Key Features
Patrii Magnum target — fetches kubeconfig via connection_id and cluster_id.
Raw manifest deploy — kubectl apply-equivalent through the kubernetes Python SDK.
Helm release deploy — installs and upgrades Helm charts against the target.
Rollback — one-button rollback for both manifests and Helm releases.
Status polling — cron-driven status refresh; readiness reflected on the deployment record.
Audit trail — every deploy/rollback recorded as a chatter message on the deployment.
Premium-gated — requires the patrii_k8s_deploy premium feature.
Integrates With
lynx_patrii_cloud_connector — uses its API client to fetch kubeconfigs from Magnum.
lynx_api — emits patrii.k8s.deployment.ready and patrii.k8s.deployment.failed.
Models
lynx.k8s.target — one bound K8s cluster (Patrii Magnum or BYO kubeconfig).
lynx.k8s.deployment — one workload deployed to a target.
Depends on
Try Lynx Patrii Cloud K8s Deploy on your team.
Free trial, no credit card. Talk to sales when you're ready.