Skip to content

Commit e705f09

Browse files
slagleclaude
andcommitted
Document edpm_playbook_environment for proxy configuration
Add documentation for configuring environment variables across all data plane playbooks using the edpm_playbook_environment variable. This change adds a new optional step in the data plane node creation procedure that shows how to: - Create a secret containing the edpm_playbook_environment variable with proxy settings - Reference the secret using ansibleVarsFrom with secretRef in the OpenStackDataPlaneNodeSet CR The documentation follows the same pattern as the existing redhat-registry secret example and provides clear instructions for operators who need to configure proxy settings or other environment variables for their data plane deployments. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com> Jira: OSPRH-15529 Depends-On: openstack-k8s-operators/edpm-ansible#1049 Signed-off-by: James Slagle <jslagle@redhat.com>
1 parent c7bbe1f commit e705f09

1 file changed

Lines changed: 14 additions & 0 deletions

File tree

docs/assemblies/proc_creating-a-set-of-data-plane-nodes.adoc

Lines changed: 14 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -170,6 +170,17 @@ $ oc create secret generic redhat-registry \
170170
* Replace `<registry_username>` with the applicable user name.
171171
* Replace `<registry_password>` with the applicable password.
172172

173+
. Optional: Configure environment variables for all playbooks, such as proxy settings:
174+
+
175+
The `edpm_playbook_environment` variable sets environment variables that are applied to all tasks within all playbooks. This is useful for configuring proxy settings or other environment variables needed across the data plane deployment.
176+
+
177+
----
178+
$ oc create secret generic edpm-playbook-environment \
179+
--from-literal edpm_playbook_environment='{"HTTP_PROXY": "http://proxy.example.com:8080", "HTTPS_PROXY": "http://proxy.example.com:8080", "NO_PROXY": "localhost,127.0.0.1", "http_proxy": "http://proxy.example.com:8080", "https_proxy": "http://proxy.example.com:8080", "no_proxy": "localhost,127.0.0.1"}'
180+
----
181+
+
182+
* Replace the proxy values with your actual proxy server addresses.
183+
173184
+
174185
----
175186
apiVersion: dataplane.openstack.org/v1beta1
@@ -188,11 +199,14 @@ spec:
188199
name: subscription-manager
189200
- secretRef:
190201
name: redhat-registry
202+
- secretRef:
203+
name: edpm-playbook-environment
191204
----
192205

193206
+
194207
For a complete list of the Red Hat Customer Portal registration commands, see https://access.redhat.com/solutions/253273. For information about how to log into `registry.redhat.io`, see https://access.redhat.com/RegistryAuthentication#creating-registry-service-accounts-6.
195208
endif::[]
209+
196210
. If your nodes are bare metal, you must configure the bare metal template, see xref:con_provisioning-bare-metal-data-plane-nodes_{context}[Provisioning bare metal data plane nodes].
197211

198212
. Optional: The sample `OpenStackDataPlaneNodeSet` CR you copied includes default node configurations under the `nodes` section. You can add additional nodes, and edit the configured values as required. For example, to add node-specific Ansible variables that customize the node, add the following configuration to your `openstack-edpm.yaml` file:

0 commit comments

Comments
 (0)