Skip to content

Conversation

@tmalove
Copy link
Contributor

@tmalove tmalove commented Jul 13, 2023

This PR is to port the "Security and compliance" OCP content to ROSA. Reference that section only for comments, reviews, etc.
OSDOCS-3995

Version(s):

Link to docs preview (local build): https://file.rdu.redhat.com/tlove/sd-port-security-tlove/security/index.html (Updated 3/5)

QE review:

  • QE has approved this change.

@openshift-ci openshift-ci bot added the size/L Denotes a PR that changes 100-499 lines, ignoring generated files. label Jul 13, 2023
@tmalove tmalove force-pushed the sd-port-security-tlove branch from 85e8fba to 11f19ae Compare July 19, 2023 18:20
@ocpdocs-previewbot
Copy link

ocpdocs-previewbot commented Jul 19, 2023

🤖 Fri Feb 09 18:30:23 - Prow CI generated the docs preview: https://62384--ocpdocs-pr.netlify.app

@tmalove tmalove force-pushed the sd-port-security-tlove branch from 11f19ae to 02911e0 Compare July 20, 2023 13:49
@tmalove
Copy link
Contributor Author

tmalove commented Aug 1, 2023

@jaybeeunix @xueli181114 See this spreadsheet of errors I get from testing CLI commands in the security section. This list is still WIP. Thx.
https://docs.google.com/document/d/1EE4o5iF9bXMZS20DeeuJkd-UakZnKssVXcjsaFrPvx4/edit#heading=h.g1x54zpbotj

@xiaojiey
Copy link
Contributor

@xingxingxia @geliu2016 @sunilcio @wangke19 Could you please help to review for your components? thanks.
I will check for Compliance Operator, File Integrity Operator and Security Profiles Operator.

Comment on lines 416 to 497
- Name: Authenticating the cert-manager Operator for Red Hat OpenShift with GCP Workload Identity
File: cert-manager-authenticate-gcp
- Name: Authenticating the cert-manager Operator for Red Hat OpenShift on AWS
File: cert-manager-authentication-non-sts
- Name: Authenticating the cert-manager Operator for Red Hat OpenShift on GCP
File: cert-manager-authenticate-non-sts-gcp
Copy link
Contributor

Choose a reason for hiding this comment

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

It is ROSA document for ROSA cluster, then GCP documents cert-manager-authenticate-gcp and cert-manager-authenticate-non-sts-gcp are not applicable, need be removed.
cert-manager-operator-issuer-acme has GCP ambient credential section, that is also not applicable for ROSA cluster.

@wangke19
Copy link

Apiserver topics look good to me. But I checked the link https://file.rdu.redhat.com/tlove/sd-port-security-tlove/upgrading/rosa-upgrading-cluster-prepare.html, we still has this upgrade path, I think that's a problem.

Preparing to upgrade ROSA to 4.9 

@xiaojiey
Copy link
Contributor

For Compliance Operator, generally it is good. There are minor issues need to be updated:

  1. For important notice in https://file.rdu.redhat.com/tlove/sd-port-security-tlove/security/compliance_operator/compliance-operator-supported-profiles.html, better to remove unreleated platforms:
    Current: "The Compliance Operator might report incorrect results on managed platforms, such as OpenShift Dedicated, Red Hat OpenShift Service on AWS, and Azure Red Hat OpenShift. For more information, see the Red Hat Knowledgebase Solution #6983418."
    Better to be: "The Compliance Operator might report incorrect results on Red Hat OpenShift Service on AWS. For more information, see the Red Hat Knowledgebase Solution #6983418."
  2. For important notice in https://file.rdu.redhat.com/tlove/sd-port-security-tlove/security/compliance_operator/compliance-operator-installation.html,
    Current: "The Compliance Operator might report incorrect results on managed platforms, such as OpenShift Dedicated, Red Hat OpenShift Service on AWS, and Microsoft Azure Red Hat OpenShift. For more information, see the Red Hat Knowledgebase Solution #6983418."
    Better to be: "The Compliance Operator might report incorrect results on Red Hat OpenShift Service on AWS. For more information, see the Red Hat Knowledgebase Solution #6983418."

