Back to index

4.6.60

Jump to: Complete Features | Incomplete Features | Complete Epics | Incomplete Epics | Other Complete |

Changes from 4.5.41

Note: this page shows the Feature-Based Change Log for a release

Complete Features

These features were completed when this image was assembled

Incomplete Features

When this image was assembled, these features were not yet completed. Therefore, only the Jira Cards included here are part of this release

Complete Epics

This section includes Jira cards that are linked to an Epic, but the Epic itself is not linked to any Feature. These epics were completed when this image was assembled

Incomplete Epics

This section includes Jira cards that are linked to an Epic, but the Epic itself is not linked to any Feature. These epics were not completed when this image was assembled

Other Complete

This section includes Jira cards that are not linked to either an Epic or a Feature. These tickets were completed when this image was assembled

The background is the following RFE: https://issues.redhat.com/browse/RFE-924 and is leveraged by OpenShift Dedicated.

 

Story: As a cluster administrator I would like to rely on a more robust image pruning mechanism so that pruning commences even in the face of invalid image references.

 

Acceptance criteria:

  • the Image Registry Operator should support the `--ignore-invalid-refs` flag to be passt on to the image pruner
  • the option should be enabled by default for new clusters
  • the option should remain disabled for existing clusters

discover-etcd-initial-cluster was written very early on in the cluster-etcd-operator life cycle. We have observed at least one bug in this code and in order to validate logical correctness it needs to be rewritten with unit tests.

PR: https://github.com/openshift/etcd/pull/73