-
Notifications
You must be signed in to change notification settings - Fork 267
Support kustomize for S3 #350
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
Support kustomize for S3 #350
Conversation
We're going to need to use a specific version of |
kind: CustomResourceDefinition | ||
metadata: | ||
annotations: | ||
controller-gen.kubebuilder.io/version: v0.3.1-0.20200716001835-4a903ddb7005 | ||
controller-gen.kubebuilder.io/version: v0.4.0 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@jaypipes Do you think it is enough if annotated here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's not really about the annotation (that is created by the controller-gen crd
command). It's that we need to fix ALL the controllers, not just S3 :)
And the root of the fix is in how we install a specific version of controller-gen
. We're currently using go get
which has the very unfortunate side-effect of modifying the go.mod
and go.sum
file for the source repository, which isn't what we want.
I'll take a stab at trying to fix this in a less instrusive way, @ricardo-larosa.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Cool! For reference kubernetes-sigs/kubebuilder#1351
@ricardo-larosa I think we're good to close this PR out, yeah? All service controllers have now been updated for controller-gen 0.4.0 and we've ensured in our build scripts that [email protected] is installed. |
thanks @jaypipes |
Make possible to install ACK S3 via Kustomize and also fix #349
Run:
Please note it uses latest