@tmalove tmalove force-pushed the sd-port-security-tlove branch from 02911e0 to 2cdebf9 Compare August 22, 2023 16:11
@openshift-merge-robot openshift-merge-robot added needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. and removed needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. labels Aug 22, 2023
@openshift-ci openshift-ci bot added size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. and removed size/L Denotes a PR that changes 100-499 lines, ignoring generated files. labels Aug 23, 2023
@tmalove tmalove force-pushed the sd-port-security-tlove branch from d07bf0b to aea07ed Compare August 24, 2023 15:11
@openshift-ci openshift-ci bot added size/L Denotes a PR that changes 100-499 lines, ignoring generated files. and removed size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. labels Aug 24, 2023
@tmalove tmalove force-pushed the sd-port-security-tlove branch 4 times, most recently from 507da05 to 61895ed Compare August 28, 2023 19:53
@BhargaviGudi
Copy link

BhargaviGudi commented Aug 29, 2023

For file-integrity-operator, generally it is good. There are minor changes need to be updated:

  1. Commands under below links needs to be appended with namespace name (-n openshift-file-integrity)
    a. https://file.rdu.redhat.com/tlove/sd-port-security-tlove/security/file_integrity_operator/file-integrity-operator-understanding.html#checking-the-file-integrity-CR-status_file-integrity-operator
    b. https://file.rdu.redhat.com/tlove/sd-port-security-tlove/security/file_integrity_operator/file-integrity-operator-understanding.html#understanding-file-integrity-node-statuses-object_file-integrity-operator
    c. https://file.rdu.redhat.com/tlove/sd-port-security-tlove/security/file_integrity_operator/file-integrity-operator-understanding.html#file-integrity-node-status-failure_file-integrity-operator
    d. https://file.rdu.redhat.com/tlove/sd-port-security-tlove/security/file_integrity_operator/file-integrity-operator-understanding.html#file-integrity-events_file-integrity-operator
    e. https://file.rdu.redhat.com/tlove/sd-port-security-tlove/security/file_integrity_operator/file-integrity-operator-configuring.html#file-integrity-examine-default-config_file-integrity-operator
    f. https://file.rdu.redhat.com/tlove/sd-port-security-tlove/security/file_integrity_operator/file-integrity-operator-configuring.html#file-integrity-operator-defining-custom-config_file-integrity-operator
    g. https://file.rdu.redhat.com/tlove/sd-port-security-tlove/security/file_integrity_operator/file-integrity-operator-advanced-usage.html#file-integrity-operator-reinitializing-database_file-integrity-operator
    h. https://file.rdu.redhat.com/tlove/sd-port-security-tlove/security/file_integrity_operator/file-integrity-operator-troubleshooting.html#determining-the-fileintegrity-objects-phase

  2. For Understanding the FileIntegrityNodeStatuses object, https://file.rdu.redhat.com/tlove/sd-port-security-tlove/security/file_integrity_operator/file-integrity-operator-understanding.html#understanding-file-integrity-node-statuses-object_file-integrity-operator , Example Output needs to be updated.
    Sample output:

$ oc get fileintegritynodestatuses -n openshift-file-integrity
NAME                                                              NODE                                         STATUS
worker-fileintegrity-ip-10-0-145-177.us-east-2.compute.internal   ip-10-0-145-177.us-east-2.compute.internal   Succeeded
worker-fileintegrity-ip-10-0-171-252.us-east-2.compute.internal   ip-10-0-171-252.us-east-2.compute.internal   Succeeded
worker-fileintegrity-ip-10-0-193-251.us-east-2.compute.internal   ip-10-0-193-251.us-east-2.compute.internal   Succeeded
  1. Defining a custom File Integrity Operator configuration,https://file.rdu.redhat.com/tlove/sd-port-security-tlove/security/file_integrity_operator/file-integrity-operator-configuring.html#file-integrity-operator-defining-custom-config_file-integrity-operator , Step 7 need to update command to create fileintegrity.
    Currently only fileintegrity config is given.
    Add command: $ oc create -f master-fileintegrity.yaml -n openshift-file-integrity

