Install the NFS Server in the NFS Server Node
-
Configure the NFS server for Glance and Cinder
From the bastion, connect to the NFS server host and configure the networking:
ssh -i /home/lab-user/.ssh/{guid}key.pem cloud-user@nfsserver
Escalate to root:
sudo -i
mkdir -p /nfs/cinder
mkdir -p /nfs/glance
mkdir -p /nfs/aap
chmod 777 /nfs/cinder
chmod 777 /nfs/glance
chmod 777 /nfs/aap
cat << EOF > /etc/exports
/nfs/cinder *(rw,sync,no_root_squash)
/nfs/glance *(rw,sync,no_root_squash)
/nfs/aap *(rw,sync,no_root_squash)
EOF
nmcli con delete 'Wired connection 1'
nmcli con add con-name "static-eth1" ifname eth1 type ethernet ip4 172.18.0.13/24
nmcli con up "static-eth1"
systemctl start nfs-server
systemctl enable nfs-server
exit
logout
Login to the preprovisioned Compute and configure networking
From the bastion login to the compute01 host:
ssh -i /home/lab-user/.ssh/{guid}key.pem cloud-user@compute01
sudo hostnamectl set-hostname edpm-compute-1.sandbox-{guid}-ocp4-cluster.svc.cluster.local
sudo nmcli con add con-name "static-eth1" ifname eth1 type ethernet ip4 172.22.0.100/24 ipv4.dns "172.22.0.89"
sudo nmcli con up "static-eth1"
sudo nmcli con add type ethernet ifname eth0 con-name eth0-dhcp ipv4.method auto ipv6.method ignore
sudo nmcli con up eth0-dhcp
sudo nmcli con mod eth0-dhcp connection.stable-id "user-set"
And log off VM
logout
Install kustomize
In the bastion, execute:
wget https://github.com/kubernetes-sigs/kustomize/releases/download/kustomize%2Fv5.6.0/kustomize_v5.6.0_linux_amd64.tar.gz
tar -xvzf kustomize_v5.6.0_linux_amd64.tar.gz
sudo cp kustomize /usr/local/bin/.
Allow the pattern Argo CD instance to manage cluster-scoped resources
Validated Patterns deploys the RHOSO applications through the cluster (hub) Argo
CD instance in the openshift-gitops namespace. That instance must remain
cluster-scoped so child applications can create cluster-level resources
(CRDs, ClusterRoles, OperatorGroups, and so on). The Validated Patterns
imperative namespace also needs cluster scope for helper Jobs.
Without this setting, applications can fail with errors like
can not be managed when in namespaced mode, and the OpenStack operator never
installs.
The AppProject name rhoso-gitops-standalone is only a Validated Patterns
clusterGroup / project label. This lab does not create a second Argo CD
instance or a rhoso-gitops-standalone namespace.
|
Patch the GitOps Operator Subscription so openshift-gitops and imperative
are treated as cluster-scoped:
oc patch subscription openshift-gitops-operator -n openshift-operators --type=merge -p '{
"spec": {
"config": {
"env": [
{
"name": "ARGOCD_CLUSTER_CONFIG_NAMESPACES",
"value": "openshift-gitops,imperative"
}
]
}
}
}'
Wait until the operator deployment picks up the new environment variable:
oc set env deployment/openshift-gitops-operator-controller-manager \
-n openshift-operators --list | grep ARGOCD_CLUSTER_CONFIG_NAMESPACES
The output must include openshift-gitops and imperative. If the variable is
missing or incomplete, restart the operator deployment and check again:
oc rollout restart deployment/openshift-gitops-operator-controller-manager \
-n openshift-operators
oc rollout status deployment/openshift-gitops-operator-controller-manager \
-n openshift-operators