This patch updates the "cloud-install" links in the documentation to
point to the current location.
Signed-off-by: Juan Hernandez <juan.hernandez@redhat.com>
This updates vSphere docs to provide more information about permissions.
We can see in a lot of cases (https://bugzilla.redhat.com/show_bug.cgi?id=1869035)
that when admins are not granting Global Permissions they are neglecting
to assign minimum priveleges to the vSphere itself.
The installer now generates spec v3.1 ignition config,
instead of v2.2 (and v2.4 for openstack) as before.
The v3.1 ignition config specification can be found at [1].
A detailed overview of the differences between specs v2 and v3 can be found at [2].
Notable differences are:
- the `Filesystem` identifier on ignition file configs no longer exists
- `Overwrite` now defaults to `false` (was `true` in spec v2), which is why
it is now set explicitly to keep the same behaviour.
- duplicate file configs are now prohibited, i.e. all contents and
all appendices must be defined in a single config.
- duplicate systemd unit configs are now prohibited, i.e. the content
and all dropins must be defined in a single config.
This commit:
- Bumps ignition to v2.3.0 with support for config spec v3.1.
- Bumps terraform-provider-ignition to v2.1.0.
Also adds downloading of the provider binary to `images/installer/Dockerfile.upi.ci`
which is necessary because the ignition v2/spec3 version from the
`community-terraform-providers/terraform-ignition-provider` fork is not
present in the provider registry that is maintained by Hashicorp and can
therefore not be pulled in automatically by terraform.
is not present in the
- Bumps machine-config-operator to b3b074ee9156
(latest commit at the time of this writing).
- Adds "github.com/clarketm/json" dependency for marshaling Ignition configs.
This is a dropin replacement for "encoding/json" that supports zero values of
structs with omittempty annotations when marshaling.
In effect, this will exclude empty pointer struct fields from the
marshaled data instead of inserting nil values into them, which do not
pass openAPI validation on fields that are supposed to contain e.g. strings.
The same library is used by machine-config-operator and ignition itself.
- Updates the vendor dir to make commit idempotent.
[1] https://github.com/coreos/ignition/blob/master/doc/configuration-v3_1.md
[2] https://github.com/coreos/ignition/blob/master/doc/migrating-configs.md#from-version-230-to-300
Co-authored-by: Vadim Rutkovsky <vrutkovs@redhat.com>
To enable infrastructure provisioning in vSphere, the installer now
creates machine object and machineset manifests. This commit updates
UPI docs to remove those manifests, as the skew between the installer
produced manifests and user-provisioned control-plane causes errors.
Sets the vCPU and memory to the minimum requirements for both the control plane and worker nodes. Includes the default values in the machinesets as well as terraform code for creating the control plane.
This commit also includes documentation for customizing the machine pools. Note that the memory json specification in the install-config uses MB while the variable name is MiB. The intention of this split is to keep the user-facing docs and install-config consistent with Red Hat docs which use MB/GB, but the variable names to be consistent with the machine-api and kubernetes in general which uses MiB/GiB.
Broken since the vSphere docs landed in 0ec07d0769 (docs: vSphere
installation docs, 2019-04-07, #1545). Also a bunch of other broken
links and some minor wordsmithing.
This is a bit more accessible than pointing folks at Godocs, since it
allows us to focus on the YAML property names (while Godocs
understandably focus on Go property names) and YAML renderings. Also
break up our old "one big example" install-config.yaml into a minimal
per-platform example and a series of small extentions excercising
groups of properties.
The vSphere docs are based heavily on [1].
Also drop proxy.md. It was added in e7edbf71fd (Add proxy
configuration to bootstrap node, 2019-06-24, #1832), but:
* Proxy testing and Squid configuration information belongs in
openshift/release, not in the installer repository.
* docs/user/customization.md now contains a more complete proxy-config
fragment.
OpenStack computeFlavor precedence is based on [2].
[1]: https://github.com/openshift/openshift-docs/blob/enterprise-4.2/modules/installation-vsphere-config-yaml.adoc
Last touched by commit openshift/openshift-docs@25afc7626d , 2019-08-19
[2]: https://github.com/openshift/installer/pull/2162#discussion_r322410878
Most of our docs were bumped in befde3c232 (pkg/types/installconfig:
Bump v1beta4 to v1, 2019-04-10, #1589), but these v1beta4 references
snuck in with 0ec07d0769 (docs: vSphere installation docs, 2019-04-07, #1545)
and 0055065143 (baremetal: add baremetal IPI platform, 2019-07-16, #1873).
This was added out of an abundance of caution about how etcd metrics
were being scraped, because the Prometheus scrapers can run on compute
nodes. We've now confirmed that etcd-metrics are being scraped from
port 9979, which is part of the existing "OpenShift reserved" and so
does not need a specific call-out.
Add instructions in the documentation for setting the hostname
and static IP address of a machine.
Add language to indicate that the preferrence is to use DHCP for
establishing the hostname and IP addresses.
