#16219: Kubernetes self re-deploy openclaw

<!-- greptile_comment --> <h3>Greptile Summary</h3> Comprehensive Kubernetes deployment infrastructure that packages OpenClaw as a Helm chart with Flux/Argo-ready Kustomize overlays. Implementation includes proper security contexts, persistent volumes for state management, optional ingress, and GitOps-friendly configuration. - Helm chart provides flexible deployment with configurable persistence, resources, and security contexts - Kustomize overlays for dev/prod environments with appropriate resource sizing - Init container handles volume permissions (UID 1000) before main container starts - Security context configured with `runAsNonRoot: true`, dropped capabilities, and `allowPrivilegeEscalation: false` - Documentation includes architecture diagrams and examples for Flux and Argo CD integration - Extensibility through `extraContainers`, `extraVolumes`, and `extraVolumeMounts` for sidecars The infrastructure is production-ready and follows Kubernetes best practices. Previous comments about fork-specific URLs in documentation examples should be addressed before merge. <h3>Confidence Score: 4/5</h3> - This PR is safe to merge with minor documentation updates needed for upstream repository references. - The implementation is solid with proper security configurations, well-structured Helm charts, and comprehensive documentation. The code follows Kubernetes best practices including security contexts, RBAC, and resource management. The only issues are documentation references to fork-specific URLs that should point to the upstream repository, which have already been flagged in previous comments. - Documentation files (`deploy/kubernetes/README.md` and `docs/kubernetes.md`) need URL updates to reference upstream repository instead of fork. _{Last reviewed commit: ef674ae} <!-- greptile_other_comments_section --> <!-- /greptile_comment -->