@xiaojiey
Copy link
Contributor

For Compliance Operator, below points are not applicable:

  1. For important notice in https://file.rdu.redhat.com/tlove/sd-port-security-tlove/security/compliance_operator/compliance-operator-supported-profiles.html, better to remove unreleated platforms:
    Current: "The Compliance Operator might report incorrect results on managed platforms, such as OpenShift Dedicated, Red Hat OpenShift Service on AWS, and Azure Red Hat OpenShift. For more information, see the Red Hat Knowledgebase Solution #6983418."
    Better to be: "The Compliance Operator might report incorrect results on Red Hat OpenShift Service on AWS. For more information, see the Red Hat Knowledgebase Solution #6983418."

  2. For important notice in https://file.rdu.redhat.com/tlove/sd-port-security-tlove/security/compliance_operator/compliance-operator-installation.html,
    Current: "The Compliance Operator might report incorrect results on managed platforms, such as OpenShift Dedicated, Red Hat OpenShift Service on AWS, and Microsoft Azure Red Hat OpenShift. For more information, see the Red Hat Knowledgebase Solution #6983418."
    Better to be: "The Compliance Operator might report incorrect results on Red Hat OpenShift Service on AWS. For more information, see the Red Hat Knowledgebase Solution #6983418."

  3. For paragraph below, it is not applicable for ROSA as it is for hypershift hosted cluster only
    https://file.rdu.redhat.com/tlove/sd-port-security-tlove/security/compliance_operator/compliance-operator-installation.html#installing-compliance-operator-hcp_compliance-operator-installation

  4. For paragraph below, it is not applicable for ROSA as creating custom mcp will fail. https://docs.openshift.com/container-platform/4.13/security/compliance_operator/compliance-operator-remediation.html#compliance-operator-apply-remediation-for-customized-mcp
    https://docs.openshift.com/container-platform/4.13/security/compliance_operator/compliance-operator-remediation.html#compliance-custom-node-pools_compliance-remediation

@tmalove tmalove force-pushed the sd-port-security-tlove branch 3 times, most recently from 17b9bc2 to 551a033 Compare August 29, 2023 20:49
@tmalove tmalove changed the title OSDOCS#3995: ROSA - port security content from OCP OSDOCS#3995: ROSA - port 'Security' content from OCP Aug 29, 2023
@tmalove
Copy link
Contributor Author

tmalove commented Aug 29, 2023

Apiserver topics look good to me. But I checked the link file.rdu.redhat.com/tlove/sd-port-security-tlove/upgrading/rosa-upgrading-cluster-prepare.html, we still has this upgrade path, I think that's a problem.

Preparing to upgrade ROSA to 4.9 

@wangke19 When this was initially added, the admin acknowledgment was a new requirement. However, all major versions require this now. I will follow up with SRE to confirm. Thanks.

@tmalove
Copy link
Contributor Author

tmalove commented Aug 30, 2023

@sheriff-rh @bergerhoffer @xenolinux adding you for your awareness.

@tmalove tmalove force-pushed the sd-port-security-tlove branch from 7a7c941 to d535ea0 Compare January 30, 2024 15:49
@tmalove
Copy link
Contributor Author

tmalove commented Jan 30, 2024

/test validate-asciidoc

1 similar comment
@tmalove
Copy link
Contributor Author

tmalove commented Jan 31, 2024

/test validate-asciidoc

@tmalove
Copy link
Contributor Author

