Skip to content

OSDOCS#19442: Correct TLS configuration content - MicroShift#111698

Open
tmalove wants to merge 2 commits into
openshift:mainfrom
tmalove:OSDOCS-19442
Open

OSDOCS#19442: Correct TLS configuration content - MicroShift#111698
tmalove wants to merge 2 commits into
openshift:mainfrom
tmalove:OSDOCS-19442

Conversation

@tmalove
Copy link
Copy Markdown
Contributor

@tmalove tmalove commented May 15, 2026

Version(s):
4.22+

Issue:
OSDOCS-19442

Link to docs preview:
Creating a secret for the ingress controller certificateSecret
Creating a route through an Ingress object

QE review:

  • QE has approved this change.

Additional information:
none

@openshift-ci openshift-ci Bot added the size/S Denotes a PR that changes 10-29 lines, ignoring generated files. label May 15, 2026
To serve a custom default certificate through the ingress controller in {microshift-short}, you can create a TLS secret containing your certificate chain and private key, then set the `certificateSecret` value in the configuration file to that secret name.
You can provide a custom default certificate for the {microshift-short} ingress router by creating a TLS secret and updating the configuration file. This ensures that the ingress controller uses your specific certificate to secure network traffic instead of the generated default.

To configure application-level certificates for a Kubernetes Ingress object by using the `spec.tls` field, follow the procedure in xref:../../microshift_networking/microshift-configuring-routes.adoc#nw-ingress-creating-a-route-via-an-ingress_microshift-configuring-routes[Creating a route through an Ingress object].
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

🤖 [error] OpenShiftAsciiDoc.NoXrefInModules: Do not include xrefs in modules, only assemblies (exception: release notes modules).

To serve a custom default certificate through the ingress controller in {microshift-short}, you can create a TLS secret containing your certificate chain and private key, then set the `certificateSecret` value in the configuration file to that secret name.
You can provide a custom default certificate for the {microshift-short} ingress router by creating a TLS secret and updating the configuration file. This ensures that the ingress controller uses your specific certificate to secure network traffic instead of the generated default.

To configure application-level certificates for a Kubernetes Ingress object by using the `spec.tls` field, follow the procedure in xref:../microshift_networking/microshift-configuring-routes.adoc#nw-ingress-creating-a-route-via-an-ingress_microshift-configuring-routes[Creating a route through an Ingress object].
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

🤖 [error] OpenShiftAsciiDoc.NoXrefInModules: Do not include xrefs in modules, only assemblies (exception: release notes modules).

@openshift-ci
Copy link
Copy Markdown

openshift-ci Bot commented May 15, 2026

@tmalove: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/validate-portal a295d40 link true /test validate-portal

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.

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

Labels

size/S Denotes a PR that changes 10-29 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants