Skip to content
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

Fips fixes #789

Merged
merged 2 commits into from
Jul 5, 2023
Merged

Fips fixes #789

merged 2 commits into from
Jul 5, 2023

Conversation

tesshuflower
Copy link
Contributor

Describe what this PR does

  • Restrict metrics to TLS 1.2 (was TLS 1.3). TLS 1.3 has issues with FIPS envs in older OpenShift envs
  • also USE CGO_ENABLED=1 when building. This is really only required when using the openshift go toolset to build (for FIPS support) - but changing here so we're consistent with downstream builds.

See: https://access.redhat.com/security/vulnerabilities/RHSB-2023-001

Is there anything that requires special attention?

Related issues:

Signed-off-by: Tesshu Flower <tflower@redhat.com>
Signed-off-by: Tesshu Flower <tflower@redhat.com>
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jul 5, 2023

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: tesshuflower

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:

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

@sonarcloud
Copy link

sonarcloud bot commented Jul 5, 2023

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

No Coverage information No Coverage information
0.0% 0.0% Duplication

@tesshuflower
Copy link
Contributor Author

Will need to pull into the release-0.7 stream

/cherry-pick release-0.7

@openshift-cherrypick-robot

@tesshuflower: once the present PR merges, I will cherry-pick it on top of release-0.7 in a new PR and assign it to you.

In response to this:

Will need to pull into the release-0.7 stream

/cherry-pick release-0.7

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.

@@ -6,7 +6,7 @@ WORKDIR /workspace
# We don't vendor modules. Enforce that behavior
ENV GOFLAGS=-mod=readonly
ENV GO111MODULE=on
ENV CGO_ENABLED=0
ENV CGO_ENABLED=1
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looking at where the CGO_ENABLED=0 came in, I think it may be needed for the multi-arch builds (that we don't use)

Copy link
Member

@JohnStrunk JohnStrunk left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@codecov
Copy link

codecov bot commented Jul 5, 2023

Codecov Report

Merging #789 (6b02591) into main (ec4bcc2) will increase coverage by 0.0%.
The diff coverage is n/a.

Additional details and impacted files
@@          Coverage Diff          @@
##            main    #789   +/-   ##
=====================================
  Coverage   66.8%   66.9%           
=====================================
  Files         55      55           
  Lines       7054    7055    +1     
=====================================
+ Hits        4719    4725    +6     
+ Misses      2056    2053    -3     
+ Partials     279     277    -2     

see 1 file with indirect coverage changes

@openshift-merge-robot openshift-merge-robot merged commit 6bfd84e into backube:main Jul 5, 2023
23 checks passed
@openshift-cherrypick-robot

@tesshuflower: #789 failed to apply on top of branch "release-0.7":

Applying: restrict metrics to TLS1.2
Using index info to reconstruct a base tree...
M	bundle/manifests/volsync.clusterserviceversion.yaml
Falling back to patching base and 3-way merge...
Auto-merging bundle/manifests/volsync.clusterserviceversion.yaml
CONFLICT (content): Merge conflict in bundle/manifests/volsync.clusterserviceversion.yaml
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 restrict metrics to TLS1.2
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".

In response to this:

Will need to pull into the release-0.7 stream

/cherry-pick release-0.7

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.

tesshuflower pushed a commit to tesshuflower/volsync that referenced this pull request Jul 5, 2023
@tesshuflower tesshuflower deleted the fips_fixes branch July 5, 2023 15:40
tesshuflower pushed a commit to tesshuflower/volsync that referenced this pull request Jul 5, 2023
Fips fixes

(cherry picked from commit 6bfd84e)
Signed-off-by: Tesshu Flower <tflower@redhat.com>
openshift-merge-robot added a commit that referenced this pull request Jul 5, 2023
Merge pull request #789 from tesshuflower/fips_fixes
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants