v1 blog post #70
v1 blog post #70
Conversation
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: jasonmadigan The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
✅ Deploy Preview for relaxed-faloodeh-7fa6f1 ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
|
@maleck13 would appreciate your eyes - in particular if there's any other key release highlight that I've missed (I just went by memory/changelogs) @david-martin too |
|
Very nice. |
jasonmadigan
force-pushed
the
kuadrant-v1
branch
from
f5afe97 to
6b4bef1
Compare
jasonmadigan
force-pushed
the
kuadrant-v1
branch
2 times, most recently
from
17deeaf to
049cda8
Compare
src/blog/kuadrant-v1.md
Outdated
|
|
||
| ### What's new in v1? | ||
|
|
||
| There are too many features and bug fixes to mention (although you are welcome to peruse our [release changelogs](https://github.com/Kuadrant/kuadrant-operator/releases/tag/v1.0.0)). Here are some highlights: |
There was a problem hiding this comment.
Given that this is the 1.0 release, this feels like a HUGE missed opportunity. You'll never have the chance to advertise these features again. Take a look at Kubernetes release blogs for an example of how you should doc features for a major release: https://kubernetes.io/blog/2024/08/13/kubernetes-v1-31-release/
There was a problem hiding this comment.
Yeah I think that's fair, and I've always liked how Kubernetes and other projects highlight big ticket features. Will have a go at expanding this notes set a bit to highlight new features better, with links off to further ref material
src/blog/kuadrant-v1.md
Outdated
| |---------------------|---------------------------------------------------------------------------------------------------| | ||
| | Authorino Operator | [v0.16.0](https://github.com/Kuadrant/authorino-operator/releases/tag/v0.16.0) | | ||
| | Limitador Operator | [v0.12.1](https://github.com/Kuadrant/limitador-operator/releases/tag/v0.12.1) | | ||
| | DNS Operator | [v0.12.0](https://github.com/Kuadrant/dns-operator/releases/tag/v0.12.0) | | ||
| | WASM Shim | [v0.8.1](https://github.com/Kuadrant/wasm-shim/releases/tag/v0.8.1) | | ||
| | Console Plugin | [v0.0.14](https://github.com/Kuadrant/console-plugin/releases/tag/v0.0.14) | |
There was a problem hiding this comment.
If none of these operators are 1.0, how is this the Kuadrant 1.0 release?
There was a problem hiding this comment.
This is a fair question. One we will no doubt debate further over the next few releases. The Kuadrant Opertor is v1 and its APIs are v1. These components are its dependencies that are also part of the kuadrant org. The v1 release signifies the kuadrant policy APIs and the kuadrant operator as being stable (RateLimitPolicy, DNSPolicy, TLSPolicy and AuthPolicy) we wont break these APIs. If one of the dependencies has a change in their API, the kuadrant-opertor and the kuadrant community will be responsible for ensuring we handle that change without breaking the external v1 policy APIs.
jasonmadigan
force-pushed
the
kuadrant-v1
branch
from
049cda8 to
db88328
Compare
Signed-off-by: Jason Madigan <[email protected]>
jasonmadigan
force-pushed
the
kuadrant-v1
branch
2 times, most recently
from
4ea5d33 to
a62b87d
Compare
Signed-off-by: Jason Madigan <[email protected]>
|
/hold |
jasonmadigan
force-pushed
the
kuadrant-v1
branch
2 times, most recently
from
1f0bfa4 to
fbdfd55
Compare
|
@maleck13 another tech sanity check would be welcome |
Signed-off-by: Jason Madigan <[email protected]>
jasonmadigan
force-pushed
the
kuadrant-v1
branch
from
fbdfd55 to
be212dd
Compare
|
/unhold |
Draft v1 blog post