Skip to content

kudo-v0.6.0
Compare
Choose a tag to compare
@kensipe kensipe released this 09 Sep 15:57
· 434 commits to master since this release
v0.6.0
c74d227

Release Highlights

KUDO INIT

With new CLI installed you can now use kubectl kudo init command to setup a Kubernetes cluster with install version of KUDO and establish a KUDO_HOME on the client. To manage the details yourself, run kubectl kudo init --dry-run -o=yaml. Using the --dry-run flag will make no changes locally nor at the cluster, however the -o=yaml will output the YAML definitions for the server to STDOUT, making kubectl kudo init --dry-run -o=yaml > kudo-install.yaml an option.

KUDO v0.6.0 introduces the ability to use your own operator repository, details below. In order to configure KUDO to use a different repository it must be configured at the client. Assuming you already have KUDO installed in the cluster, run kubectl kudo init --client-only will establish the default KUDO repository options.

TIP: Looking to have the KUDO CLI "Wait" until KUDO is ready in the cluster? Try kubectl kudo init --wait.

Run kubectl kudo init --help for more details.

KUDO Repository Management

KUDO 0.6.0 introduces the ability to manager repository options with the ability to Add, Remove and List repositories (details with kubectl kudo repo).

kudo repo list will provide a table of repository options with an * denoting the default or "current" repository.

kubectl kudo repo list
NAME      	URL                                           
*community	https://kudo-repository.storage.googleapis.com

Repository Index Creation

Looking to create your own repository? This release provides kubectl kudo repo index ... which will create the index.yaml needed at a repository. Assuming you have a folder operators will a set of operators, you simply run kubectl kudo repo index operators --url=http:/localhost:8080. This assumes you will run a web server at port 8080 locally to use the repository.

Selecting a Repository

All commands that need to interact with a repository (install, upgrade, etc.) now support a new flag --repo. By default without using --repo, the current context repository will be used (denoted by * in repo list). --repo makes it possible to use another repository for a command without change the default context. Assuming a test repo, it is possible to install using kubectl kudo install zookeeper --repo=test.

Creating an Operator Package

Newly add is the ability to create an operator tarball package from a folder with project defined naming conventions and some validation. Run kubectl kudo package operator, assuming operator is the folder of your operator. This will confirm the operator has a valid operator.yaml and params.yaml file and will create a foo-1.0.0.tgz, where foo is the name of the operator and 1.0.0 is the version.

For more details run kubectl kudo package --help.

Changelog

6fab360 Add Arkansas event (#715)
04840db Add Hamburg meetup (#699)
76b5095 Add Nordics tour (#720)
47a70be Add Phoenix date (#719)
8cbb168 Add Tampa Kubernetes Meetup information (#726)
c607f9c Add missing kind to the PR template (#701)
82bf2ee Add update and upgrade docs (#700)
6e498a5 Blogpost for 0.5.0 (#695)
e94ec41 Bundle Feature: Create Package Bundle (#677)
d18ae0e Change date for Glasgow (#724)
3c3346a Final phase of 'developing operators' docs (#651)
c0ae416 Fix broken link to developing-operators (#697)
6f7ba7a Fix flake in CreateOrUpdate (#707)
fa7a7b2 Fix getting started installation for 0.5.0 (#714)
47e7da7 Fix race with ActivePlan between Instance and PlanExecution controllers (#722)
388a9f9 Fix some wording around the update subcommand (#727)
6fdef76 Fix testing link (#716)
842c7f1 Get ready for 0.5.0 (#689)
750c4c9 Instance spec as part of plan execution CRD (#705)
aa31c5a Integration test for update plan (#706)
be37229 KEP: Draft For Repository (targeted for KEP-15) (#654)
3d81a36 KUDO Init (#736)
7d7ce10 Minor docs overhaul: wording, grammar, formatting (#709)
c74d227 Proposal: Support calling out to arbitrary commands in the test harness. (#754)
eddf74b Reduce the indirection by directly referencing controllers (#694)
a0d82e6 Remove the site and docs since they now live in the www repo (#734)
e915644 Repo Add, Remove, List and Context Features (#757)
333e1fb Repo Index (#730)
fba47ba Unify feel of install, upgrade and update (#688)
f6081b9 Update controller dependencies (#746)
9d5c0da Update date for K8s Finland Meetup, fix community link in announcements (#708)
bf8362c Upgrade plan test (#702)
94ef046 Uses Repo Name in kudo install and upgrade
3312f42 add Data Natives Vienna meetup information (#732)
a6162c2 fix lingo in docs: task, not step (#698)
e6ef0ef kafka: use kudo cli in the quickstart examples (#690)
42a347c kudo init client side (#751)
79a2f56 switching maintainer back to 0.5.0 release and adding marshaling tests (#749)
414a82e these are generated files. fixing the grammar causes the repo to be dirty on builds. (#735)
de4f770 update min minikube spec to allow zk/kafka (#704)

Docker images

  • docker pull kudobuilder/controller:latest
  • docker pull kudobuilder/controller:v0.6.0
Assets 24
Loading