openshift-docs icon indicating copy to clipboard operation
openshift-docs copied to clipboard

OSDOCS10256: Added a section regarding FIPS compliant support for cert manager

Open subhtk opened this issue 1 year ago • 5 comments
trafficstars

Version(s): 4.12+

Issue: https://issues.redhat.com/browse/OSDOCS-10256

Link to docs preview: https://76688--ocpdocs-pr.netlify.app/openshift-enterprise/latest/security/cert_manager_operator/index.html#cert-manager-fips-support_cert-manager-operator-about

QE review:

  • [ ] QE has approved this change.

Additional information:

subhtk avatar May 30 '24 08:05 subhtk

🤖 Mon Jul 08 14:01:00 - Prow CI generated the docs preview:

https://76688--ocpdocs-pr.netlify.app/openshift-enterprise/latest/security/cert_manager_operator/index.html

ocpdocs-previewbot avatar May 30 '24 08:05 ocpdocs-previewbot

/test validate-portal

subhtk avatar Jul 01 '24 17:07 subhtk

@lunarwhite could you please help take a look? thanks. cc @xingxingxia

lihongan avatar Jul 03 '24 01:07 lihongan

/cc

lunarwhite avatar Jul 03 '24 03:07 lunarwhite

/label peer-review-needed

subhtk avatar Jul 08 '24 08:07 subhtk

@subhtk: 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.

openshift-ci[bot] avatar Jul 08 '24 14:07 openshift-ci[bot]

/label merge-review-needed

subhtk avatar Jul 08 '24 14:07 subhtk

@jeana-redhat: Those labels are not set on the issue: merge-review-in-progress

In response to this:

LGTM

/remove-label merge-review-in-progress /remove-label merge-review-needed

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.

openshift-ci[bot] avatar Jul 08 '24 14:07 openshift-ci[bot]

/cherrypick enterprise-4.17

jeana-redhat avatar Jul 08 '24 14:07 jeana-redhat

/cherrypick enterprise-4.16

jeana-redhat avatar Jul 08 '24 14:07 jeana-redhat

/cherrypick enterprise-4.15

jeana-redhat avatar Jul 08 '24 14:07 jeana-redhat

/cherrypick enterprise-4.14

jeana-redhat avatar Jul 08 '24 14:07 jeana-redhat

@jeana-redhat: new pull request created: #78562

In response to this:

/cherrypick enterprise-4.17

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.

@jeana-redhat: new pull request created: #78563

In response to this:

/cherrypick enterprise-4.16

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.

@jeana-redhat: new pull request created: #78564

In response to this:

/cherrypick enterprise-4.15

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.

@jeana-redhat: #76688 failed to apply on top of branch "enterprise-4.14":

Applying: Added FIPS compliance for cert manager section
Using index info to reconstruct a base tree...
M	security/cert_manager_operator/index.adoc
Falling back to patching base and 3-way merge...
Auto-merging security/cert_manager_operator/index.adoc
CONFLICT (content): Merge conflict in security/cert_manager_operator/index.adoc
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 Added FIPS compliance for cert manager section
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:

/cherrypick enterprise-4.14

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.