Skip to content

https://issues.redhat.com/browse/ACM-21429 ClusterInstance field updates #8260

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 2 commits into
base: 2.15_stage
Choose a base branch
from
Open

https://issues.redhat.com/browse/ACM-21429 ClusterInstance field updates #8260

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
5c82fdb
https://issues.redhat.com/browse/ACM-21429 for 2.15
dockerymick Sep 26, 2025
175c726
Update apis/clusterinstance.json.adoc
dockerymick Oct 28, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions apis/clusterinstance.json.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -419,10 +419,16 @@ __optional__|Specify the public Secure Shell (SSH) key to provide access to inst
This key is added to the host to allow SSH access.|string
|*nodes* +
__required__|Specify the configuration parameters for each node.|<<_rhacm-docs_apis_clusterinstance_jsoncluster_nodes,nodes>> array
|*reference* +
_required_|Specify dependencies or related objects in different namespaces.|array
|*namespace* +
_required_|Specify the namespace of the reference object.|string
Comment on lines +422 to +425
Copy link
Contributor

@sakhoury sakhoury Oct 15, 2025

Choose a reason for hiding this comment

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

Can you share where you got these fields (viz. reference and namespace) from?

Copy link
Contributor Author

@dockerymick dockerymick Oct 28, 2025

Choose a reason for hiding this comment

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

@sakhoury thanks for your patience! I was on PTO and catching up. Here is the link: https://github.com/stolostron/siteconfig/commit/a804ef8a4b8265f1469861c30a1c57a72489d413@

|*templateRefs* +
__required__|Specify the list of the references to cluster-level templates.
A cluster-level template consists of a `ConfigMap` object, in which the keys of the data field represent the kind of the installation manifests.
Cluster-level templates are instantiated once per cluster in the `ClusterInstance` CR.|array
|*hostRef* +
_optional_|Specify a reference to a `BareMetalHost` nodes that are in different namespaces. Use `hostRef` to link a resource to a specific `BareMetalHost` instance.|
|===

[[_rhacm-docs_apis_clusterinstance_jsoncluster_nodes]]
Expand Down
20 changes: 14 additions & 6 deletions mce_acm_integration/siteconfig/siteconfig_install_clusters.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -187,16 +187,21 @@ spec:
[...]
clusterImageSetNameRef: "img4.17-x86-64"
[...]
templateRefs: <6>
reference: <6>
[...]
namespace: <7>
[...]
templateRefs: <8>
- name: ibi-cluster-templates-v1
namespace: rhacm
hostRef: <9>
[...]
nodes:
[...]
bmcCredentialsName: <7>
bmcCredentialsName: <10>
name: "example-bmh-secret"
[...]
templateRefs: <8>
templateRefs: <11>
- name: ibi-node-templates-v1
namespace: rhacm
[...]
Expand All @@ -206,9 +211,12 @@ spec:
<3> Reference the `name` of one or more extra manifests `ConfigMap` objects.
<4> Reference the `name` of your pull secret.
<5> Ensure that the value of the `clusterName` field in the `ClusterInstance` custom resource matches the value of the `namespace` field.
<6> Reference the `name` of the cluster-level templates in the `spec.templateRefs` field. If you are using a default installation template, the `namespace` must match the namespace where the Operator is installed.
<7> Reference the `name` of the BMC secret.
<8> Reference the `name` of the node-level templates in the `spec.nodes.templateRefs` field. If you are using a default installation template, the `namespace` must match the namespace where the Operator is installed.
<6> Specify dependencies or related objects in different namespaces.
<7> Specify the namespace of the reference object.
<8> Reference the `name` of the cluster-level templates in the `spec.templateRefs` field. If you are using a default installation template, the `namespace` must match the namespace where the Operator is installed.
<9> Specify a refence to a `BareMetalHost` resource that is in a different resource.
<10> Reference the `name` of the BMC secret.
<11> Reference the `name` of the node-level templates in the `spec.nodes.templateRefs` field. If you are using a default installation template, the `namespace` must match the namespace where the Operator is installed.

. Apply the file and create the resource by running the following command:

Expand Down