From 028f45f0cf9dc8c6588079f901807421280f9e36 Mon Sep 17 00:00:00 2001 From: George Jenkins Date: Sat, 11 May 2024 22:40:22 -0700 Subject: [PATCH] storage --- hips/hip-00XX.md | 1 + 1 file changed, 1 insertion(+) diff --git a/hips/hip-00XX.md b/hips/hip-00XX.md index eaa3ca21..28dc73d5 100644 --- a/hips/hip-00XX.md +++ b/hips/hip-00XX.md @@ -86,6 +86,7 @@ As such, while option 1. is probably the cleanest from an implementation and use - If the user attempts to use SSA with a cluster which does not support it (unlikely: SSA [went GA](https://kubernetes.io/blog/2021/08/06/server-side-apply-ga/) in Kubernetes v1.22), Helm should error. - Client-side API object validation isn't applicable when SSA enabled (`helm install|upgrade --disable-openapi-validation`) - Hooks could be deployed with SSA. But as hook objects are not updated (create/delete only), they are not really affected +- Stored release manifests should not change (they store the object as Helm intends) ### Implementation