-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Make manifests usable by Kustomize #1367
Make manifests usable by Kustomize #1367
Conversation
karpoftea
commented
Oct 12, 2021
- Group manifests by purpose
- Add kustomization.yaml for each group to benefit for users that prefer Kustomize
- Move examples to appropriate folder
We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for all the commit author(s) or Co-authors. If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google. ℹ️ Googlers: Go here for more info. |
e050136
to
e8061da
Compare
@googlebot I fixed it. |
I think somehow we need to disable one of the check for CRD drift between |
thanks! i'll see what i can do and submit a change |
e8061da
to
d1fe030
Compare
We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for all the commit author(s) or Co-authors. If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google. ℹ️ Googlers: Go here for more info. |
d1fe030
to
62aa142
Compare
I've simply added |
* Add kustomization manifests * exlcude kustomization.yaml from detect-crds-drift build step