Skip to content

KubeDirector v0.5.0
Compare
Choose a tag to compare
@joel-bluedata joel-bluedata released this 17 Jul 15:18
v0.5.0
21f17cb
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

If you reached this page through a direct link, please check the to see what the latest release is before proceeding, just in case this version is outdated.

The major change in this release is the move from operator SDK v0.8.1 to v0.15.2, which has a couple of notable sets of consequences:

  • Anyone building KubeDirector from source, as opposed to using a pre-built operator image, should re-read doc/kubedirector-development.md to become acquainted with new requirements and with some tips for continuing to build your existing local repo. We highly recommend reading this before merging the new release source into your existing source.
  • Anyone who is currently running a KubeDirector 0.4.x deployment and is interested in updating that deployment in-place should read doc/upgrade.md.

KD 0.5.0 supports some additional properties in KubeDirectorApp and KubeDirectorCluster; see the "properties supported by KD v0.5.0+" sections in those tables. These implement three new features:

  • A KD app can indicate that a unique token should be generated to be used for authentication to a service endpoint. This token will be visible in the KD cluster member status, visible within the relevant container (through configcli) for use in setting up that service, and also advertised through an annotation on the K8s Service resource for that member.
  • A KD app can define which lifecycle events (among "configure"/"addnodes"/"delnodes") the members in a role actually care about being notified for. If we can skip sending notifications to a member, then it matters less if that member is down when a KD cluster is reconfigured.
  • A KD cluster can specify a list of "connections" to certain other resources (secrets, configmaps, and/or other KD clusters) whose configuration will be shared within the container (through confligcli). This info will be updated as the connections list is edited or the resources are modified. See the wiki for more details.

The example catalog of KD apps has also been significantly reworked and expanded, including additional complex applications and a collection of usage documentation. We know we have more to do on the front of app-development documentation and that will be a major focus of the next release!

A final bonus QOL improvement is included for automated deployment of KD app CRs. The KD app validation will now allow a PUT to an existing KD app CR that is being used by existing KD clusters, if it is determined that the resulting document (after defaults-substitutions and any other mutations) will not end up changing the "spec" section that the clusters depend on.

Assets 2
Loading