NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
Go modules
Go modules, #1287 by repository stars
Latest stable
v1.4.17
Last release 20 days ago
02 Nov 2026
Ships fairly regularly
a new release about every 4 weeks
Most releases are documented
notes for 21 of 35 stable releases
Nothing withdrawn
no release was ever pulled
8 years old
1034 releases · first in 2018
Drag across the ruler to compare, or tap a release to open it.
Nothing published for this version
Nothing published for this version
Nothing published for this version
Azure disk selection fix for hive
Azure disk selection fix for hive
Your coding agent can read these notes before it upgrades. Set up the MCP server →
Pre-release tag for k8s pkg bump
Pre-release tag for k8s pkg bump
Installer 5.0 Dev Branch Opens
Installer 5.0 Dev Branch Opens
4.22 Engineering Candidate 5
4.22 Engineering Candidate 5
4.21 Release Candidate 2
4.21 Release Candidate 2
Includes CRD definitions for hive usage.4.21 Pre-release
Includes CRD definitions for hive usage.4.21 Pre-release
Includes CRD definitions for hive usage.4.21 Pre-release
Includes CRD definitions for hive usage.4.21 Pre-release
Includes CRD definitions for hive usage.4.21 Pre-release
Includes CRD definitions for hive usage.4.21 Pre-release
Includes CRD definitions for hive usage.4.21 Pre-release
Includes CRD definitions for hive usage.4.21 Pre-release
Includes CRD definitions for hive usage.4.21 Pre-release
Includes CRD definitions for hive usage.4.21 Pre-release
Includes CRD definitions for hive usage.4.21 Pre-release
Includes CRD definitions for hive usage.4.21 Pre-release
Includes CRD definitions for hive usage.4.21 Pre-release
Includes CRD definitions for hive usage.4.21 Pre-release
Includes CRD definitions for hive usage.4.21 Pre-release
Includes CRD definitions for hive usage.4.21 Pre-release
Includes CRD definitions for hive usage.4.21 Pre-release
Includes CRD definitions for hive usage.4.21 Pre-release
Includes CRD definitions for hive usage.4.21 Pre-release
Includes CRD definitions for hive usage.4.21 Pre-release
Includes CRD definitions for hive usage.4.21 Pre-release
Includes CRD definitions for hive usage.
Tag for konflux for acb3420
Tag for konflux for acb3420
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Creating a new, arbitrary version to bring the latest release to a more recent commit. We were seeing issues when other projects imported the module d
Creating a new, arbitrary version to bring the latest release to a more recent commit. We were seeing issues when other projects imported the module due to the gap between the most recent release and master (5 years, 10,000+ commits).
See https://issues.redhat.com/browse/OCPBUGS-42448 for more details.
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
This release adds the build-tooling fix from [#1521][0] to 0.16.0, so the compiled binaries actually pin the intended quay.io release image.
This release adds the build-tooling fix from #1521 to 0.16.0, so the compiled binaries actually pin the intended quay.io release image.
The installer change log is here (still the v0.16.0 change log, since no installer code changed, just the build tooling). SHA 256 for the released binaries:
The release-image change-log since v0.15.0 is here.
The installer change log is [here][1]. SHA 256 for the released binaries:
master branch. Please use 0.16.1 instead (same installer code, but actually pins the right release image)The installer change log is here. SHA 256 for the released binaries:
The release-image change-log since v0.15.0 is here.
quay.io/coreos/kube-etcd-signer-server.networkconfigs.networkoperator.openshift.io to
networks.operator.openshift.io.install-config.yaml, the installer will now only
create per-zone resources for those zones. This allows for clusters
in high-zone regions like us-east-1 without requiring limit bumps.Name and
openshiftClusterID.s3:GetBucketObjectLockConfiguration.The installer change log is [here][1]. SHA 256 for the released binaries:
kube-system
Secrets and ConfigMaps.kube-client-agent reference, replacing
quay.io/coreos/kube-client-agent.pod reference.user-provided-infrastructure subcommand.v1beta4 for changes
to more closely align with Network.config.openshift.io:
serviceCIDR is now serviceNetwork.clusterNetworks is now clusterNetwork.type is now networkType.hostSubnetLength is now hostPrefix.
v1beta3 is deprecated and will be removed in a future release.aws-cloud-credentials (created by [the credential
operator][credential-operator]) to fulfill our Machine(Set)s./readyz instead
of /healthz for health checks, which allows for more graceful
control-plane rotation.destroy cluster has some fixes for:
InvalidGroup.NotFound is now caught and considered a succesful
deletion in more situations than with previous releases.api and *.apps DNS entries for internal
IPs when a floating IP is not configured.none platform no longer creates Machine(Set)s, because there
is, by definition, no machine-API support for that platform.cluster-config-v1 ConfigMap no longer contains the
pull secret, now that all pull-secret consumers have been migrated
to the coreos-pull-secret Secret.Mitigate XSS vulnerabilities in Singlestat panel #14116
The installer change log is [here][1]. SHA 256 for the released binaries:
The following is the release-image change-log since v0.13.1, as generated by:
$ oc adm release info --changelog ~/.local/lib/go/src --changes-from quay.io/openshift-release-dev/ocp-release:4.0.0-0.6 quay.io/openshift-release-dev/ocp-release:4.0.0-0.7
Created: 2019-03-05 18:33:12 +0000 UTC
Image Digest: sha256:641c0e4f550af59ec20349187a31751ae5108270f13332d1771935520ebf34c1
Promoted from registry.svc.ci.openshift.org/ocp/release:4.0.0-0.nightly-2019-03-04-234414
sha256:8faf4b3739c952de448c69325c8c101193c0665bb149d3d2830afd2aca973413sha256:86bb159de280a6d9f81a69081090148cfad233db1b6f596a996097b56c0d6940sha256:71f521d9cb0b1f03fe78938f90df7a0a9bdf5a45a31c65b168533e507644da34sha256:7b9990d7f21ddd4d981701d7f1e326e3ae2041d9aafad53115a828a9f0fa8d0esha256:6edd77ad4ef48f3b29045acc0c9a57b01dcfb2c42b497ab857fa4eb27d8a841csha256:9af8c72361b3a8bad34c44be6903e02c0f8a56b6ef4d459fce9c75ee38251093sha256:fc79d84dee4f2a998a105e94a1457eb5aabf85b1b9d1a6468aca6f8835c04408sha256:4a561991866a16773e965586f40a5684174229430e56ad25f15b851fe8e725edsha256:9f720109ad203a0a0e44e0da14e2e82aefaa40e6d41accdefdc5ec2b3aed9153sha256:3fe76f173faaf16af80d4f865c377a4dc4db24d32c1bba4c6d3115e66a788861sha256:7bcb847c457cf8bf5813e10e46058f34426560d0798ca1d80f8ee34e5fa5727bsha256:a457ab8bc3be66c97ce6babd77e6f1c1eaff91477bd5442460f927db06a15e55sha256:6b65c7ff285c611ae17a91deff91c0585773507e7fcffec7353ea849a66bd018sha256:4274c276fec8729ad17ff77d74188ade01e3695b3b2afa3b995081394b107857sha256:61180c69f1cba674625bd6c85995f524bdbdde27b2d08ea7efcecd7d3427409bsha256:fc9fa4ce84819c084737115feef722f49d05d43ca6f438edfbc21535e2479b2dsha256:077b65e55d01d3abd114933c4e132a642a0315f83b93b05b185fa338ce09595asha256:035af1a1f35a1f0d8159576460437d9d3529b4f64e0b142a8da59a5e4e056a68sha256:810ded5c25b9ec252dba6a2497d1eff9ad13a19cc3ac290ef8943b7d658803f2sha256:da1d1556af41b9d71e24cdc7406e0671f3eca877a16e465e6e5bdd5ecfad6bd1sha256:5625206aa10f98cb2306bb37621cc3a6637ef69a43713fb4f9a34ebff1d4b3ffsha256:414275a7a91f92951cae01928234aed2e0d4670fb911f0d1f189a2ee0a821c9esha256:26c197ba809ac3cd18a79c1dde21812e97e6957e0dfc93ac6f4c50947f3dfe99sha256:8a107dd61b46e2fd0b71e1e6c291f97ccd634fd4c759f46d9f4403c3a6f4496asha256:1d0dd92b072c381c0471b1b8ed6f3bc5eded95d747c87b4bbe659c1396ad63edsha256:03b053176eacf0e847d75c5ce8137455faa4c7a52623381f723de1fa87a36761sha256:032cf8f0fd7ac91f58ee670244892812cd024d8d7eee923266b9acf97ee21ac4release info --changelog #22163-C for release extraction #22184/auth/callback path #161Note truncated.
sigs.k8s.io/cluster-api-... to machine.openshift.io, continuing
the transition begun in 0.13.0.SecurityGroups schema has changed, as
has the schema for selecting subnets.Removing unused/deprecated security groups and ports. Updated AWS doc #1306
The installer change log is here. SHA 256 for the released binaries:
The following is the release-image change-log since v0.13.0, as generated by:
$ oc adm release info --changelog ~/.local/lib/go/src --changes-from quay.io/openshift-release-dev/ocp-release:4.0.0-0.5 quay.io/openshift-release-dev/ocp-release:4.0.0-0.6
Created: 2019-02-28 20:40:11 +0000 UTC
Image Digest: sha256:5ce3d05da3bfa3d0310684f5ac53d98d66a904d25f2e55c2442705b628560962
Promoted from registry.svc.ci.openshift.org/ocp/release:4.0.0-0.nightly-2019-02-27-213933
sha256:f87be09923a5cb081722634d2e0c3d0a5633ea2c23da651398d4e915ad9f73b0sha256:955413b82cf8054ce149bc05c18297a8abe9c59f9d0034989f08086ae6c71fa6sha256:756e813fce04841993c8060d08a5684c173cbfb61a090ae67cb1558d76a0336esha256:dbdd90da7d256e8d49e4e21cb0bdef618c79d83f539049f89f3e3af5dbc77e0fsha256:773d3355e6365237501d4eb70d58cd0633feb541d4b6f23d6a5f7b41fd6ad2f5sha256:ca15f98cc1f61440f87950773329e1fdf58e73e591638f18c43384ad4f8f84dasha256:a66af3b1f4ae98257ab600d54f8c94f3a4136f85863bbe0fa7c5dba65c5aea46sha256:ad71743cc50a6f07eba013b496beab9ec817603b07fd3f5c022fffbf400e4f4bsha256:e61d1fdb7ad9f5fed870e917a1bc8fac9ccede6e4426d31678876bcb5896b000sha256:8f3b40b4dd29186975c900e41b1a94ce511478eeea653b89a065257a62bf3ae9sha256:e7c9323b91dbb11e044d5a1277d1e29d106d92627a6c32bd0368616e0bcf631asha256:097a429eda2306fcd49e14e4f5db8ec3a09a90fa29ebdbc98cc519511ab6fb5bsha256:7d59edff68300e13f0b9e56d2f2bc1af7f0051a9fbc76cc208239137ac10f782sha256:32360c79d8d8d54cea03675c24f9d0a69877a2f2e16b949ca1d97440b8f45220sha256:f8c07cb72dc8aa931bbfabca9b4133f3b93bc96da59e95110ceb8c64f3efc755sha256:c6434441fa9cc96428385574578c41e9bc833b6db9557df1dd627411d9372bf4sha256:bb589cf71d4f41977ec329cf808cdb956d5eedfc604e36b98cfd0bacce513ffcsha256:2f1812a95e153a40ce607de9b3ace7cae5bee67467a44a64672dac54e47f2a66sha256:27062ab2c62869e5ffeca234e97863334633241089a5d822a19350f16945fbcbsha256:e4e9677d004f8f93d4f084739b4502c2957c6620d633e1fdb379c33243c684fasha256:548abcc50ccb8bb17e6be2baf050062a60fc5ea0ca5d6c59ebcb8286fc9eb043sha256:c899b557e4ee2ea7fdbe5c37b5f4f6e9f9748a39119130fa930d9497464bd957sha256:772c1b40b21ccaa9ffcb5556a1228578526a141b230e8ac0afe19f14404fdffcsha256:b6de05167ecab0472279cdc430105fac4b97fb2c43d854e1c1aa470d20a36572sha256:611c800c052de692c84d89da504d9f386d3dcab59cbbcaf6a26023756bc863a0sha256:6ab8749886ec26d45853c0e7ade3c1faaf6b36e09ba2b8a55f66c6cc25052832sha256:e3f87811d22751e7f06863e7a1407652af781e32e614c8535f63d744e923ea5csha256:093a2ac687849e91671ce906054685a4c193dfbed27ebb977302f2e09ad856dcsha256:f9c321de068d977d5b4adf8f697c5b15f870ccf24ad3e19989b129e744a352a7sha256:730f3b504cccf07e72282caf60dc12f4e7655d7aacf0374d710c3f27125f7008sha256:3235ad5e22b6f560d447266e0ecb2e5655fda7c0ab5c1021d8d3a4202f04d2casha256:013455905e4a6313f8c471ba5f99962ec097a9cecee3e22bdff3e87061efad57sha256:54512a6cf25cf3baf7fed0b01a1d4786d952d93f662578398cad0d06c9e4e951sha256:244fc5f1a4a0aa983067331c762a04a6939407b4396ae0e86a1dd1519e42bb5dsha256:390e5e1b3f3c401a0fea307d6f9295c7ff7d23b4b27fa0eb8f4017bd86d7252csha256:6e697dcaa19e03bded1edf5770fb19c0d2cd8739885e79723e898824ce3cd8f5sha256:85ea2924810ced0a66d414adb63445a90d61ab5318808859790b1d4b7decfea6sha256:7f89db559ffbd3bf609489e228f959a032d68dd78ae083be72c9048ef0c35064sha256:fd518d2c056d4ab8a89d80888e0a96445be41f747bfc5f93aa51c7177cf92b92oc debug node/X instead of set #22086oc adm release info --changelog should clone if necessary #22148etcdctl referenced from the
release image, instead of hard-coding its own version.v1beta1 and
v1beta2 has been removed, so the installer will error out if
provided with an older install-config.yaml. v1beta1 was
deprecated in 0.12.0 and v1beta2 was deprecated in 0.13.0. In
both cases, the installer would ignore removed properties but not
error out.The change log is [here][1]. SHA 256 for the released binaries:
The change log is here. SHA 256 for the released binaries:
config.openshift.io custom resource definitions.The install-config version has been bumped from v1beta2 to
v1beta3. All users will need to update any saved
install-config.yaml to use the new schema.
machines has been split into controlPlane and compute.
Multiple compute pools are now supported (previously, only a
single worker pool was supported). Every compute pool will
use the same Ignition configuration. The installer will warn
about but allow configurations where there are zero compute
replicas.masterIPs property has been removed, since you
cannot configure master IPs via the libvirt machine API
provider.lbFloatingIP property, which
allows you to provide an IP address to be used by the load
balancer. This allows you to create local DNS entries ahead of
time before calling create cluster.Cluster domain names have been adjusted so that the cluster lives entirely within a per-cluster subdomain. This keeps split-horizon DNS from masking other clusters with the same base domain.
The cluster-version update URL has been changed from the dummy
http://localhost:8080/graph to the functioning
https://api.openshift.com/api/upgrades_info/v1/graph and the
channel has been changed from fast to stable-4.0, to opt
clusters in to 4.0 upgrades.
Machine-API resources have been moved from cluster.k8s.io to
machine.openshift.io to clarify our divergence from the upstream
types while they are unstable. The openshift-cluster-api
namespace has been replaced with openshift-machine-api as well.
The installer now uses etcd and OS images referenced by the update payload when configuring the machine-config operator.
The etcd, aggregator, and other certificate authorities are now self-signed, decoupling their chains of trust from the root certificate authority.
The installer no longer creates a service-serving certificate authority. The certificate authority is now created by the [service-CA operator][service-ca-operator].
On AWS, the worker IAM role permissions were reduced to a smaller set required for kubelet initialization.
On AWS, the worker security group has been expanded to allow ports 9000-9999 for for host network services. This matches the approach we have been using for masters since 0.4.0. The master security group has also been adjusted to fix a 9990 -> 9999 typo from 0.4.0.
On libvirt, the default compute nodes have been bumped from 2 to 4 GiB of memory and the control-plane nodes have been bumped from 4 to 6 GiB of memory and 2 to 4 vCPUs.
Several doc and internal cleanups and minor fixes.
The router certificate authority is appended to the admin
kubeconfig to fix the OAuth flow behind oc login.
The install-config.yaml validation is now more robust, with the
installer:
networking.clusterNetworks[].cidr and explicitly
checking for nil machineCIDR and serviceCIDR.Terraform variables are now generated from master machine configurations instead of from the install configuration. This allows them to reflect changes made by editing master machine configurations during staged installs.
metadata.json is generated before the Terraform invocation, fixing
a bug introduced in 0.12.0 which made it hard to clean up after
failed Terraform creation.
The machine-config server has moved its Ignition-config service from port 49500 to 22623 to avoid the dynamic-port range starting at [49152][rfc-6335-s6].
When the installer prompts for AWS credentials, it now respects
AWS_PROFILE and will update an existing credentials file instead
of erroring out.
On AWS, the default [instance types][aws-instance-types] now depend on the selected region, with regions that do not support m4 types falling back to m5.
On AWS, the installer now verifies that the user-supplied credentials have sufficient permissions for creating a cluster. Previously, permissions issues would surface as Terraform errors or broken cluster functionality after a nominally successful install.
On AWS, the destroy cluster implementation is now more robust,
fixing several bugs from 0.10.1:
nil before dereferencing,
avoiding panics when removing internet gateways which had not
yet been associated with a VPC, and in other similar cases.On AWS and OpenStack, there is a new infra ID that is a uniqified, possibly-abbreviated form of the cluster name. The infra ID is used to name and tag cluster resources, allowing for multiple clusters that share the same cluster name in a single account without naming conflicts (beyond DNS conflicts if both clusters also share the same base domain).
On OpenStack, the HAProxy configuration on the service VM now only balances ports 80 and 443 across compute nodes (it used to also balance them across control-plane nodes).
On OpenStack, the service VM now uses CoreDNS instead of dnsmasq.
And it now includes records for *.apps.{cluster-domain} and the
Kubernetes API.
On OpenStack, the service VM has been moved to its own subnet.
The change log is [here][1]. SHA 256 for the released binaries:
The change log is here. SHA 256 for the released binaries:
ClusterVersion][ClusterVersion] to report all
operators as available before returning from create cluster.networks.config.openshift.io and reserve
networkconfigs.networkoperator.openshift.io for lower-level
configuration (although we still generate it as well).apiServerURL and etcdDiscoveryDomain in
infrastructures.config.openshift.io.MODE=dev remain unstripped if you want to
attach a debugger.destroy cluster no longer depends directly on the cluster
name (although it still depends on the cluster name indirectly via
the kubernetes.io/cluster/{name} tag). This makes it easier to
reconstruct metadata.json for destroy cluster if you
accidentally removed the file before destroying your cluster.ERROR: logging before flag.Parse...
messages from our underlying Kubernetes libraries.install-config.yaml, we now error on CIDRs whose IP is
not at the beginning of the masked subnet. For example, we now
error for 192.168.126.10/24, since the beginning of that subnet is
192.168.126.0.install-config.yaml, we now fill in defaults for
replicas when it is unset or explicitly null.cloud value, and the secret name has been updated
from openstack-creds to openstack-credentials.local-dns service will now restart on failure
(e.g. when the initial image pull fails) and it no longer sets the
name of the container (so we can always re-run it without running
into duplicate name issues).install-config.yaml, the installer no longer restricts
networking.type to a known value. If the network operator sees an
unrecognized type, it assumes the user is configurating networking
and doesn't react.~core/.bash_history on the bootstrap node, as
part of becoming less opinionated about which users are present on
the underlying operating system.iamRoleName machine-pool property is gone, and the
podCIDR networking property (deprecated in 0.4.0) is gone. The
install-config version has been bumped from v1beta1 to v1beta2.
All users, regardless of platform, will need to update any saved
install-config.yaml to use the new version. IAM roles are being
replaced by [the credential operator][credential-operator], and
while we still create IAM roles for our master, worker, and
bootstrap machines, we're removing the user-facing property now to
avoid making this breaking change later.The change log is [here][1]. SHA 256 for the released binaries:
The change log is here. SHA 256 for the released binaries:
oc rsh and Kubernetes node
registration in the face of inappropriate default DHCP options. And
because [the AWS domain-name logic is
region-specific][aws-dhcp-options], there is no single DHCP options
configuration that provides internal unqualified-hostname resolution
for multiple regions.install-config.yaml. Previously, only the
install-config wizard would prompt.openshift-install has improved error handling for various invalid
command lines. It now errors when additional positional arguments
are passed to commands that do not take positional arguments
(previously those commands silently ignored the presence of
positional arguments). And it logs an error and exits 1 when an
invalid value is provided to --log-level (previously it exited 1 but
did not write to the standard error stream).
The slow-input issues for the install-config wizard have been fixed.
On AWS, destroy cluster fixed a bug in the 0.10.1 refactor which
could lead to leaked resources and a claim of successful deletion if
a call to get tagged resources failed (for example, because the
caller lacked the tag:GetResources permission).
On AWS, a new explicit dependency in the Terraform modules prevents errors like:
* module.vpc.aws_lb.api_external: 1 error occurred:
* aws_lb.api_external: Error creating Application Load Balancer: InvalidSubnet: VPC vpc-0765c67bbc82a1b7d has no internet gateway
status code: 400, request id: 5a...d5
On libvirt, the installer no longer holds the OS image in memory after it has been written to disk. Ideally it would stream the OS image to disk instead of ever holding it in memory, but this fix mitigates our current in-memory buffering.
The change log is [here][1]. SHA 256 for the released binaries:
The change log is here. SHA 256 for the released binaries:
create ignition-configs now also writes metadata.json to the
asset directory, which allows [Hive][] to more reliably destroy
clusters.destroy cluster now removes .openshift_install_state.json on
success, clearing the way for future create cluster runs in the
same asset directory.On AWS, the cluster-API provider now supports configuring machine
volumes, so rootVolume settings in install-config.yaml will be
respected.
On AWS, the generated Terraform variables no longer clobber master
instance type and root volume configuration set via
install-config.yaml. You can now use:
machines:
- name: master
platform:
aws:
type: m5.large
rootVolume:
iops: 3000
size: 220
type: io1
replicas: 3
- name: worker
...
and similar to successfully customize your master machines.
On AWS, destroy cluster has been adjusted to use more efficient
tag-based lookup and fix several bugs due to previously-missing
pagination. This should address some issues we had been seeing with
leaking AWS resources despite destroy cluster claiming success.
The change log is [here][1]. SHA 256 for the released binaries:
The change log is here. SHA 256 for the released binaries:
cluster-config-v1 resource.openshift-install has a new completion subcommand, to generation
shell-completion code (currently only for Bash).destroy cluster now also removed IAM users with the usual
tags. We don't create these users yet, but the removal sets the
stage for the coming [credential operator][credential-operator].Install configuration now includes a new apiVersion property which
must be set to v1beta1. Future changes to the install-config
schema will result in new versions, allowing new installers to
continue to support older install-config schema (and older
installers to error out when presented with newer install-config
schema). Changes to the schema since 0.9.0:
clusterID has been removed. This should be a new UUID for
every cluster, so there is no longer an easy way for users to
configure it.OPENSHIFT_INSTALL_OS_IMAGE_OVERRIDE
environment variable.machineCIDR from which node IP addresses are
assigned.install-config.yaml read during staged
installs will now have
installer-defaults applied for missing properties. This allows you
to set only the properties you are interested in overriding, and
allow the installer to manage the remaining properties.
create ignition-configs now also writes the admin kubeconfig to
the asset directory, to support bring-your-own-infrastructure use
cases.
The bootstrap node now serves journals for easier troubleshooting.
The validity for the initial kubelet TLS certificate has been increased from one hour to 24 hours, to give bring-your-own-infrastructure users longer to manually distribute the certificate before it expires.
The key for the root certificate authority is no longer pushed into the cluster (not even to the bootstrap node).
Machine(set)s generated by the installer now use providerSpec
instead of the deprecated providerConfig.
On AWS, the load balancers now use HTTPS health checks to reduce log noise like:
http: TLS handshake error from 10.0.20.86:28372: EOF
On AWS, IAM roles are now tagged with the usual resource tags
(openshiftClusterID, etc.). Some other resources have had their
tags updated to match those conventions (e.g. the internal Route 53
hosted zone was updated from KubernetesCluster to
kubernetes.io/cluster/{name}: owned).
The OpenStack platform has been removed from the install-config
wizard while it remains experimental. It is still available for
users who supply their own install-config.yaml.
On OpenStack, the service VP now respects any SSH key specified in the install configuration.
On OpenStack, a developer-only internal DNS server has been removed, so users need to configure additional records for the existing external DNS zone.
On OpenStack, Neutron trunk ports are now used for VM network interfaces if Neutron supports them to support future Kuryr integration.
On OpenStack, masters and workers have been consolidated in a single subnet to simplify the deployment.
On OpenStack, the Ignition security group now only allows internal connections, and no longer allows connections from outside the cluster network.
On OpenStack, the machine(set) templates have been updated to set
cloudName and some other properties.
On libvirt, destroy cluster is now more robust in the face of
domains which were already shutdown.
Lots of doc and internal cleanup and minor fixes.
install-config.yml (deprecated in 0.8.0) has been
removed.On AWS, domain pagination for the wizard's base-domain select widget has been fixed. Previously, it would continuously fetch the first page of hosted zones (for accounts with multiple pages of zones) until it hit an error like:
ERROR list hosted zones: Throttling: Rate exceeded
status code: 400, request id: ...
before falling back to a free-form base-domain input.
Nothing published for this version
Nothing published for this version
The change log is [here][1]. SHA 256 for the released binaries:
The change log is here. SHA 256 for the released binaries:
The change log is [here][1]. SHA 256 for the released binaries:
The change log is here. SHA 256 for the released binaries:
none platform for bring-your-own infrastructure
users who want to generate Ignition configurations. The new
platform is mostly undocumented; users will usually interact with it
via [OpenShift Ansible][openshift-ansible].Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
One column per quarter.