docs: replace "ephemeral cluster" with "Bonfire host cluster" in namespace workflow#592
Conversation
…space workflow In OpenShift CI, "ephemeral cluster" conventionally refers to temporary clusters that are created, tested, and destroyed. The permanent central cluster used for Bonfire namespace management is not ephemeral — it is a long-lived host cluster. This commit updates the ephemeral-namespace-workflow documentation (introduced in PR openshift#590) to use "Bonfire host cluster" instead of "ephemeral cluster" when referring to the permanent cluster that hosts the Ephemeral Namespace Operator and namespace pools. File names in SHARED_DIR (ephemeral-kubeconfig, ephemeral-cluster-server, ephemeral-namespace) are left unchanged as they are actual artifact names used by the workflow steps.
|
@redhat-ship-help: GitHub didn't allow me to request PR reviews from the following users: openshift/ci-docs-reviewers. Note that only openshift members and repo collaborators can review this PR, and authors cannot review their own PRs. DetailsIn response to this:
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. |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: redhat-ship-help The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
openshift-ci
bot
added
the
needs-ok-to-test
|
Hi @redhat-ship-help. 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 Regular contributors should join the org to skip this step. Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. DetailsInstructions 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. |
|
/ok-to-test |
openshift-ci
bot
added
ok-to-test
|
@redhat-ship-help: The following test failed, say
Full PR test history. Your PR dashboard. DetailsInstructions 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. |
2 participants
Summary
Replaces all 13 occurrences of "ephemeral cluster" with "Bonfire host cluster" in the ephemeral-namespace-workflow how-to page introduced by #590.
Motivation
In OpenShift CI, "ephemeral cluster" conventionally refers to temporary clusters that are provisioned, tested, and then destroyed (e.g. via the
ipi-installworkflow or the Ephemeral Clusters in Konflux CI feature).The permanent, long-lived cluster that hosts the Ephemeral Namespace Operator and Bonfire namespace pools is not ephemeral — it is a central host cluster. Calling it "the ephemeral cluster" in the documentation creates confusion with the established meaning of the term.
This PR updates the prose to refer to it as the Bonfire host cluster to clearly distinguish it from actual ephemeral (temporary) clusters.
What changed
content/en/how-tos/ephemeral-namespace-workflow.mdSHARED_DIR(ephemeral-kubeconfig,ephemeral-cluster-server,ephemeral-namespace) are unchanged — these are actual artifact names used by the workflow stepsWhat did NOT change
/cc @openshift/ci-docs-reviewers