H4HIP: Server Side Apply support #312
Conversation
gjenkins8
force-pushed
the
server_side_apply_hip
branch
from
95e4e59 to
3c11723
Compare
gjenkins8
changed the title
hips/hip-00XX.md
Outdated
|
|
||
| #### Special | ||
|
|
||
| - `--dry-run=client` doesn't work with SSA enabled |
There was a problem hiding this comment.
@mattfarina points out that this will make it difficult for user's to preview changes
hips/hip-00XX.md
Outdated
|
|
||
| #### Conflicts and forcing | ||
|
|
||
| It is possible when Helm upgrades a chart, that there will be a field conflict with another field manager. In this case, Helm should report the error to the user. |
There was a problem hiding this comment.
TODO: verify we can abort atomically across multiple objects (Ian Z points this out)
|
@gjenkins8 I think this HIP as written would apply to the release secret itself, too. Am I correct with this understanding? We're running into the issue that the release secret is > 1MB in https://github.com/community-tooling/charts because of the |
gjenkins8
force-pushed
the
server_side_apply_hip
branch
4 times, most recently
from
e1e4d73 to
9048d85
Compare
Signed-off-by: George Jenkins <[email protected]>
gjenkins8
force-pushed
the
server_side_apply_hip
branch
from
028f45f to
82b28b6
Compare
Signed-off-by: George Jenkins <[email protected]>
gjenkins8
changed the title
Signed-off-by: George Jenkins <[email protected]>
Signed-off-by: George Jenkins <[email protected]>
| Allowing Helm to update objects which have been modified by other processes. | ||
| Kubernetes now offers a similar server-side process that has several advantages over the client-side apply (CSA) methods that Helm and `kubectl` (for example) have traditionally utilized. | ||
|
|
||
| ## Motivation |
There was a problem hiding this comment.
Perhaps also include that client-side validation is now largely unsupported (need to read up on the details):
HIP for Helm to support SSA