Skip to content

Commit 6f1add7

Browse files
stephenfinmandre
authored andcommitted
Bug 2096376: [openstack] Remove limitation on single node deployments
There should no longer be any issues running router pods on control plane nodes (i.e. kubernetes/kubernetes#65618 which was resolved in kubernetes/enhancements#1144). Remove this limitation from the docs. Signed-off-by: Stephen Finucane <[email protected]>
1 parent b8fbd1a commit 6f1add7

File tree

1 file changed

+0
-18
lines changed

1 file changed

+0
-18
lines changed

docs/user/openstack/install_upi.md

-18
Original file line numberDiff line numberDiff line change
@@ -33,7 +33,6 @@ of this method of installation.
3333
- [Modify NetworkType (Required for Kuryr SDN)](#modify-networktype-required-for-kuryr-sdn)
3434
- [Edit Manifests](#edit-manifests)
3535
- [Remove Machines and MachineSets](#remove-machines-and-machinesets)
36-
- [Make control-plane nodes unschedulable](#make-control-plane-nodes-unschedulable)
3736
- [Ignition Config](#ignition-config)
3837
- [Infra ID](#infra-id)
3938
- [Bootstrap Ignition](#bootstrap-ignition)
@@ -463,23 +462,6 @@ Leave the compute MachineSets in if you want to create compute machines via the
463462

464463
[mao]: https://github.com/openshift/machine-api-operator
465464

466-
### Make control-plane nodes unschedulable
467-
468-
Currently [emptying the compute pools][empty-compute-pools] makes control-plane nodes schedulable. But due to a [Kubernetes limitation][kubebug], router pods running on control-plane nodes will not be reachable by the ingress load balancer. Update the scheduler configuration to keep router pods and other workloads off the control-plane nodes:
469-
<!--- e2e-openstack-upi: INCLUDE START --->
470-
```sh
471-
$ python -c '
472-
import yaml
473-
path = "manifests/cluster-scheduler-02-config.yml"
474-
data = yaml.safe_load(open(path))
475-
data["spec"]["mastersSchedulable"] = False
476-
open(path, "w").write(yaml.dump(data, default_flow_style=False))'
477-
```
478-
<!--- e2e-openstack-upi: INCLUDE END --->
479-
480-
[empty-compute-pools]: #empty-compute-pools
481-
[kubebug]: https://github.com/kubernetes/kubernetes/issues/65618
482-
483465
## Ignition Config
484466

485467
Next, we will turn these manifests into [Ignition][ignition] files. These will be used to configure the Nova servers on boot (Ignition performs a similar function as cloud-init).

0 commit comments

Comments
 (0)