Enable fips checks

[JasonPowr]

Summary by Sourcery

Enable FIPS checks in CI pipelines and mark the operator as FIPS-compliant

Enhancements:

• Add fips-check parameter set to true across operator and bundle Tekton pipeline definitions for pull-request and push workflows
• Update bundle Dockerfile and ClusterServiceVersion manifest to label the operator as FIPS-compliant

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

This PR enables FIPS compliance by introducing a FIPS_CHECK parameter to the Tekton CI pipelines for both pull request and push workflows and updating bundle and operator CSV metadata labels to mark them as FIPS-compliant.

Entity relationship diagram for updated FIPS-compliant metadata labels

erDiagram
  OPERATOR_BUNDLE {
    string name
    string fips-compliant
  }
  CLUSTERSERVICEVERSION {
    string name
    string fips-compliant
  }
  OPERATOR_BUNDLE ||--|| CLUSTERSERVICEVERSION : contains
  OPERATOR_BUNDLE ||--|| CLUSTERSERVICEVERSION : mirrors fips-compliant

Loading

File-Level Changes

Change	Details	Files
Enable FIPS check in CI pipelines	Add a fips-check parameter with value "true" to pull-request bundle pipeline Add a fips-check parameter with value "true" to push bundle pipeline Add a fips-check parameter with value "true" to pull-request operator pipeline Add a fips-check parameter with value "true" to push operator pipeline	.tekton/rhtas-operator-bundle-pull-request.yaml .tekton/rhtas-operator-bundle-push.yaml .tekton/rhtas-operator-pull-request.yaml .tekton/rhtas-operator-push.yaml
Mark bundle as FIPS-compliant	Change features.operators.openshift.io/fips-compliant label to "true"	bundle.Dockerfile
Mark operator CSV as FIPS-compliant	Update clusterserviceversion annotation features.operators.openshift.io/fips-compliant to "true"	config/manifests/bases/rhtas-operator.clusterserviceversion.yaml

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[JasonPowr]

/retest

[sourcery-ai]

New security issues found

[sourcery-ai]

security (generic-api-key): Detected a Generic API Key, potentially exposing access to various services and sensitive operations.

Source: gitleaks

[sourcery-ai]

security (generic-api-key): Detected a Generic API Key, potentially exposing access to various services and sensitive operations.

Source: gitleaks

[sourcery-ai]

security (generic-api-key): Detected a Generic API Key, potentially exposing access to various services and sensitive operations.

Source: gitleaks

[sourcery-ai]

security (generic-api-key): Detected a Generic API Key, potentially exposing access to various services and sensitive operations.

Source: gitleaks