Skip to content

Version 0.3.0

Compare
Choose a tag to compare
@arschles arschles released this 26 Jan 23:33
· 266 commits to main since this release
84d97e4

This is the third beta release of the KEDA HTTP Addon. Please see the install documentation to get started.

The largest change in this release is that operators now have the option of running a single cluster-global installation. This means that an HTTP Addon installation (e.g. scaler, interceptor, and operator) can now be scoped either to one namespace, or the entire cluster. The latter case is called a cluster-global install. If you do want to run a cluster-global HTTP Addon, you must:

  1. Not run any other KEDA HTTP Addon installations, even if they are scoped to one namespace
  2. Also run a cluster-global installation of KEDA itself

Breaking changes

There are no backward-incompatible changes to HTTPScaledObjects. However, there is a breaking change to the internal URL routing table. To overcome this, please delete your HTTP Addon installation (using helm delete if you're using the Helm chart) and re-install it at the 0.3.0 version.

Other significant changes

While the cluster-global feature is the biggest in this release, we have made several internal improvements such as:

  • Using the Kubernetes client library's informer framework in #326 (thanks to @tpiperatgod)
  • The ability to restore the target Deployment to its original replica count after deleting the associated HTTPScaledObject in #339 (thanks to @tpiperatgod)
  • Compiling operator, interceptor and scaler with the SHA of the source code they were built with, and adding an HTTP endpoint to each process's admin server to output this information in #377 (thanks to @asw101)
  • Returning a custom header for all requests that triggered a "cold start" (i.e. scaling up from 0 replicas) in #366 (thanks to @asw101)

What's Changed

  • Bump k8s.io/api from 0.22.2 to 0.22.3 by @dependabot in #307
  • Bump sigs.k8s.io/controller-runtime from 0.10.1 to 0.10.3 by @dependabot in #317
  • Updating the release process document with correct order of operations by @arschles in #327
  • Bump k8s.io/apimachinery from 0.22.3 to 0.22.4 by @dependabot in #328
  • Bump k8s.io/client-go from 0.22.2 to 0.22.4 by @dependabot in #329
  • Bump google.golang.org/grpc from 1.41.0 to 1.42.0 by @dependabot in #312
  • Add configMap informer by @tpiperatgod in #326
  • Restore target to original replica count after deleting httpscaledobject resource. by @tpiperatgod in #339
  • Upgrading images to use Go 1.17.2 by @arschles in #349
  • Adding documentation for how to issue curl requests by @arschles in #347
  • chore: Allow blank issues by @tomkerkhove in #352
  • Bump github.com/magefile/mage from 1.11.0 to 1.12.1 by @dependabot in #360
  • Bump google.golang.org/grpc from 1.42.0 to 1.43.0 by @dependabot in #358
  • converting bug report issue template to a form issue by @arschles in #363
  • Allowing cluster-global operation by @arschles in #269
  • Return custom header when request was returned from a cold start by @asw101 in #366
  • Updating dependencies by @arschles in #348
  • Bump go.uber.org/zap from 1.19.1 to 1.20.0 by @dependabot in #362
  • Bump github.com/go-logr/zapr from 0.4.0 to 1.2.2 by @dependabot in #357
  • Bump k8s.io/apimachinery from 0.23.1 to 0.23.2 by @dependabot in #376
  • Bump k8s.io/client-go from 0.23.1 to 0.23.2 by @dependabot in #375
  • Compile binaries and docker images with git SHA by @asw101 in #377
  • Bump github.com/onsi/gomega from 1.17.0 to 1.18.0 by @dependabot in #378
  • Configure WhiteSource Bolt for GitHub by @whitesource-bolt-for-github in #379
  • adding targetPendingRequests to the xkcd helm chart by @arschles in #373
  • fixing targetPendingRequests in the HTTPScaledObject v0.2.0 documenta… by @arschles in #372

New Contributors

  • @tpiperatgod made their first contribution in #326
  • @asw101 made their first contribution in #366
  • @whitesource-bolt-for-github made their first contribution in #379

Full Changelog: v0.2.0...v0.3.0