tmalove commented Jan 31, 2024

/retest

@tmalove
Copy link
Contributor Author

tmalove commented Feb 1, 2024

/test validate-asciidoc

@tmalove tmalove force-pushed the sd-port-security-tlove branch 2 times, most recently from 0feb202 to bf26e79 Compare February 5, 2024 14:33
@tmalove
Copy link
Contributor Author

tmalove commented Feb 5, 2024

/retest

@tmalove tmalove force-pushed the sd-port-security-tlove branch from 97ded61 to f07c973 Compare February 6, 2024 14:25
@tmalove
Copy link
Contributor Author

tmalove commented Feb 6, 2024

/retest

@tmalove
Copy link
Contributor Author

tmalove commented Feb 6, 2024

/retest-required

@tmalove tmalove force-pushed the sd-port-security-tlove branch from f07c973 to fdd4c69 Compare February 6, 2024 15:31
- Name: Deployments
Dir: deployments
Distros: openshift-rosa
Topics:
Copy link
Contributor

Choose a reason for hiding this comment

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

Put back this line. removing it breaks the build

Copy link
Contributor

Choose a reason for hiding this comment

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

Whole stanza should look like:

Topics:
- Name: Deployments
  Dir: deployments
  Distros: openshift-rosa
  Topics:
  - Name: Custom domains for applications
    File: osd-config-custom-domains-applications

@tmalove tmalove force-pushed the sd-port-security-tlove branch from a81d173 to 43efa43 Compare February 7, 2024 15:10
@tmalove tmalove force-pushed the sd-port-security-tlove branch from 43efa43 to b579c62 Compare February 9, 2024 18:23
@openshift-ci
Copy link

openshift-ci bot commented Feb 9, 2024

@tmalove: 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/test-infra repository. I understand the commands that are listed here.

@tmalove
Copy link
Contributor Author

tmalove commented Feb 12, 2024

@arendej @rhmdnd @BillDett the preview is updated with the removal of the 'Compliance Operator' and 'File Integrity Operator' sections FYI. Thanks!

@codymant
Copy link

@tmalove the netflix preview link doesn't seem to work any more. Is there another link somewhere? Eric Chapman and Austin Quam would like to review and share feedback if the review window is still open.

https://62384--ocpdocs-pr.netlify.app/openshift-rosa/latest/welcome/index.html

@tmalove
Copy link
Contributor Author

tmalove commented Mar 5, 2024

@tmalove the netflix preview link doesn't seem to work any more. Is there another link somewhere? Eric Chapman and Austin Quam would like to review and share feedback if the review window is still open.

62384--ocpdocs-pr.netlify.app/openshift-rosa/latest/welcome/index.html

@codymant An updated preview is available, however VPN/network access is required. Let me know if Eric or Austin cannot access it.

@tmalove
Copy link
Contributor Author

tmalove commented Mar 11, 2024

This PR is superseded by #72837. Refer to this PR for the Security porting project.

@tmalove
Copy link
Contributor Author

tmalove commented Apr 9, 2024

@rhmdnd @BillDett @arendej @xingxingxia Use this latest PR for updates on the 'Security and compliance' porting.

@tmalove
Copy link
Contributor Author

tmalove commented Apr 9, 2024

Refer to the latest PR to continue updates.

@tmalove tmalove closed this Apr 9, 2024
@tmalove tmalove deleted the sd-port-security-tlove branch April 9, 2024 17:39
@xingxingxia
Copy link
Contributor

@rhmdnd @BillDett @arendej @xingxingxia Use this latest #72837 for updates on the 'Security and compliance' porting.

@tmalove got it. For me, what I reviewed was for cert-manager as in my previous comment #62384 (comment) . In the new PR, seems cert-manager doc is totally removed. Anyway nvm, I'm transfering to @lunarwhite to continue review for cert-manager area in the new PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. size/XL Denotes a PR that changes 500-999 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.