GA: Promote Kustomization API to kustomize.toolkit.fluxcd.io/v1#822
GA: Promote Kustomization API to kustomize.toolkit.fluxcd.io/v1#822stefanprodan merged 11 commits intomainfrom
kustomize.toolkit.fluxcd.io/v1#822Conversation
Signed-off-by: Stefan Prodan <stefan.prodan@gmail.com>
a091558 to
67f19f2
Compare
Signed-off-by: Sanskar Jaiswal <jaiswalsanskar078@gmail.com>
Signed-off-by: Stefan Prodan <stefan.prodan@gmail.com>
Signed-off-by: Stefan Prodan <stefan.prodan@gmail.com>
Signed-off-by: Stefan Prodan <stefan.prodan@gmail.com>
Signed-off-by: Stefan Prodan <stefan.prodan@gmail.com>
Signed-off-by: Sanskar Jaiswal <jaiswalsanskar078@gmail.com>
Signed-off-by: Sanskar Jaiswal <jaiswalsanskar078@gmail.com>
Signed-off-by: Sanskar Jaiswal <jaiswalsanskar078@gmail.com>
Signed-off-by: Sanskar Jaiswal <jaiswalsanskar078@gmail.com>
e56c397 to
9764b8d
Compare
There was a problem hiding this comment.
This looks good enough to me to be released.
In terms of the spec doc, I think it could use another proof read to see if more interlinking between sections is possible, and to align tone of voice between different sections. In addition to reducing the usage of "kustomize-controller" as at some point based on the context it can just be called "controller", and other nits like this. But not blocking to move forward, as structure wise it's 💯.
Thanks @stefanprodan and @aryan9600 🙇 🥇
i completely agree. one particular instance that comes to mind is how can we make the sops guide and the decryption section more compatible/co-existent? |
|
Another thing I ran into is that we first talk about
but then later have a section on how this default can be changed. I think this should eventually be rewritten in a way which brings the override more to the foreground, as people who read lazily may have had their alarm bells ring before they actually notice this. |
darkowlzz
left a comment
There was a problem hiding this comment.
Left some suggestions in the API spec doc. There are some references of GitRepository instead of Kustomization which need to be fixed, but the other suggestions can be used or ignored as they may be subjective.
2fc216b to
a91e6a6
Compare
Signed-off-by: Hidde Beydals <hidde@hhh.computer>
API changes
The
Kustomizationkind was promoted from v1beta2 to v1 (GA) and deprecated fields were removed.The
kustomizations.source.toolkit.fluxcd.ioCRD contains the following versions:Upgrade
The
Kustomizationv1 API is backwards compatible with v1beta2 with the following exceptions:.spec.validationwas removed.spec.patchesStrategicMergewas removed (replaced by.spec.patches).spec.patchesJson6902was removed (replaced by.spec.patches)To upgrade from v1beta2, after deploying the new CRD and controller, set
apiVersion: kustomize.toolkit.fluxcd.io/v1in the YAML files that containKustomizationdefinitions and remove the deprecated fields if any. Bumping the API version in manifests can be done gradually. It is advised to not delay this procedure as the beta versions will be removed after 6 months.Closes: #755
Closes: #664