Keel - automated Kubernetes deployments for the rest of us - DEPRECATED
This chart is deprecated! You can find the new chart in: - Source: https://github.com/keel-hq/keel/tree/master/chart/keel - Charts repository: https://charts.keel.sh
Keel is a tool for automating Kubernetes deployment updates. Keel is stateless, robust and lightweight.
Keel provides several key features:
No CLI/API - tired of
***ctlfor everything? Keel doesn’t have one. Gets job done through labels, annotations, charts.
Semver policies - specify update policy for each deployment/Helm release individually.
Automatic Google Container Registry configuration - Keel automatically sets up topic and subscriptions for your deployment images by periodically scanning your environment.
Native, DockerHub and Quay webhooks support - once webhook is received impacted deployments will be identified and updated.
Polling - when webhooks and pubsub aren’t available - Keel can still be useful by checking Docker Registry for new tags (if current tag is semver) or same tag SHA digest change (ie:
Notifications - out of the box Keel has Slack and standard webhook notifications, more info here
Note: For now Keel gets installed into
kube-system namespace by default as where Helm’s
Tiller is installed.
Installing the Chart with Kubernetes provider support
Docker image polling and Kubernetes provider are set by default, then Kubernetes deployments can be upgraded when new Docker image is available:
helm upgrade --install keel stable/keel"
Installing the Chart with Helm provider support
Docker image polling is set by default, but we need to enable Helm provider support, then Helm releases can be upgraded when new Docker image is available:
helm upgrade --install keel stable/keel --set helmProvider.enabled="true"
Setting up Helm release to be automatically updated by Keel
Add the following to your app’s
values.yaml file and do
helm upgrade ...:
keel: # keel policy (all/major/minor/patch/force) policy: all # trigger type, defaults to events such as pubsub, webhooks trigger: poll # polling schedule pollSchedule: "@every 3m" # images to track and update images: - repository: image.repository # it must be the same names as your app's values tag: image.tag # it must be the same names as your app's values
The same can be applied with
--set flag without using
helm upgrade --install whd webhookdemo --reuse-values \ --set keel.policy="all",keel.trigger="poll",keel.pollSchedule="@every 3m" \ --set keel.images.repository="image.repository" \ --set keel.images.tag="image.tag"
You can read in more details about supported policies, triggers and etc in the User Guide.
Also you should check the Webhooh demo app and it’s chart to have more clear idea how to set automatic updates.
Uninstalling the Chart
To uninstall/delete the
$ helm delete keel
The command removes all the Kubernetes components associated with the chart and deletes the release.
The following table lists has the main configurable parameters (polling, triggers, notifications, service) of the Keel chart and they apply to both Kubernetes and Helm providers:
||Docker registries polling||
||Enable/disable Helm provider||
||Enable/disable GCR Registry||
||GCP Project ID GCR belongs to|
||Enable/disable GCP Pub/Sub trigger||
||Enable/disable Webhook Notification||
||Remote webhook endpoint|
||Enable/disable Slack Notification||
||Slack approval channel|
||Slack Bot name|
||Enable/disable Keel service||
||Keel service type||
||Keel service port||
||Enable/disable WebhookRelay integration||
Specify each parameter using the
--set key=value[,key=value] argument to
Alternatively, a YAML file that specifies the values for the above parameters can be provided while installing the chart. For example,
$ helm install --name keel -f values.yaml stable/keel
Tip: You can use the default values.yaml