Repository navigation
Replies: 1 comment
|
A small For a first PR, I’d start with that one type and an API-server test: apply the two fields with separate managers, toggle |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Operators that create Flux objects from Go (HelmRelease, Kustomization, GitRepository, OCIRepository, HelmRepository) cannot use server-side apply with typed apply configurations. The API modules (
helm-controller/api,kustomize-controller/api,source-controller/api) do not ship them. So consumers use unstructured objects or full typed objects, and full typed objects claim ownership of every field.controller-gen v0.23.0 can generate apply configurations from the existing kubebuilder markers (
// +kubebuilder:ac:generate=true). The output is a self-contained package next to each API version, and it contains the structural schema, soExtract…andNewTypeConverterwork.Would the maintainers accept generated apply configurations in the API modules? We can contribute the PRs.
All reactions