-
Notifications
You must be signed in to change notification settings - Fork 4
-
Notifications
You must be signed in to change notification settings - Fork 4
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
[spike] Decide on how to package and deploy the pipeline manifests #10
[spike] Decide on how to package and deploy the pipeline manifests #10
Comments
/sig devsecops |
@codificat: The label(s) In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Trying again: |
/wg cnbi |
Many k8s operators appears to do that, but in my opinion they should not. The Roles needed for installing and running are not the same.
Is is a good resume to say that those two options bog down to bundle the pipelines with the operator, or separately ? Note that we could combine the two. |
Note from the meeting yesterday: might have some troubles using KfDef since it's using kustomize which is less powerful (if simpler) than something like helm (=> array merging in yaml) |
/reopen |
@codificat: Reopened this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Removed the revised-size as the issue is yet to be marked done. |
At the time of this writing, the pipeline manifests for the CNBi feature implemented via the Meteor operator are added in the operator's repo under the
hack/
directory and deployed via theMakefile
.The pipelines should eventually be properly packaged and deployed.
Options:
The text was updated successfully, but these errors were encountered: