Skip to content

Commit 68692df

Browse files
committed
CHANGELOG: Document changes since v0.9.0
Through 63bdb7f (Merge pull request #1050 from ironcladlou/trouble-doc, 2019-01-14).
1 parent 63bdb7f commit 68692df

File tree

1 file changed

+108
-0
lines changed

1 file changed

+108
-0
lines changed

CHANGELOG.md

Lines changed: 108 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -4,6 +4,114 @@ All notable changes to this project will be documented in this file.
44

55
The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/).
66

7+
## 0.10.0 - 2019-01-15
8+
9+
### Added
10+
11+
- The installer pushes an Infrastructure object to
12+
infrastructures.config.openshift.io with platform information.
13+
Cluster components should use this instead of the deprecated
14+
`cluster-config-v1` resource.
15+
- `openshift-install` has a new `completion` subcommand, to generation
16+
shell-completion code (currently only for Bash).
17+
- On AWS, `destroy cluster` now also removed IAM users with the usual
18+
tags. We don't create these users yet, but the removal sets the
19+
stage for the coming credentials operator.
20+
21+
### Changed
22+
23+
- Install configuration now includes a new `apiVersion` property which
24+
must be set to `v1beta1`. Future changes to the install-config
25+
schema will result in new versions, allowing new installers to
26+
continue to support older install-config schema (and older
27+
installers to error out when presented with newer install-config
28+
schema). Changes to the schema since 0.9.0:
29+
30+
- `clusterID` has been removed. This should be a new UUID for
31+
every cluster, so there is no longer an easy way for users to
32+
configure it.
33+
- Image configuration has been removed. Almost all users should
34+
be fine with the installer-chosen RHCOS. Users who need to
35+
override the RHCOS build (because they're testing new RHCOS
36+
releases) can set a new `OPENSHIFT_INSTALL_OS_IMAGE_OVERRIDE`
37+
environment variable.
38+
- Per-platform network properties have been consolidated into the
39+
platform-agnostic `machineCIDR` from which node IP addresses are
40+
assigned.
41+
- On libvirt, all machine-pool configuration has been removed, as
42+
no remaining properties were supported by the libvirt
43+
cluster-API provider.
44+
45+
- `install-config.yaml` read during [staged
46+
installs](docs/user/overview.md#multiple-invocations) will now have
47+
installer-defaults applied for missing properties. This allows you
48+
to set only the properties you are interested in overriding, and
49+
allow the installer to manage the remaining properties.
50+
- `create ignition-configs` now also writes the admin kubeconfig to
51+
the asset directory, to support bring-your-own-infrastructure use
52+
cases.
53+
- The bootstrap node now [serves
54+
journals](docs/user/troubleshooting.md#troubleshooting-the-bootstrap-node)
55+
for easier troubleshooting.
56+
- The validity for the initial kubelet TLS certificate has been
57+
increased from one hour to 24 hours, to give
58+
bring-your-own-infrastructure users longer to manually distribute
59+
the certificate before it expires.
60+
- The key for the root certificate authority is no longer pushed into
61+
the cluster (not even to the bootstrap node).
62+
- Machine(set)s generated by the installer now use `providerSpec`
63+
instead of the deprecated `providerConfig`.
64+
- On AWS, the load balancers now use HTTPS health checks to reduce log
65+
noise like:
66+
67+
http: TLS handshake error from 10.0.20.86:28372: EOF
68+
69+
- On AWS, IAM roles are now tagged with the usual resource tags
70+
(`openshiftClusterID`, etc.). Some other resources have had their
71+
tags updated to match those conventions (e.g. the internal Route 53
72+
hosted zone was updated from `KubernetesCluster` to
73+
`kubernetes.io/cluster/{name}: owned`).
74+
- The OpenStack platform has been removed from the install-config
75+
wizard while it remains experimental. It is still available for
76+
users who supply their own `install-config.yaml`.
77+
- On OpenStack, the service VP now respects any SSH key specified in
78+
the install configuration.
79+
- On OpenStack, a developer-only internal DNS server has been removed,
80+
so users need to configure additional records for the existing
81+
external DNS zone.
82+
- On OpenStack, Neutron trunk ports are now used for VM network
83+
interfaces if Neutron supports them to support future Kuryr
84+
integration.
85+
- On OpenStack, masters and workers have been consolidated in a single
86+
subnet to simplify the deployment.
87+
- On OpenStack, the Ignition security group now only allows internal
88+
connections, and no longer allows connections from outside the
89+
cluster network.
90+
- On OpenStack, the machine(set) templates have been updated to set
91+
`cloudName` and some other properties.
92+
- On libvirt, `destroy cluster` is now more robust in the face of
93+
domains which were already shutdown.
94+
- Lots of doc and internal cleanup and minor fixes.
95+
96+
### Removed
97+
98+
- Support for `install-config.yml` (deprecated in 0.8.0) has been
99+
removed.
100+
101+
### Fixed
102+
103+
- On AWS, domain pagination for the wizard's base-domain select widget
104+
has been fixed. Previously, it would continuously fetch the first
105+
page of hosted zones (for accounts with multiple pages of zones)
106+
until it hit an error like:
107+
108+
```
109+
ERROR list hosted zones: Throttling: Rate exceeded
110+
status code: 400, request id: ...
111+
```
112+
113+
before falling back to a free-form base-domain input.
114+
7115
## 0.9.0 - 2019-01-05
8116
9117
### Added

0 commit comments

Comments
 (0)