Add uni04delta and uni04delta-adoption network-values templates #3532
Conversation
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: 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 |
|
Build failed (check pipeline). Post https://softwarefactory-project.io/zuul/t/rdoproject.org/buildset/6611052b84d94ad3b106ddebbe3cffde ❌ openstack-k8s-operators-content-provider FAILURE in 6m 49s |
…ork-values templates Add kustomize network-values templates for uni04delta scenario to support both greenfield integration deployments and adoption workflows. These templates generate NetworkAttachmentDefinition configurations and node network data from cifmw_networking_definition for RHOSO deployments. The uni04delta template is for integration jobs, while uni04delta-adoption is for adoption pipeline jobs that migrate from OSP 17.1 to RHOSO 18.0. Based on uni04delta-ipv6 templates, adapted for IPv4 networking. Related: OSPNW-880 Assisted-by: Cursor(claude-4.5-sonnet) Signed-off-by: Roberto Alfieri <ralfieri@redhat.com>
|
Build failed (check pipeline). Post https://softwarefactory-project.io/zuul/t/rdoproject.org/buildset/ab5356fbc15d42c1b6a7c622cb1dc7f6 ✔️ openstack-k8s-operators-content-provider SUCCESS in 2h 05m 11s |
|
recheck |
|
Build failed (check pipeline). Post https://softwarefactory-project.io/zuul/t/rdoproject.org/buildset/5e9a0bd162f642f5b2a24432f4460da2 ✔️ openstack-k8s-operators-content-provider SUCCESS in 2h 23m 20s |
|
recheck |
roles/ci_gen_kustomize_values/templates/uni04delta-adoption/network-values/values.yaml.j2
Show resolved
Hide resolved
2 participants
Add kustomize network-values templates for uni04delta scenario to support both greenfield integration deployments and adoption workflows.
These templates generate NetworkAttachmentDefinition configurations and node network data from cifmw_networking_definition for RHOSO deployments.
The uni04delta template is for integration jobs, while uni04delta-adoption is for adoption pipeline jobs that migrate from OSP 17.1 to RHOSO 18.0.
Based on uni04delta-ipv6 templates, adapted for IPv4 networking.
Related: OSPNW-880
Assisted-by: Cursor(claude-4.5-sonnet)