Skip to content

Commit

Permalink
CHANGELOG: Document changes since v0.3.0
Browse files Browse the repository at this point in the history
Through 1e2b796 (Merge pull request openshift#594 from crawford/nlb,
2018-11-02).
  • Loading branch information
wking committed Nov 2, 2018
1 parent 1e2b796 commit e15703e
Showing 1 changed file with 78 additions and 0 deletions.
78 changes: 78 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,6 +4,77 @@ All notable changes to this project will be documented in this file.

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

## 0.4.0 - 2018-11-02

### Added

- [The ingress operator][ingress-operator] is no longer masked. The
old Tectonic ingress operator has been removed.
- The [checkpointer operator][checkpointer-operator] is no longer
masked. It runs on the production cluster, but not on the bootstrap
node.
- Cloud credentials are now pushed into a secret where they can be
consumed by cluster-API operators and other tools.

### Changed

- For consistency with 0.3.0's `destroy`, the the old
`install-config`, `manifests`, `ignition-configs`, and `cluster`
commands have been pushed down under a new `create` subcommand. For
example, you should now use `openshift-install create cluster`
instead of `openshift-install cluster`. The old commands are
deprecated.
- etcd discovery now happens via `SRV` records. On libvirt, this
requires a new Terraform provider, so users with older providers
should [install a newer
version](docs/dev/libvirt-howto.md#install-the-terraform-provider).
This also allows all masters to use a single Ignition file.
- On AWS the API and service load balancers have been changed from
[classic load balancers][aws-elb] to [network load
balancers][aws-nlb]. This should avoid [some latency issues we were
seeing with classic load balancers][aws-elb-latency], and network
load balancers are cheaper.
- The bootstrap kubelet is no longer part of the production cluster.
This reduces complexity and keeps production pods off of the
temporary bootstrap node.
- [The cluster-version operator][cluster-version-operator] now runs in
a static pod on the bootstrap node until the production control
plane comes up. This breaks a cyclic dependency between the
production API server and operators.
- The bootstrap control plane now waits for some core pods to come up
before exiting.
- [The machine-API operator][machine-api-operator] now reads the
install-config from the `cluster-config-v1` config-map, instead of
from an operator-specific configuration.
- AWS AMIs and libvirt images are now pulled from the new [RHCOS
pipeline][rhcos-pipeline].
- Updated the security contact information for CoreOS -> Red Hat.
- Lots of doc and internal cleanup and minor fixes.

### Fixed

- The `bootstrap-complete` event (new in 0.3.0) is now pushed at the
appropriate time (it was too early in 0.3.0).
- `delete cluster` is now more robust on AWS, removing resources with
either the `tectonicClusterID` or `kubernetes.io/cluster/<name>:
owned` tags. It also removes pending instances as well (it used to
only remove running instances).
- Bootstrap Ignition edits (via `create ignition-configs`) no longer
suffer from a `worker.ign` dependency cycle, which had been
clobbering manual `bootstrap.ign` changes.
- The state-purging implementation respects `--dir`, avoiding `remove
...: no such file or directory` errors during [staged
installs](docs/user/overview.md#multiple-invocations).
- Cross-filesystem Terraform state recovery during `destroy bootstrap`
no longer raises `invalid cross-device link`.
- Bootstrap binaries are now located under `/usr/local/bin`, avoiding
SELinux violations on RHEL 8.

### Removed

- The kube-addon operator no longer installs an image registry, now
that [the registry operator][registry-operator] fills that role.

## 0.3.0 - 2018-10-22

### Added
Expand Down Expand Up @@ -136,12 +207,19 @@ installer and follow along as it guides you through the process.
The `tectonic` command and tarball distribution are gone. Please use
the new `openshift-install` command instead.

[aws-elb]: https://docs.aws.amazon.com/elasticloadbalancing/latest/classic/introduction.html
[aws-elb-latency]: https://github.com/openshift/installer/pull/594#issue-227786691
[aws-nlb]: https://docs.aws.amazon.com/elasticloadbalancing/latest/network/introduction.html
[checkpointer-operator]: https://github.com/openshift/pod-checkpointer-operator
[cluster-api-provider-aws]: https://github.com/openshift/cluster-api-provider-aws
[cluster-version-operator]: https://github.com/openshift/cluster-version-operator
[dot]: https://www.graphviz.org/doc/info/lang.html
[ingress-operator]: https://github.com/openshift/cluster-ingress-operator
[kube-apiserver-operator]: https://github.com/openshift/cluster-kube-apiserver-operator
[kube-controller-manager-operator]: https://github.com/openshift/cluster-kube-controller-manager-operator
[machine-api-operator]: https://github.com/openshift/machine-api-operator
[machine-config-operator]: https://github.com/openshift/machine-config-operator
[Prometheus]: https://github.com/prometheus/prometheus
[registry-operator]: https://github.com/openshift/cluster-image-registry-operator
[rhcos-pipeline]: https://releases-rhcos.svc.ci.openshift.org/storage/releases/maipo/builds.json
[service-serving-cert-signer]: https://github.com/openshift/service-serving-cert-signer

0 comments on commit e15703e

Please sign in to comment.