Skip to content

v0.4.0
Compare
Choose a tag to compare
@github-actions github-actions released this 18 Sep 18:13
· 7 commits to main since this release
v0.4.0
This tag was signed with the committer’s verified signature.
xrstf Christoph Mewes
SSH Key Fingerprint: T6KhNP27At/KCYLLTNLHgbmUghiVeJAtgGAazABecd0
Verified
Learn about vigilant mode.
2488477
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

The team is happy to announce the 4th minor release of the kcp Sync Agent. This release brings the long awaited support for kcp 0.28, basic support for events in kcp and more flexible references in PublishedResources.

Changelog since version 0.3

New Features

  • #89: Add support for kcp 0.28; support configuring an APIExportEndpointSlice instead of an APIExport using command line flags (by @xrstf)
  • #83: References can now return lists of values to allow a single related resource configuration to match many Kubernetes objects at once (by @xrstf)
  • #87: The sync-agent will now create events on source objects in kcp. Existing APIBindings to APIExports managed by the agent will need to be updated to accept the new events permission claim (by @xrstf)

Changes

  • #72: Refactor agent to work based on multicluster-runtime (by @xrstf)

Bugfixes

  • #91: Fix ClusterName and WorkspacePath being empty in templating strings for related resources (by @xrstf)

Documentation

  • #84: Add kube-bind comparision page (by @xrstf)

Upgrade Notes

  • APIExportEndpointSlice support: The agent can now source the URL to connect to from an APIExportEndpointSlice instead of an APIExport. Admins may pick their preferred migration path:

    • On kcp 0.27 you can keep either the --apiexport-ref or manually create an APIExportEndpointSlice and then use --apiexportendpointslice-ref to point the agent to it.
    • On kcp 0.28 the APIExport will not contain the virtual workspace URLs anymore and admins will have to switch to the APIExportEndpointSlice. This can -- in the simplest case -- be the endpoint slice created by kcp with the same name as the APIExport, but admins may also choose to create their own endpoint slices.

    Note that the syncagent still only supports a single (the first) URL of either an APIExportEndpointSlice or the APIExport. Support for connecting to multiple endpoints is planned for the future but depends significantly on the kcp provider for multicluster-runtime.

    APIExportEndpointSlices do not need to be in the same workspace as their referenced APIExport, but in those cases the agent needs the appropriate permissions in both workspaces.

Contributors

xrstf
Assets 7
Loading