-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[crd-generator] Generated CRD YAML is not always the same when using @PrinterColumn #3040
Comments
metacosm
added a commit
that referenced
this issue
Apr 30, 2021
metacosm
added a commit
that referenced
this issue
Apr 30, 2021
11 tasks
metacosm
added a commit
that referenced
this issue
Apr 30, 2021
metacosm
added a commit
that referenced
this issue
May 4, 2021
metacosm
added a commit
that referenced
this issue
May 4, 2021
manusa
pushed a commit
that referenced
this issue
May 12, 2021
manusa
pushed a commit
that referenced
this issue
May 12, 2021
Great, thank you very much 👍🏻 |
ddl-audi
pushed a commit
to ddl-audi/kubernetes-client
that referenced
this issue
May 14, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello,
I've been migrating some internal operator from the go-based CRD generation to the Java based one. Thanks for this lib.
A minor inconvenience I noticed is that, when using additional printer column via the
@PrinterColumn
annotation, the generated YAML may change at each build because the order of the additionalPrinterColumns in the YAML is not consistent.This cause the digest of the docker image to change each build, which cause our CD to deploy the operator.
My current workaround is something like
to make the order predictable.
Cheers
The text was updated successfully, but these errors were encountered: