GP3 volumes have the ability to configure throughput from 125 MiB/s to
2000 MiB/s. This allows the ability to set this at install time in the
install-config.
https://issues.redhat.com/browse/CORS-4212
GP3 volumes have the ability to configure throughput from 125 MiB/s to
2000 MiB/s. This allows the ability to set this at install time in the
install-config.
https://issues.redhat.com/browse/CORS-4212
This field was introduced [1] before the Installer had support for
custom AMIs in machine pools [2]. Now that it does, the same
functionality is achieved via the defaultMachinePlatform field
`platform.aws.defaultMachinePlatform.amiID`
[1] fdf94e39ee
[2] bc47222576
Fix a disconnect about the slug to use for the reference link from
17030b3bdb (aws: allow users to set the KMS key id for encrypting EBS
volumes, 2020-03-13, #3293).
users can set AMI for the platform or defaultMachinePool or individual machine pool, and the AMI used is based on increasing order of priority of the list mentioned before.
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
API version v1beta4 of install-config deprecated a few options names. While
not dramatic -- the installer knows how to update to the new format --
we should stop using deprecated options in the configuration examples
we provide.
This bumps the installconfig version from `v1beta3` to `v1beta4`. Users
will *not* have to update their existing configurations, becaue the
installer will automatically upconvert.
The network operator recently removed support for the older string, so
this exampled needed to be updated. The default string was updated back
in dafc79f, but these docs weren't updated.
docs/user/aws: update customization for controlPlane/compute
The machine field in install-config.yaml has been replaced with the controlPlane
and compute fields. The docs/user/aws/customization.md file needs to be updated
to reflect the change in the structure of install-config.yaml.
We're planning on dropping instance profiles in favor of the new
credentials operator [1], because we want AWS access to have
operator/pod/namespace granularity and not instance granularity. Many
pods could be running on a given instance, and not all of them should
have a given permission. While we're blocked from dropping these at
the moment due to kubelet cloud-config+secrets [2], we can drop the
user-facing knobs for this feature now. Then pivoting the internal
approach once we get the kubelet sorted will be a non-breaking change.
[1]: https://github.com/openshift/cloud-credential-operator
[2]: https://github.com/openshift/installer/pull/697#issuecomment-451582731
This is some initial documentation that covers the types of
customization that the installer supports. It only covers AWS right now,
so libvirt and OpenStack will need to be added eventually.
