v0.6.2

[shaneutt]

API versions: v1beta1, v1alpha2

This is a patch release that predominantly includes updated conformance tests
for implementations to implement.

For all major changes since the v0.5.x release series, please see the
v0.6.0 release notes.

Maintenance

• As per changes in upstream to container image registries we replaced all
  usage of the k8s.gcr.io registry with registry.k8s.io.
  (chore: replace usage of the deprecated k8s.gcr.io registry #1736, @shaneutt)

Bug Fixes

• Fix invalid HTTP redirect/rewrite examples.
  (fix: remove invalid redirect examples #1787, @Xunzhuo)

Conformance Test Updates

• The HTTPRouteInvalidCrossNamespaceParentRef conformance test now checks for
  the NotAllowedByListeners reason on the HTTPRoute's Accepted: false
  condition to better indicate why the route was note accepted.
  (conformance: check reason in HTTPRouteInvalidCrossNamespaceParentRef test #1714, @skriss)
• A conformance test was added for HTTPRoute to cover the behavior of a
  non-matching SectionName similar to what was already present for
  ListenerPort.
  (Add missing sectionName conformance test #1719, @zaunist)
• Fixed an issue where tests may fail erroneously on the removal of resources
  that are already removed.
  (chore: cleanup err check in conformance tests #1745, @mlavacca)
• Logging in conformance utilities related to resource's ObservedGeneration
  has been improved to emit the `ObservedGenerations that are found for the
  purpose of making it easier to debug test failures and be more verbose about
  the objects in question.
  (Log Generation / Observed generation. #1761, @briantkennedy)
  (Improve conformance test log message. #1763, @briantkennedy)
• Patch instead of update in some places in conformance tests to reduce noise
  in logs.
  (conformance: use Patch to make ObservedGeneration tests robust against conflicts #1760, @michaelbeaumont)
• Added AttachedRoutes testing to conformance tests.
  (conformance: add attachedRoutes to conformance tests #1624, @ChaningHwang)
• The conformance tests always check that the HTTPRoute ResolvedRefs condition
  is enforced, even when the status is true.
  (conformance: HTTPRoute resolvedRefs condition always checked #1668, @mlavacca)

---

This discussion was created from the release v0.6.2.