SSCSI-98: Add required go build flags for FIPS

[chiragkyal]

Description:

• Enable FIPS-compliant builds via GOEXPERIMENT=strictfipsruntime, CGO_ENABLED=1, and appropriate build tags.
  • -tags "strictfipsruntime,openssl"
• Update Dockerfile to print Go module build info using go version -m.

The change will modify the make build target from

go build -trimpath -ldflags ...

to

CGO_ENABLED=1 GOEXPERIMENT=strictfipsruntime go build -trimpath -tags strictfipsruntime,openssl -ldflags ...

CI Changes

• SSCSI-97: Add FIPS scanning and E2E in FIPS for SSCSI Driver and Operator release#64430

Note: Currently, we're relying on the ART golang builder to intercept the non-compliant flags forcefully. This PR is intended to make the binary FIPS compliant by default.

[openshift-ci-robot]

@chiragkyal: This pull request references SSCSI-98 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.20.0" version, but no target version was set.

In response to this:

Description:

• Enable FIPS-compliant builds via GOEXPERIMENT=strictfipsruntime, CGO_ENABLED=1, and appropriate build tags.
  • -tags "strictfipsruntime,openssl"
• Update Dockerfile to print Go module build info using go version -m.

The change will modify the make build target from

go build -trimpath -ldflags ...

to

CGO_ENABLED=1 GOEXPERIMENT=strictfipsruntime go build -trimpath -tags strictfipsruntime,openssl -ldflags ...

CI Changes

• SSCSI-97: Add FIPS scanning and E2E in FIPS for SSCSI Driver and Operator release#64430

Note: Currently, we're relying on the ART golang builder to intercept the non-compliant flags forcefully. This PR is intended to make the binary FIPS compliant by default.

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 openshift-eng/jira-lifecycle-plugin repository.

[chiragkyal]

/hold
for openshift/release#64430

[chiragkyal]

/assign @arkadeepsen @mytreya-rh

[chiragkyal]

/test all

[chiragkyal]

/hold cancel

[mytreya-rh]

/lgtm
/approve

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: chiragkyal, mytreya-rh

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [mytreya-rh]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[chiragkyal]

/retest

[emmajiafan]

/label qe-approved

[openshift-ci-robot]

@chiragkyal: This pull request references SSCSI-98 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.20.0" version, but no target version was set.

In response to this:

Description:

• Enable FIPS-compliant builds via GOEXPERIMENT=strictfipsruntime, CGO_ENABLED=1, and appropriate build tags.
  • -tags "strictfipsruntime,openssl"
• Update Dockerfile to print Go module build info using go version -m.

The change will modify the make build target from

go build -trimpath -ldflags ...

to

CGO_ENABLED=1 GOEXPERIMENT=strictfipsruntime go build -trimpath -tags strictfipsruntime,openssl -ldflags ...

CI Changes

• SSCSI-97: Add FIPS scanning and E2E in FIPS for SSCSI Driver and Operator release#64430

Note: Currently, we're relying on the ART golang builder to intercept the non-compliant flags forcefully. This PR is intended to make the binary FIPS compliant by default.

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 openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci]

@chiragkyal: all tests passed!

Full PR test history. Your PR dashboard.

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-sigs/prow repository. I understand the commands that are listed here.