Skip to content

Bug 1834966: update vSphere UPI docs to remove machinesets #3619

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

Merged
openshift-merge-robot merged 1 commit into from
May 19, 2020
Merged

Bug 1834966: update vSphere UPI docs to remove machinesets #3619

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.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
38 changes: 37 additions & 1 deletion docs/user/vsphere/install_upi.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -180,9 +180,45 @@ test-vsphere

NOTE: The filename for `install-config` in the `INSTALL_DIR` must be `install-config.yaml`

### Invoking the installer to get manifests
Given that you have setup the `INSTALL_DIR` with the appropriate `install-config.yaml`, you can create manifests by using the `create manifests` target. For example,

```console
Copy link
Contributor

@abhinavdahiya abhinavdahiya May 19, 2020

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe truncated find if the items to sure that this is an example as there list might change.. keep the openshift/ machine objects

Copy link
Contributor Author

@patrickdillon patrickdillon May 19, 2020

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@abhinavdahiya Updated but not sure if this is what you had in mind. If not, let me know and I am happy to revise.

$ openshift-install --dir vsphere-test create manifests
INFO Consuming Install Config from target directory
```
This produces two directories which contain many manifests that will be used for installation.
```
$ tree vsphere-test -d
vsphere-test
├── manifests
└── openshift

2 directories
```

#### Remove Machines and MachineSets

Some of the manifests produced are for creating machinesets and machine objects:

```
$ find vsphere-test -name '*machineset*' -o -name '*master-machine*'
vsphere-test/openshift/99_openshift-cluster-api_master-machines-1.yaml
vsphere-test/openshift/99_openshift-cluster-api_master-machines-2.yaml
vsphere-test/openshift/99_openshift-cluster-api_master-machines-0.yaml
vsphere-test/openshift/99_openshift-cluster-api_worker-machineset-0.yaml
```

We should remove these, because we don't want to involve [the machine-API operator][machine-api-operator] during install.

From within the `INSTALL_DIR`:
```console
$ rm -f openshift/99_openshift-cluster-api_master-machines-*.yaml openshift/99_openshift-cluster-api_worker-machineset-*.yaml
```

### Invoking the installer to get Ignition configs

Given that you have setup the `INSTALL_DIR` with the appropriate `install-config`, you can create the Ignition configs by using the `create ignition-configs` target. For example,
Given that you have setup the `INSTALL_DIR` with the appropriate manifests, you can create the Ignition configs by using the `create ignition-configs` target. For example,

```console
$ openshift-install --dir test-vsphere create ignition-configs
Expand Down