Version 0.1.0

[arschles]

This is the first beta version of the KEDA HTTP Add-on! It's been a while since our last release, which was 0.0.1. Since then, we've made big improvements to nearly every area of this project.

If you'd like to get started right away, please see the walkthrough documentation for this release.

Otherwise, below is a list of some of the most significant changes in this release.

HTTPScaledObject changes

Note: there is a breaking change to the HTTPScaledObject spec field in this release. Please see the last bullet point of this section for more details

• The status field of HTTPScaledObjects is now automatically populated (by the operator) with more details on the progress of your deployment (Improve status conditions #47)
• You get more control over how your app is scaled, including specifying the minimum and maximum replicas (Add min and max replicas #85),
• The HTTP Add-on operator no longer controls your application's Deployment or Service resources. You have full control over creating, updating or removing your application components, and the HTTP Add-on won't touch them anymore (Not creating app deployments  #78)
  • This is a breaking change. Most old HTTPScaledObject spec fields will not work with this release

Logistics changes

• All container images for the HTTP Add-on are pushed to GitHub Container Registry now, rather than Docker Hub. Links are provided below:
  • Scaler on GH Container Registry
  • Operator on GH Container Registry
  • Interceptor on GH Container Registry
• Our container images are now based on the scratch base image (Change images to scratch #41), reducing the overall attack surface area of running HTTP Add-on pods
• The helm chart is now hosted in the same chart repository as the chart for KEDA Core. See the chart source at github.com/kedacore/charts/tree/master/http-add-on
• We've added significant test coverage (Beginning to write tests #43)

Local development environment changes

• The previous Makefile has been removed in favor of magefiles in Magefiles #89
  • This change allows us to provide HTTP Add-on developers a consistent, fast, and reliable experience across platforms
  • We're also now able to provide more complex build tasks, including building and pushing container images to GitHub Container Registry in parallel

Documentation changes

• We've done several major documentation improvements, including adding an FAQ (Adding an FAQ #71), outlining the scope of functionality of the HTTP Add-on (Document use cases #81), and use cases (Document use cases #81)
• We've also added a document ensuring that this project has a pointer to the kedacore-wide code of conduct (Adding Code of Conduct #178)

Thanks

This project is young at the moment, and we have a wonderful and growing community. Special thanks to @ajanth97 and @khaosdoctor for their contributions.

We have a lot of features pending in this project, and we welcome new contributors to help build them. We also have documentation to write, issues to fix, and plenty of other things to do to otherwise push the KEDA HTTP Add-on project forward.

If you're interested in contributing in any way, we are willing to help you get started. Please send a direct message to arschles in the Kubernetes slack group indicating your interest.

---

This discussion was created from the release Version 0.1.0.