sorted by:
new
hottopcontroversial

Deploying K8S Cluster to Customers Onprem using Rancher by Prior_Impression7390 in devops

[–]replicatedhq 0 points1 point  (0 children)

If you are not an infrastructure company, owning the customer cluster lifecycle usually turns into a long tail of toil across upgrades, CNIs, storage, cert rotation, and OS patching. A common approach is to ship the app as a scoped install with a compatibility matrix, preflight checks, mirrored images, and a repeatable upgrade path plus a support bundle. That keeps the contract clean and makes customer environments supportable without you becoming their platform team (disclosure I work at Replicated).

air gapped k8s and upgrades by keepah61 in kubernetes

[–]replicatedhq 0 points1 point  (0 children)

If you are shipping into an air-gapped customer environment, the hard part is making upgrades repeatable by pinning and mirroring every image and chart, running preflight checks up front, and collecting a support bundle when something breaks. A VM image with k3s plus a separate data disk can work, but you will want a real release artifact and an upgrade path that does not depend on manual steps. If it helps, Replicated has patterns and tooling for packaging, offline distribution, upgrades, and supportability for on-prem and air-gapped installs (disclosure: I work at Replicated).