-
Notifications
You must be signed in to change notification settings - Fork 1.6k
Announcement for release 1.27 #16725
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
😊 Welcome! This is either your first contribution to the Istio documentation repo, or
Thanks for contributing! Courtesy of your friendly welcome wagon. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Partial pass on release notes, will continue reviewing later.
content/en/news/releases/1.27.x/announcing-1.27/change-notes/index.md
Outdated
Show resolved
Hide resolved
content/en/news/releases/1.27.x/announcing-1.27/change-notes/index.md
Outdated
Show resolved
Hide resolved
content/en/news/releases/1.27.x/announcing-1.27/change-notes/index.md
Outdated
Show resolved
Hide resolved
content/en/news/releases/1.27.x/announcing-1.27/change-notes/index.md
Outdated
Show resolved
Hide resolved
content/en/news/releases/1.27.x/announcing-1.27/change-notes/index.md
Outdated
Show resolved
Hide resolved
content/en/news/releases/1.27.x/announcing-1.27/change-notes/index.md
Outdated
Show resolved
Hide resolved
content/en/news/releases/1.27.x/announcing-1.27/change-notes/index.md
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Finished first pass over the change notes.
content/en/news/releases/1.27.x/announcing-1.27/change-notes/index.md
Outdated
Show resolved
Hide resolved
content/en/news/releases/1.27.x/announcing-1.27/change-notes/index.md
Outdated
Show resolved
Hide resolved
content/en/news/releases/1.27.x/announcing-1.27/change-notes/index.md
Outdated
Show resolved
Hide resolved
content/en/news/releases/1.27.x/announcing-1.27/change-notes/index.md
Outdated
Show resolved
Hide resolved
content/en/news/releases/1.27.x/announcing-1.27/change-notes/index.md
Outdated
Show resolved
Hide resolved
content/en/news/releases/1.27.x/announcing-1.27/change-notes/index.md
Outdated
Show resolved
Hide resolved
content/en/news/releases/1.27.x/announcing-1.27/change-notes/index.md
Outdated
Show resolved
Hide resolved
content/en/news/releases/1.27.x/announcing-1.27/change-notes/index.md
Outdated
Show resolved
Hide resolved
content/en/news/releases/1.27.x/announcing-1.27/change-notes/index.md
Outdated
Show resolved
Hide resolved
content/en/news/releases/1.27.x/announcing-1.27/change-notes/index.md
Outdated
Show resolved
Hide resolved
|
||
- **Added** support for native `nftables` when using Istio sidecar mode. This update makes it possible to use `nftables` | ||
instead of iptables to manage network rules, offering more efficient approach to traffic redirection for pods and | ||
services. To enable the `nftables` mode, use `--set values.global.nativeNftables=true` at the time of installation. ([Issue #56487](https://github.com/istio/istio/issues/56487)) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we add a note here that only debug images currently support this mode?
PS: Following is the tracker for including the nftables-slim in distroless images - istio/istio#57237
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A note for future, that should be part of the release notes yaml in the PR.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry, forgot to sent this yesterday
content/en/news/releases/1.27.x/announcing-1.27/upgrade-notes/index.md
Outdated
Show resolved
Hide resolved
## Multiple certificate types support in Gateway | ||
|
||
Istio now supports configuring multiple certificate types (such as RSA and ECDSA) simultaneously in Gateway resources. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Classic Gateway or Kubernetes Gateway?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Both
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Added Add support for multiple server certificates in gateway (istio & gateway api)
it seems like to be both for the release notes.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yes. it is both
- **Added** certificate revocation list (CRL) support for plugged-in CAs, enabling Istio to watch for `ca-crl.pem` files and | ||
automatically distribute CRLs across all namespaces in the cluster. This enhancement allows | ||
proxies to validate and reject revoked certificates, strengthening the security posture of service mesh deployments | ||
using plugged-in CAs. ([Issue #56529](https://github.com/istio/istio/issues/56529)) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should this point to istio/istio#56308 where the design doc is referenced?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this's generated from the release notes in istio/istio, I'm fine if you want to highlight the design doc.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We also don't link to pull requests, only issues. It's best to put design docs in the issue.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There is no obvious issue; the issue linked is for something after the fact. 56529 didn't tell me anything; I had to work backwards to figure out what the thing was.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
At least, it linked to the implement PR, and there's a design in the PR description.
@istio/release-managers-1-27 Something I just ran into: after istio/istio#56048, using an older istioctl or helm chart version with new istio-cni images will cause ambient enablement to break completely because the defaults are set in the install mechanism. Maybe something to call out in release notes? Maybe it's too much, but it took me a while to debug so I figured I'd bring it up. Sidenote: we may want to consider patching the istio-cni code itself so that the default doesn't result in ambient being unusable...probably a good thing to target for a 1.27.1 release? |
I've run into the same but its a 100% invalid way to install Istio which has been broken for ~80% of versions (usually broken in different ways) so its not a new thing. I have also ran into this exact CNI issue and struggled to debug, though since I often pull |
- **Added** certificate revocation list (CRL) support for plugged-in CAs, enabling Istio to watch for `ca-crl.pem` files and | ||
automatically distribute CRLs across all namespaces in the cluster. This enhancement allows | ||
proxies to validate and reject revoked certificates, strengthening the security posture of service mesh deployments | ||
using plugged-in CAs. ([Issue #56529](https://github.com/istio/istio/issues/56529)) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There is no obvious issue; the issue linked is for something after the fact. 56529 didn't tell me anything; I had to work backwards to figure out what the thing was.
|
3e436e4
to
631aaa8
Compare
/test easycla |
@dhawton: The specified target(s) for
The following commands are available to trigger optional jobs:
Use
In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
/easycla |
what happen to |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Couple nits
content/en/news/releases/1.27.x/announcing-1.27/change-notes/index.md
Outdated
Show resolved
Hide resolved
content/en/news/releases/1.27.x/announcing-1.27/upgrade-notes/index.md
Outdated
Show resolved
Hide resolved
content/en/news/releases/1.27.x/announcing-1.27/upgrade-notes/index.md
Outdated
Show resolved
Hide resolved
content/en/news/releases/1.27.x/announcing-1.27/upgrade-notes/index.md
Outdated
Show resolved
Hide resolved
Nothing. That's still my primary GH email address. Not sure what error easycla is having, nothing has changed irt my GH account in several years. Seems to also not like a commit co-authored by Keith.. so easycla/GH issue maybe? or it's not us. |
it happen after I merged master, so I think it might not from our side. |
Ah yes.. the commit has "2 people and zirain" and the first of the "2 people" is an invalid zirain profile. So something isn't right in those commits. |
if you don't mind, let me merge them all into one commit to pass it? |
/easycla |
847b47f
to
3077597
Compare
No description provided.