|
8 yıl önce | |
---|---|---|
.. | ||
defaults | 8 yıl önce | |
handlers | 8 yıl önce | |
meta | 8 yıl önce | |
tasks | 8 yıl önce | |
templates | 8 yıl önce | |
README.md | 8 yıl önce |
Node service installation
From this role:
Name | Default value | |
---|---|---|
openshift_node_debug_level | openshift_debug_level | Verbosity of the debug logs for node |
oreg_url | UNDEF (Optional) | Default docker registry to use |
From openshift_common:
Name | Default Value | |
---|---|---|
openshift_debug_level | 2 | Global openshift debug log verbosity |
openshift_public_ip | UNDEF (Required) | Public IP address to use for this host |
openshift_hostname | UNDEF (Required) | hostname to use for this instance |
openshift_common
Currently we support re-labeling nodes but we don't re-schedule running pods nor remove existing labels. That means you will have to trigger the re-schedulling manually. To re-schedule your pods, just follow the steps below:
oadm manage-node --schedulable=false ${NODE}
oadm manage-node --drain ${NODE}
oadm manage-node --schedulable=true ${NODE}
`
If you are using version less than 1.5/3.5 you must replace
--drain
with--evacuate
.
TODO
Apache License, Version 2.0
TODO