OSDOCS-20001: Fix invalid componentName and empty egress in ExternalS…

[sampadasawant-36]

…ecretsConfig documentation

• Replace invalid componentName: CoreController with the correct CRD enum value ExternalSecretsCoreController in the allow-all-traffic egress module.
• Replace the null egress: (deny-all) with egress: - {} (allow all) in the allow-all-traffic module.
• Replace egress: - {} (empty object) with an explicit port 443/TCP egress rule in the create-externalsecretsconfig module.

Resolves: OSDOCS-20001

Version(s):

Issue:

Link to docs preview:

QE review:

• QE has approved this change.

Additional information:

[openshift-ci-robot]

@sampadasawant-36: This pull request references OSDOCS-20001 which is a valid jira issue.

Details

In response to this:

…ecretsConfig documentation

• Replace invalid componentName: CoreController with the correct CRD enum value ExternalSecretsCoreController in the allow-all-traffic egress module.
• Replace the null egress: (deny-all) with egress: - {} (allow all) in the allow-all-traffic module.
• Replace egress: - {} (empty object) with an explicit port 443/TCP egress rule in the create-externalsecretsconfig module.

Resolves: OSDOCS-20001

Version(s):

Issue:

Link to docs preview:

QE review:

• QE has approved this change.

Additional information:

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]

Hi @sampadasawant-36. Thanks for your PR.

I'm waiting for a openshift member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work.

Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

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.

[dpateriya]

/ok-to-test

[ocpdocs-previewbot]

🤖 Fri Jun 12 09:21:37 - Prow CI generated the docs preview:

https://113229--ocpdocs-pr.netlify.app/openshift-enterprise/latest/security/external_secrets_operator/external-secrets-operator-config-net-policy.html
https://113229--ocpdocs-pr.netlify.app/openshift-enterprise/latest/security/external_secrets_operator/external-secrets-operator-migrate-downstream-upstream.html

[openshift-ci]

@sampadasawant-36: all tests passed!

Full PR test history. Your PR dashboard.

Details

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.