v0.5.0 — introducing v1beta1

Changes since the last release (v0.4.1)

• Conformance: add IPv6 and dual-stack support (#143) by @tpantelis
• conformance: generate report in yaml format (#145) by @AnupamGhosh
• Conformance: Accept implementation metadata via cli flags (#149) by @AnupamGhosh
• Add v1beta1 API and switch usage to v1beta1 across the repo (#133) by @MrFreezeex

The main purpose of this release is to make the v1beta1 CRDs and client available for downstreams. v1alpha1 is still provided, so downstreams are not required to migrate to v1beta1 if they upgrade to this release.

Known issues

None.

v0.4.1

This has the same features as v0.4.0 but includes the CRD version bumps / resets that were forgotten in v0.4.0.

v0.4.0

This release contains the following changes:

Conformance tests:

• use new ServiceExport Condition definitions (#120, @tpantelis)
• ensure the first cluster exports the service before the second cluster (#123, @tpantelis)
• check the service type (#123, @tpantelis)
• check internal traffic policy and traffic distribution (#131, @MrFreezeex)
• check conflict conditions on asymetrical traffic (#132, @MrFreezex)
• check conflicting ports (#136, @MrFreezex)
• fix annotations/labels tests, allow empty endpoints (#134, @MrFreezeex)
• include skipped tests and all labels in the HTML report (#137, @MrFreezeex)
• allow retries with hanging commands (#139, @MrFreezex)
• allow custom domains instead of .clusterset.local (#141, @AnupamGhosh)

CRDs regenerated (#127, @kahirokunn)

Demo:

• use the multicluster support in CoreDNS (#126, @kahirokunn)
• install the MCS API CRDs before CoreDNS starts (#126, @kahirokunn)
• add a .clusterset.local example (#126, @kahirokunn)

E2E:

• relax criteria for the "Local service not impacted" test to avoid flakiness (#121, @tpantelis)

API:

• add the ipFamilies field (#104, @MrFreezeex)
• add a bundle label version in the CRDs and check whether it needs bumping (#116, @MrFreezeex)
• add traffic distribution and internal traffic policies fields (#131, @MrFreezeex)
• add conflict conditions on asymetrical traffic (#132, @MrFreezeex)

Thanks to all the contributors!

v0.3.0

This release adds a number of constants for conditions etc. and embeds the CRD YAML; see #112, #113, and #115 for details.

v0.2.0

This is still v1alpha1, with the latest updates (including exportedLabels and exportedAnnotations, and support for two IP addresses in ServiceImport), and with updated dependencies and a module split. The main module provides the client.

There is one change requiring code changes in dependent projects: ServiceExport now uses API Machinery Condition instead of its own ServiceExportCondition type. The associated ServiceExportConditionType has been removed too.

v0.1.0 - v1alpha1

API Version: v1alpha1

This is the initial v1alpha1 release as used by a variety of implementations.

The SIG is focused on bringing MCS to Beta, but there may still be minor changes to the Alpha API. Any breaking changes before Beta will result in a v1alpha2 release.