-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Remove CGO_ENABLED=0 references for FIPS compliance #6504
Remove CGO_ENABLED=0 references for FIPS compliance #6504
Conversation
https://github.com/operator-framework/operator-sdk/actions/runs/5613582949/job/15210100650?pr=6504 For the scaffolding, we inherit
|
Signed-off-by: rashmigottipati <[email protected]>
Signed-off-by: rashmigottipati <[email protected]>
Signed-off-by: rashmigottipati <[email protected]>
…go file scaffolds Signed-off-by: rashmigottipati <[email protected]>
be56a3c
to
31a3bda
Compare
//(TODO): This removes `CGO_ENABLED=0` references from the go/v3 and go/v4-alpha scaffolds for FIPS compliance. | ||
// This is a temporary workaround to remove CGO_ENABLED=0 references in the Go plugin chain from files scaffolded from upstream plugins. | ||
// We would need to remove this when the fix is made in upstream Kubebuilder eventually. | ||
err = util.ReplaceInFile("Dockerfile", "CGO_ENABLED=0", "") | ||
if err != nil { | ||
return err | ||
} |
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 feels wrong to me to put this functionality in the manifests
plugin. Should we have a separate temporary plugin for this?
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.
Could you please elucidate what you mean by a separate temporary plugin? Would it be an overkill to have a temporary plugin just for this?
Wondering if having that would eliminate the need to make changes in the Kubebuilder, and if so, that makes sense to me. But if we need to make changes in Kubebuilder anyway, do we still want to have a separate temporary plugin for this?
Signed-off-by: rashmigottipati <[email protected]>
Signed-off-by: rashmigottipati <[email protected]>
PR needs rebase. 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. |
Issues go stale after 90d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle stale |
Stale issues rot after 30d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle rotten |
Rotten issues close after 30d of inactivity. Reopen the issue by commenting /close |
@openshift-bot: Closed this PR. 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. |
Removes all of the CGO_ENABLED=0 references in order to enable FIPS compliance