CHANGELOG.md

next

3.6.2

• Pinning stats-instrument to < 3.9 to avoid breaking changes.

3.6.1

Features

• Enable the option to bypass endpoint validation for a service by using the annotation krane.shopify.io/skip-endpoint-validation: true.

3.6.0

• Test against k8s 1.29, 1.30
• Drop support for k8s 1.24

3.5.3

• Fix a minor bug in the RestartAPIError class (#953)

3.5.2

• Fixed an issue where deploying StatefulSets monitored the health of the previous revision's pods instead of the updated one.

3.5.1

• Fixed successful deployment check for StatefulSets introduced in v3.3.0.

3.5.0

• Test against k8s 1.28
• Drop support for k8s 1.23

3.4.2

• Remove flag --skip-dry-run (see #946)
• Remove support for batched server-side dry-run (#946)

3.4.1

• Added flag --skip-dry-run to completely opt out of dry run validation.

3.4.0

• Use prune-allowlist instead of prune-whitelist for 1.26+ clusters. Clusters running 1.25 or less will continue to use --prune-whitelist. #940

3.3.0

Enhancements

• Enable detection of successful StatefulSet deploys when the updateStrategy is onDelete, behind an annotation. #926

3.2.0

Enhancements

• Test against k8s 1.26

3.1.0

Enhancements

• Modify HorizontalPodAutoscaler resource class used. #920.

3.0.1

• Add Event to the list of resources not to be pruned on a deployment. Kubernetes should clean these up automatically. This can cause unnessessary deployment timeouts and increased deployment time. #909

3.0.0

Enhancements

• CI test matrix now test all Krane supported Ruby and Kubernetes versions. Ruby: 3.1.2 , 3.0.4 , 2.7.6, Kubernetes: - 1.24.6, 1.23.12, 1.22.15.

Breaking Changes

• Remove unsupported Kubernetes and Ruby versions from Krane and CI #905. See supported Kubernetes and Ruby versions in Compatibility. If you are using Kubernetes <v1.22 keep using Krane v2.4.9.

2.4.9

• Fixed a Ruby 3.1 regression that caused an exception when using a --bindings=@<file> argument to krane render #900

2.4.8

• update googleauth gem version to 1.2
• add the ruby-lsp gem to development group in the Gemfile

2.4.7

Bug fixes

• Fix replace-force deployment method override.

/usr/local/bundle/gems/krane-2.4.6/lib/krane/resource_deployer.rb:119:in `block in deploy_resources': Unexpected deploy method! (:"replace-force") (ArgumentError)

Dash (-) must be replaced with underscore (_) before applying it as method on kubernetes resource.

2.4.6

Bug fixes

• Extend #886 to not only secrets but anything that doesn't match failed to sync %s cache #886 It seems an issue when too many pods are referencing the same secret/configmap kubernetes/kubernetes#74755, so instead of failing fast, it'll now let the resources attempt to succeed.
• Add missing unit test for above feature.

2.4.5

Bug fixes

• Do not fail fast for CreateContainerConfigError when message include issues mounting the secret, to let the pods be recreated and possible succeed #885

2.4.4

Enhancements

• Improve DaemonSet rollout by ignoring Evicted Pods #883

2.4.3

Enhancements

• Improve DaemonSet rollout #881

2.4.2

Bug fixes

• Resolve errors for StatefulSet restart with updateStrategy: OnDelete #876
• Timeouts during the "predeploy priority resources" phase now raise DeploymentTimeoutError instead of FatalDeploymentError #874

2.4.1

Enhancements

• Support restart task for stateful sets that use the OnDelete strategy #840
• Make krane render produce output in a deterministic order #871

Other

• Remove buildkite #869

2.4.0

Enhancements

• Ensure deploy tasks fail without at least one non-empty resource #865

Other

• Remove Ruby 2.6 and K8s < 1.19 from the CI testing matrix. All fixtures have been updated to be compatible with K8s 1.22+.

2.3.7

• isolated_execution_state active_support require for Rails 7+

2.3.6

• Update kubeclient for better Ruby 3.1 compatibility.

2.3.5

• Psych 4 compatibility

2.3.4

• Fix for CVE-2021-41817. See ServicesDB action item here.

2.3.3

• Another Psych 4.0 compatibility fix #844

2.3.2

• Fix compatibility with Psych 4.0 #843

2.3.1

• Fix a bug in RestartTask where a NoMethodError is thrown if any of the target resources do not have annotations #841

2.3.0

• Restart tasks now support restarting StatefulSets and DaemonSets, in addition to Deployments #836

2.2.0

Enhancements

• Add a new option --selector-as-filter to command krane deploy and krane global-deploy #831

2.1.10

Bug Fixes

• Don't gather prunable resources by calling uniq only on kind: use group as well. Otherwise certain resources may not be added to the prune whitelist if the same kind exists across multiple groups #825
• Fix resource discovery failures when API paths are not located at the root of the API server (this occurs, for example, when using Rancher proxy) #827

Other

• Fix ERB deprecation of positional arguments #828

2.1.9

Other

• Don't package screenshots in the built gem to reduce size #817

2.1.8

Other

• Change statsd-instrument dependency constraint to < 4 #815

2.1.7

Enhancements

• ENV["KRANE_LOG_LINE_LIMIT"] allows the number of container logs printed for failures to be configurable from the 25 line default #803.

Other

• Remove the overly tight timeout on cluster resource discovery, which was causing too many timeouts in high latency environments #813

2.1.6

Enhancements

• Remove the need for a hard coded GVK overide list via improvements to cluster discovery #778

Bug Fixes

• Remove resources that are targeted by side-effect-inducing mutating admission webhooks from the serverside dry run batch #798

2.1.5

• Fix bug where the wrong dry-run flag is used for kubectl if client version is below 1.18 AND server version is 1.18+ #793.

2.1.4

Enhancements

• Attempt to batch run server-side apply in validation phase instead of dry-running each resource individually #781.
• Evaluate progress condition only after progress deadline seconds have passed since deploy invocation #765.

Other

• Dropped support for Ruby 2.5 due to EoL. #782.
• Only patch JSON when run as CLI, not as library #779.

2.1.3

• Add version exception for ServiceNetworkEndpointGroup (GKE resource) #768
• Kubernetes 1.14 and lower is no longer officially supported as of this version (#766)

2.1.2

• Add version exception for FrontendConfig (GKE resource) #761

2.1.1

Bug Fixes

• Fix the way environment variables are passed into the EJSON decryption invocation #759

2.1.0

Features

• (experimental) Override deploy method via annotation. This feature is considered alpha and should not be considered stable #753

Enhancements

• Increased the number of attempts on kubectl commands during Initializing deploy phase #749
• Increased attempts on kubectl apply command during deploy #751
• Whitelist context deadline error during kubctl dry run #754
• Allow specifying a kubeconfig per task in the internal API #746

2.0.0

Breaking Changes

• Remove kubernetes deploy annotation prefix #738

Bug Fixes

• Always set a deployment_id, even if the current_sha isn't set #730
• YAML string scalars with scientific/e-notation numeric format not properly quoted. #740

1.1.4

Bug Fixes

• Properly look up constant on Krane namespace. #720

Enhancements

• Allow to configure image_tag when using task runner. #719

1.1.3

Bug Fixes

• Retry dry-run validation when no error is returned. #705
• Stop deploys if ClusterResourceDiscovery's kubectl calls fail. #701

Other

• Dropped support for Ruby 2.4 since it will be EoL shortly. #693.
• Ruby 2.7 support: fix deprecation warnings, add testing. #710

1.1.2

Enhancements

• Don't treat containerCannotRun termination reason as a fatal deploy failure, since it is usually transient. #694

Bug Fixes

• Help ruby correctly identify kubectl output encoding. #646
• Add an override for Job kind for version batch/v2alpha1 #696

Other

• --stdin flag is deprecated. To read from STDIN, use -f - (can be combined with other files/directories) #684.
• Reduces the number of container logs printed for failures from 250 to 25 to reduce noise. #676
• Remove hardcoded cloudsql class. #680

1.1.1

Enhancements

• Detect and handle case when webhook prevents server-dry-run. #663
• Deploy CustomResources after most other resources in the priority deploy phase. #672

Bug Fixes

• Prints the correct argument name in error message. #660
• Fix mistakes in README.md #664, #659, & #668
• Restores the default value of the --verbose-log-prefix flag on krane deploy to false. #673

Other

• Relax dependency requirements. #657

1.1.0

Bug Fixes

• Fix a bug causing secret generation from ejson to fail when decryption succeeded but a warning was also emitted. #647

Enhancements

• Warm the ResourceCache before running resource.sync to improve sync performance. (#603)

1.0.0

We've renamed the gem and cli to Krane. See our migration guide to help navigate the breaking changes.

1.0.0.pre.2

Enhancements

• Relax thor version requirement. (#731)
• Relax googleauth restriction. (#731)

1.0.0.pre.1

Important!

• This is the final release of KubernetesDeploy. Version 1.0.0 will be released under the name Krane. We've added a migration guide to help make it easier to migrate. (#607)

Enhancements

• (beta) krane deploy will now consider all namespaced resources eligible for pruning and does not respect the krane.shopify.io/prunable annotation. This adds 5 additional types: Endpoints, Event, LimitRange, ReplicationController, and Lease. (#616

• (beta) Added the --stdin flag to krane deploy|global-deploy|render to read resources from stdin. (#630)

0.31.1

Bug Fixes

• Fix a scoping issue of ClusterResourceDiscovery where it was not visible to kubernetes-run, causing a crash. (#624)

0.31.0

Enhancements

• (alpha) Add a new krane global-deploy task for deploying global resources. Note that global pruning is turned on by default (#602 and #612)
• Add support for deploying resources that use generateName (#608)
• ENV["REVISION"] is not transparently passed into krane. Instead, you must now use the --current-sha flag to set the current_sha ERB binding in your templates. Note that kubernetes-deploy, but not krane, can still use ENV["REVISION"] as a fallback if --current-sha is not provided. (#613)

Bug Fixes

• krane deploy can accept multiple filenames with -f flag (#606)
• Ensure DaemonSet status has converged with pod statuses before reporting rollout success (#617)

Other

• Update references from using kubernetes-deploy to krane in preparation for 1.0 release (#585)
• Refactor StatsD usage so we can depend on the latest version again. (#594)

0.30.0

Enhancements

• [Breaking change] Added PersistentVolumeClaim to the prune whitelist. (#573)
  • To see what resources may be affected, run kubectl get pvc -o jsonpath='{ range .items[*] }{.metadata.namespace}{ "\t" }{.metadata.name}{ "\t" }{.metadata.annotations}{ "\n" }{ end }' --all-namespaces | grep "last-applied"
  • To exclude a resource from kubernetes-deploy (and kubectl apply) management, remove the last-applied annotation kubectl annotate pvc $PVC_NAME kubectl.kubernetes.io/last-applied-configuration-.
• Deploying global resources directly from KubernetesDeploy::DeployTask is disabled by default. You can use allow_globals: true to enable the old behavior. This will be disabled in the Krane version of the task, and a separate purpose-built task will be provided. #567
• Deployments to daemonsets now better tolerate autoscaling: nodes that appear mid-deploy aren't required for convergence. #580

0.29.0

Enhancements

• The KubernetesDeploy::RenderTask now supports a template_paths argument. (#555)
• We no longer hide errors from apply if all sensitive resources have passed server-dry-run validation. (#570)

Bug Fixes

• Handle improper duration values more elegantly with better messaging

Other

• We now require Ruby 2.4.x since Ruby 2.3 is past EoL.
• Lock statsd-instrument to 2.3.X due to breaking changes in 2.5.0

0.28.0

Enhancements

• Officially support Kubernetes 1.15 (#546)
• Make sure that we only declare a Service of type LoadBalancer as deployed after its IP address is published. #547
• Add more validations to RunnerTask. #554
• Validate secrets with --server-dry-run on supported clusters. #553 Bug Fixes
• Fix a bug in rendering where we failed to add a yaml doc separator (---) to an implicit document if there are multiple documents in the file. (#551)

Other

• Kubernetes 1.10 is no longer officially supported as of this version (#546)
• We've added a new Krane cli. This code is in alpha. We are providing no warranty at this time and reserve the right to make major breaking changes including removing it entirely at any time. (#256)
• Deprecate kubernetes-deploy.shopify.io annotations in favour of krane.shopify.io (#539)

0.27.0

Enhancements

• (alpha) Introduce a new -f flag for kubernetes-deploy. Allows passing in of multiple directories and/or filenames. Currently only usable by kubernetes-deploy, not kubernetes-render. #514
• Initial implementation of shared task validation objects. #533
• Restructure requires so that requiring a given task actually gives you the dependencies you need, and doesn't give what you don't need. #487
• [Breaking change] Added ServiceAccount, PodTemplate, ReplicaSet, Role, and RoleBinding to the prune whitelist.
  • To see what resources may be affected, run kubectl get $RESOURCE -o jsonpath='{ range .items[*] }{.metadata.namespace}{ "\t" }{.metadata.name}{ "\t" }{.metadata.annotations}{ "\n" }{ end }' --all-namespaces | grep "last-applied"
  • To exclude a resource from kubernetes-deploy (and kubectl apply) management, remove the last-applied annotation kubectl annotate $RESOURCE $SECRET_NAME kubectl.kubernetes.io/last-applied-configuration-.

Bug Fixes

• StatefulSets with 0 replicas explicitly specified don't fail deploy. #540
• Search all workloads if a Pod selector doesn't match any workloads when deploying a Service. #541

Other

• EjsonSecretProvisioner#new signature has changed. EjsonSecretProvisioner objects no longer have access to kubectl. Rather, the ejson-keys secret used for decryption is now passed in via the calling task. Note that we only consider the new and run(!) methods of tasks (render, deploy, etc) to have inviolable APIs, so we do not consider this change breaking. #514

0.26.7

Other

• Bump googleauth dependency. (#512)

0.26.6

Bug Fixes

• Re-enable support for YAML aliases when using YAML.safe_load #510

0.26.5

Bug Fixes

• Support 'volumeBindingMode: WaitForFirstConsumer' condition in StorageClass. #479
• Fix: Undefined method "merge" on LabelSelector. #488

Enhancements

• Officially support Kubernetes 1.14. #461
• Allow customising which custom resources are deployed in the pre-deploy phase. #505

Other

• Removes special treatment of GCP authentication by upgrading to kubeclient 4.3. #465

0.26.4

Bug fixes

• Adds several additional safeguards against the content of Secret resources being logged. #474

Enhancements

• Improves scalability by removing a check that caused recoverable registry problems to fail deploys. #477

Other

• Relaxes our dependency on the OJ gem. #471

0.26.3

Bug fixes

• Fixes a bug introduced in 0.26.0 where listing multiple files in the $KUBECONFIG environment variable would throw an error (#468)
• Fixes a bug introduced in 0.26.2 where kubernetes-render started adding YAML headers to empty render results (#467)

0.26.2

Enhancements

• kubernetes-render outputs results of rendering yml.erb files without passing them through a yaml parser. (#454)

Bug fixes

• Remove use of deprecated feature preventing use with Kubernetes 1.14 (#460)

0.26.1

Bug fixes

• Fixes a bug where config/deploy/$ENVIRONMENT would be used unconditionally if the ENVIRONMENT environment variable is set, ignoring any --template-dir argument passed.

0.26.0

Enhancements

• Add support for NetworkPolicies (#422)
• Setting the REVISION environment variable is now optional (#429)
• Defaults KUBECONFIG to ~/.kube/config (#429)
• Uses TASK_ID environment variable as the deployment_id when rendering resource templates for better Shipit integration. (#430)
• Arguments to --bindings will now be deep merged. (#419)
• kubernetes-deploy and kubernetes-render now support reading templates from STDIN. (#415)
• Support for specifying a --selector, a label with which all deployed resources are expected to have, and by which prunable resources will be filtered. This permits sharing a namespace with resources managed by third-parties, including other kubernetes-deploy deployments. (#439)
• Lists of resources printed during deployments will now be sorted alphabetically. (#441)
• Bare / unmanaged pods run as pre-deployment tasks will now stream logs if there is only one of them. (#436)

Features

• [Breaking change] Support for deploying Secrets from templates (#424). Non-ejson secrets are now fully supported and therefore subject to pruning like any other resource. As a result:
  • If you previously manually kubectl apply'd secrets that are not passed to kubernetes-deploy, your first deploy using this version is going to delete them.
  • If you previously passed secrets manifests to kubernetes-deploy and they are no longer in the set you pass to the first deploy using this version, it will delete them.
  • To identify potentially affected secrets in your cluster, run: kubectl get secrets -o jsonpath='{ range .items[*] }{.metadata.namespace}{ "\t" }{.metadata.name}{ "\t" }{.metadata.annotations}{ "\n" }{ end }' --context=$YOUR_CONTEXT_HERE --all-namespaces | grep -v "kubernetes-deploy.shopify.io/ejson-secret" | grep "last-applied" | cut -f 1,2. To exclude a secret from kubernetes-deploy (and kubectl apply) management, remove the last-applied annotation kubectl annotate secret $SECRET_NAME kubectl.kubernetes.io/last-applied-configuration-.
  • The secret ejson-keys will never be pruned by kubernetes-deploy. Instead, it will fail the deploy at the validation stage (unless --no-prune is set). (#447)

0.25.0

WARNING

This version contains an error for handling the --template-dir argument. If the ENVIRONMENT environment variable is set, the template directory will be forcefully set to config/deploy/$ENVIRONMENT. This has been fixed in version 0.26.1

Features

• Support timeout overrides on deployments (#414)

Bug fixes

• Attempting to deploy from a directory that only contains secrets.ejson will no longer fail deploy (#416)
• Remove the risk of sending decrypted EJSON secrets to output(#431)

Other

• Update kubeclient gem to 4.2.2. Note this replaces the KubeclientBuilder::GoogleFriendlyConfig class with KubeclientBuilder::KubeConfig (#418). This resolves #396 and should allow us to support more authentication methods (e.g. exec for EKS).
• Invalid context when using kubernetes-run gives more descriptive error(#423)
• When resources are not found, instead of being Unknown, they are now labelled as Not Found(#427)

0.24.0

Features

• Add support for specifying pass/fail conditions of Custom Resources (#376).
• Add support for custom timeouts for Custom Resources(#376)

Enhancements

• Officially support Kubernetes 1.13 (#409)

Bug fixes

• Fixed bug that caused NameError: wrong constant name if custom resources had kind with a lowercase first letter. (#413)

Other

• Kubernetes 1.9 is no longer officially supported as of this version

0.23.0

Features

• New command: kubernetes-render is a tool for rendering ERB templates to raw Kubernetes YAML. It's useful for seeing what kubernetes-deploy does before actually invoking kubectl on the rendered YAML. It's also useful for outputting YAML that can be passed to other tools, for validation or introspection purposes. (#375)
• [Breaking change] This release completes the conversion of kubernetes-deploy StatsD metrics to distributions, which was done for kubernetes-restart and kubernetes-run in v0.22.0.
• Several new distribution metrics are available to give insight into the timing of each step of the deploy process: KubernetesDeploy.validate_configuration.duration, KubernetesDeploy.discover_resources.duration, KubernetesDeploy.validate_resources.duration, KubernetesDeploy.initial_status.duration, KubernetesDeploy.create_ejson_secrets.duration, KubernetesDeploy.apply_all.duration, KubernetesDeploy.sync.duration
• [Breaking change] KubernetesDeploy.resource.duration no longer includes sha or resource tags. (#392)

Enhancements

• Roles are now predeployed before RoleBindings (#380)
• Several performance enhancements for deploys to namespaces with hundreds of resources.
• KubernetesDeploy no longer modifies the global StatsD configuration when used as a gem (#384)

Bug fixes

• Handle out-of-order arrival of entries from different streams when processing logs (#401)

0.22.0

Features

• [Breaking change] kubernetes-restart now produces StatsD distribution instead of metric. Dashboards that used these metrics will need to be updated. (#374)
• kubernetes-run now produces StatsD distribution to aid in tracking usage (#374)

Enhancements

• Predeploy RoleBinding before unmanaged pods (#354)

Bug Fixes

• Fixed bug in kubernetes-restart that caused "Pod spec does not contain a template container called 'task-runner'" error message to not be printed (#371)

Other

• Kubernetes 1.8 is no longer officially supported as of this version

0.21.1

Enhancements

• Improved failure detection for job resources. (#355)
• Unmanaged pods are now immediately identified as failed if they are evicted, preempted or deleted out of band. This is especially important to kubernetes-run. (#353)

Other

• Relaxed our googleauth dependency. (#333)

0.21.0

Features

• [Breaking change] kubernetes-run now streams container logs and waits for the pod to succeed or fail by default. You can disable this using --skip-wait, or you can use --max-watch-seconds=seconds to set a time limit on the watch. (#337)

Other

• Kubernetes 1.7 is no longer officially supported as of this version

0.20.6

Enhancements

• All resources marked as prunable will now be added to the prune whitelist (#326)
• Improve deploy status detection by ensuring we examine the correct generation (#325)

0.20.5

Enhancements

• Add Job resource class (#295)
• Add CustomResourceDefinition resource class (#306)
• Officially support Kubernetes 1.10 (#308)
• SyncMediator will only batch fetch resources when there is a sufficiently large enough set of resources being tracked (#316)
• Allow CRs to be pruned based on kubernetes-deploy.shopify.io/prunable annotation on the custom resource definitions (312)
• Add HorizontalPodAutoscaler resource class (#305)

Bug Fixes

• Prevent crash when STATSD_IMPLEMENTATION isn't set. (#3242)

0.20.4

Enhancements

• Don't consider pod preempting a failure (#317)

0.20.3

Enhancements

• Evictions are recoverable so prevent them from triggering fast failure detection (#293).
• Use YAML.safe_load over YAML.load_file (#295).

Bug Fixes

• Default rollout strategy is compatible required-rollout annotation (#289).

0.20.2

Enhancements

• Emit data dog events when deploys succeed, time out or fail (#292).

0.20.1

Bug Fixes

• Display a nice error instead of crashing when a YAML document is missing 'Kind' (#280)
• Prevent DaemonSet from succeeding before rollout finishes (#288)

Enhancements

• Merge multiple --bindings arguments, to allow a composite bindings map (multiple arguments or files)

0.20.0

Features

• Automatically add all Kubernetes namespace labels to StatsD tags (#278)

Bug Fixes

• Prevent calling sleep with a negative value (#273)
• Prevent no-op redeploys of bad code from hanging forever (#262)

Enhancements

• Improve output for rendering errors (#253)

0.19.0

Features

• Added --max-watch-seconds=seconds to kubernetes-restart and kubernetes-deploy. When set a timeout error is raised if it takes longer than seconds for any resource to deploy.
• Adds YAML and JSON file reference support to the kubernetes-deploy --bindings argument (#269)

Enhancements

• Prune resource quotas (#264)

Bug Fixes

• Update gemspec to reflect need for ActiveSupport >= 5.0(#270)

0.18.1

Enhancements

• Change the way the resource watcher fetches resources to make it more efficient for large deploys. Deploys with hundreds of resources are expected to see a measurable performance improvement from this change. (#251)

0.18.0

Features

• kubernetes-restart and kubernetes-deploy use exit code 70 when a deploy fails due to one or more resources failing to deploy in time. (#244)

Bug Fixes

• Handle deploying thousands of resources at a time, previously kubernetes-deploy would fail with Argument list too long - kubectl (Errno::E2BIG). (#257)

0.17.0

Enhancements

• Add the --cascade flag when we force replace a resource. (#250)

0.16.0

Important: This release changes the officially supported Kubernetes versions to v1.7 through v1.9. Other versions may continue to work, but we are no longer running our test suite against them.

Features

• Support partials to reduce duplication in yaml files (#207)

Bug Fixes

• Handle podless deamon sets properly (#242)

0.15.2

Enhancements

• Print warnings if kubernetes server version is not supported (#237).
• Possible via env var to disable fetching logs and/or events on deployment failure (#239).
• The kubernetes-deploy.shopify.io/required-rollout annotation now takes a percent (e.g. 90%) (#240).

0.15.1

Enhancements

• Fetch debug events and logs for failed resources in parallel (#238)

0.15.0

Bug Fixes

• None

Enhancements

• Support for cronjob resource (#206).
• Make it possible to override the tool's hard timeout for one specific resource via the kubernetes-deploy.shopify.io/timeout-override annotation (#232).
• Make it possible to modify how many replicas need to be updated and available before a deployment is considered successful via the kubernetes-deploy.shopify.io/required-rollout annotation (#208).

0.14.1

Bug Fixes

• Make deployments whose pods crash because of CreateContainerConfigError fail fast in 1.8+ too (they would previously time out).
• Fix crashes when deploying ExternalName services or services without selectors (#211)
• Predeploy ServiceAccount resources (#221)

Enhancements

• Make it possible to pass bindings (via the --bindings flag) for which the value contains commas or is a JSON encoded hash (#219)
• Support KUBECONFIG referencing multiple files (#222)

0.14.0

Bug Fixes

• Fix incorrect timeouts occasionally observed on deployments using progressDeadlineSeconds in Kubernetes <1.7.7

Enhancements

• Renamed KubernetesDeploy::Runner (which powers exe/kubernetes-deploy) to KubernetesDeploy::DeployTask. This increases consistency between our primary class names and avoids confusion with KubernetesDeploy::RunnerTask (which powers exe/kubernetes-run).
• Improved output related to timeouts. For deployments, both failure and timeout output now mentions the referenced replica set.
• Small improvements to the reliability of the success polling.
• EjsonSecretProvisioner no longer logs kubectl command output (which may contain secret data) when debug-level logging is enabled.

0.13.0

Features

• Added support for StatefulSets for kubernetes 1.7+ using RollingUpdate

Bug Fixes

• Explicitly require the minimum rest-client version required by kubeclient (#202)

Enhancements

• Begin official support for Kubernetes v1.8 (#198, #200)

0.12.12

Bug Fixes

• Fix an issue deploying Shopify's internal custom resources.

0.12.11

Bug Fixes

• Stop appending newlines to the base64-encoded values of secrets created from ejson. These extra newlines were preventing the ejson->k8s secret feature from working with v1.8 (#196).

0.12.10

Enhancement

• Log reason if deploy times out due to progressDeadlineSeconds being exceeded

0.12.9

Bug Fixes

• Retry discovering namespace and kubernetes context
• Expose real error during namespace discovery

0.12.8

Bug Fixes

• Force deployment to use its own hard timeout instead of relying on the replica set