Deployment of 4.17.0-0.okd-scos-2024-06-24-221946 #1955
Replies: 4 comments 2 replies
-
|
In addition: The solution was to delete the "ImportFailed" Tags from #1251
|
Beta Was this translation helpful? Give feedback.
-
|
There is a lot of events for Machine-Config Operator There is the description of the ValidatingAdmissionPolicy: |
Beta Was this translation helpful? Give feedback.
-
|
Just curious,
On my side, I've never been able to install OKD-SCOS, even having tried many (almost all) combinations of OS_IMAGES/RELEASE_IMAGES for assisted/agent installer for example |
Beta Was this translation helpful? Give feedback.
-
|
There is an agent install script in this repo: https://github.com/okd-project/miniagent that works. It is SNO. All of the installation methods will first boot with FCOS at the moment. I have installed (without incident) stable okd-SCOS from the 4.14 branch, SCOS-next from the 4.15 branch and nightlies from the 4.17 branch. Basically, if the release says "accepted" at https://amd64.origin.releases.ci.openshift.org/ then they do install. I have had good success with using a Travel Router (GL-AXT1800) for DNS, iPXE boot, ignition delivery plus 1-3 Intel NUCs as well as a small NUC (2 core, 32 GB ram) for sno installs. On one of the bigger NUCs (each has 6 or 12 cores and 64 GB ram, 1-2 TB of storage) I can run a three master cluster, or with three of them a 3+3 cluster plus ceph/rook storage. I use bash scripts based on Charro Gruver's Upstream without a paddle, https://upstreamwithoutapaddle.com/ Scripts are at https://github.com/cgruver/kamarotos.git using the archive-2 branch. For the most part these use iPXE UPI with a bootstrap node, the main branch of kamarotos also has a bare metal agent install of OCP. I have also installed 3 + n clusters on vSphere. There, I use a pfsense firewall and dhcp, a service host running load balancing, dns, and Apache for delivering ignition files, and the hosts for the cluster. Here I have only run FCOS as my home setup is more convenient to quickly install and tear down clusters (thanks Charro!). It really helps to look at the log messages from the bootstrap node as it is establishing the API and then finishing the bootstrap, then monitoring the install after that. Bootstrap: openshift-install --dir=${OKD_LAB_PATH}/${CLUSTER_NAME}.${DOMAIN}/okd-install-dir wait-for bootstrap-complete --log-level debug |
Beta Was this translation helpful? Give feedback.
-
|
Hi @titou10titou10 , |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for the pointers everyone |
Beta Was this translation helpful? Give feedback.
-
I've deployed single node installation of version 4.17.0-0.okd-scos-2024-06-24-221946, which is the newest version of v4.17.0-0.okd-scos.
The installation was smoothy without the errors. The result is:
Community Operator was in error State with error:
Beta Was this translation helpful? Give feedback.
All reactions