Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Include NFS configuration and control plane schedulability. #2772

Merged
merged 1 commit into from
Dec 9, 2019
Merged

Include NFS configuration and control plane schedulability. #2772

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
45 changes: 43 additions & 2 deletions docs/user/zvm/install_upi.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -253,14 +253,55 @@ INFO Waiting up to 30m0s for the bootstrap-complete event...
The Cluster Image Registry [Operator][cluster-image-registry-operator] does not pick an storage backend for `None` platform. Therefore, the cluster operator will be stuck in progressing because it is waiting for the administrator to [configure][cluster-image-registry-operator-configuration] a storage backend for the image-registry.
[NFS][openshift-nfs] should be picked as a [storage-backend][nfs-storage-backend].

TODO - document NFS backend setup.

Alternatively, for non-production clusters, emptyDir can be used for testing.
#### Configuring NFS

NFS is currently the only supported persistent storage option for OpenShift on Z. To make an existing NFS share accessible for OpenShift to use as persistent storage, users must first attach it as a Persistent Volume. At least 100GB of NFS storage space must be available for the image registry claim.

```
apiVersion: v1
kind: PersistentVolume
spec:
accessModes:
- ReadWriteMany
- ReadWriteOnce
capacity:
storage: 100Gi
nfs:
path: <NFS export path>
server: <ip of NFS server>
persistentVolumeReclaimPolicy: Recycle
volumeMode: Filesystem
status: {}
```

abhinavdahiya marked this conversation as resolved.
Show resolved Hide resolved
Once the persistent volume is created, the image registry must be patched to use it.

```
oc patch configs.imageregistry.operator.openshift.io/cluster --type merge --patch '{"spec":{"storage":{"pvc":{"claim":""}}}}'
abhinavdahiya marked this conversation as resolved.
Show resolved Hide resolved
```

#### Configuring Local Storage (testing/development only)

Alternatively, for non-production clusters, `emptyDir` can be used for testing instead of NFS.

```sh
oc patch configs.imageregistry.operator.openshift.io cluster --type merge --patch '{"spec":{"storage":{"emptyDir":{}}}}'
```

### Disabling Control Plane Schedulability

By default, when the OpenShift installer creates a cluster without any managed
workers (as is the default in a UPI installation), it configures the scheduler
to allow user-created application pods to be scheduled to the master nodes. In a
production cluster, the master nodes should not be schedulable so that user-created
applications can not consume resources dedicated to the control plane. Users should
configure the cluster to disable master schedulability.

```
oc patch schedulers.config.openshift.io/cluster --type merge --patch '{"spec":{"mastersSchedulable": false}}'
```

## Monitor for cluster completion

The administrators can use the `wait-for install-complete` target of the OpenShift Installer to monitor cluster completion. The command succeeds when it notices that Cluster Version Operator has completed rolling out the OpenShift cluster from Kubernetes APIServer.
Expand Down