Allow deploy OCP with two master node#3119
Allow deploy OCP with two master node#3119danpawlik wants to merge 1 commit intoopenstack-k8s-operators:mainfrom
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 |
|
taken from https://github.com/openshift-metal3/dev-scripts/blob/master/agent/docs/config-presets-and-options.md - that SNO is possible. |
4e54d07 to
e88bbcd
Compare
|
@danpawlik interresting! Did you test it? [1] https://github.com/openshift-metal3/dev-scripts/blob/master/Makefile#L10C1-L10C6 |
03cd4e0 to
f73a158
Compare
That commit allows to deploy OCP with two master node. It would be useful for environments with limited resources. Signed-off-by: Daniel Pawlik <dpawlik@redhat.com>
f73a158 to
8893b4a
Compare
|
Merge Failed. This change or one of its cross-repo dependencies was unable to be automatically merged with the current state of its repository. Please rebase the change and upload a new patchset. |
|
@hjensas so far, it does not work and don't know why (the SNO). It is like the metal3 does not support SNO (looking in theirs script, it is like the "feature" is not present there). I moved the changes to other PR #3129. I was hoping that the metal3 is more less using - https://docs.redhat.com/en/documentation/openshift_container_platform/4.18/html/installing_on_a_single_node/install-sno-installing-sno#install-sno-installing-sno-manually manual, but seems not. |
I'll take a look this weekend, probably start off with the agent based installer role from hotstack - but change it to use an ISO instead of network boot. It would be similar to what that last link suggest. |
That commit allows to deploy OCP with two masters node. It would be useful for environments with limited resources.