Skip to content

Releases: kyma-project/kyma

2.8.3

18 Nov 10:01
@github-actions github-actions
2.8.3
d5ccc12
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
Compare
Choose a tag to compare
2.8.3

Version 9 of Highlight.js has reached EOL and is no longer supported.
Please upgrade or ask whatever dependency you are using to upgrade.
highlightjs/highlight.js#2877

2.8.3 (2022-11-18)

Eventing

  • #16097 Bump images for updated EPP and NATS (@k15r)
  • #16095 remove explicit stream check from sending (@k15r)

Committers: 2

Assets 3
Loading

2.9.0-rc1

14 Nov 15:51
@github-actions github-actions
2.9.0-rc1
2f28123
Compare
Choose a tag to compare
2.9.0-rc1 Pre-release
Pre-release

2.9.0-rc1 (2022-11-14)

Api Gateway

Application Connector

Serverless

Eventing

Service Mesh

Monitoring

Logging

Tracing

  • #15960 [Telemetry Operator] - TracePipeline Secret rotation handling (@lindnerby)
  • #15744 Disable PSP and configure securityContext properly for observability pods (@a-thaler)

Documentation

CI

Committers: 37

Read more
Assets 3
Loading

2.8.2

07 Nov 16:12
@github-actions github-actions
2.8.2
792355d
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
Compare
Choose a tag to compare
2.8.2

While bears have started to seek the sanctuary of lairs, we are not slowing down. Here we are with Kyma 2.8.2 and the security fixes you will find useful.

Security

Istio upgraded to 1.15.3

Istio was upgraded to version 1.15.3. It improves robustness thanks to the bug fixes it contains. For more information about the changes, see the official Istio 1.15.3 release notes.

Changelog

2.8.2 (2022-11-07)

Application Connector

  • #16010 Bump AC and CRA images (@franpog859)
  • #16005 Update application-operator module dependency with latest version from branch release-2.8 (@koala7659)
  • #15993 Application Connector and compass runtime agent cherry pick with update go dependencies for application connector and compass-runtime-agent (@koala7659)

Serverless

Eventing

Security

Service Mesh

Committers: 6

Assets 3
Loading

2.8.1

25 Oct 13:13
@github-actions github-actions
2.8.1
5d9f4cc
Compare
Choose a tag to compare
2.8.1

2.8.1 (2022-10-25)

Eventing

  • #15885 Restore jetstreamEnabled flag for 2.8.x releases to prevent eventing issues (@mfaizanse)

Committers: 1

Assets 3
Loading

2.8.0

21 Oct 14:10
@github-actions github-actions
2.8.0
38cd14f
Compare
Choose a tag to compare
2.8.0

We've been working as busy bees to present to you Kyma 2.8. We packed this release with upgrades, updates, and improvements, as well as some changes to prepare the ground for the features to come. For example, we introduced support for response rewriting in Application Gateway, and improved Secret rotation for LogPipelines, but there's much more!

While we get back to beeing busy with what's next, you go and explore what we've prepared for you.

API Gateway

Exposing workloads in multiple Namespaces with one APIRule

This Kyma release comes with an update to the APIRule CR that lets you expose and secure services in multiple Namespaces. Now it’s possible to specify the service Namespace either on the spec.service level or individually for each service in spec.rules. This new field is optional. If you do not specify it, the default APIRule Namespace is used.

For more details, see the APIRule CR documentation.
Check out also our new tutorial on how to expose workloads in multiple Namespaces with a single APIRule definition.

Application Connectivity

Response rewriting in Application Gateway

From this release, Application Gateway in Kyma supports redirects for the HTTP requests in which the URL host remains unchanged.

With this functionality, the HTTP client has the option to resolve redirects within the scope of the same API.
If so configured, the HTTP client that originally called Application Gateway follows redirects through the Gateway, passing authorization, custom headers, URL parameters, and the body.

For more details, see Application Gateway details.

Status codes returned by Application Gateway

In this release, we also updated the HTTP status codes that Application Gateway returns in the following cases:

  • When the Application specified in the path does not exist.
  • When the Application, service or entry is not passed in the path.
  • When a call to target API times out.

For more details, see Status codes for errors returned by Application Gateway.

Observability

Jaeger

In preparation for the bigger changes planned in the Tracing area, we updated the Jaeger stack to version 1.37, and enabled OTLP support.

At the same time, the Serverless engine switched to OTLP as well, and is ready for the awesome future.

Monitoring

In this release, we also updated the Prometheus node-exporter to version 1.4.0, and kube-state-metrics to version 2.6.0.

For more details, see the release notes for node-exporter and kube-state-metrics.

Logging

Yet another update that we made in this release is bumping Fluent Bit to version 1.9.9.

We also improved Secret rotation support for LogPipelines. A rotated Secret is now detected instantly.

NOTE: Mind that with Kyma 2.6, the Fluent Bit part of the Logging component was replaced by the new Telemetry component. This Fluent Bit part will be removed with the next Kyma release. If you have not adopted the change yet, do so now.

Deprecation of Kiali

The Kyma Observability feature was shifted in the direction of integration and openness to enable enterprise-grade qualities based on external services.
See the blog post on Observability strategy for more details.
As a consequence, Kiali will be removed in Kyma 2.10. See the blog post on Kiali deprecation.

Worry not, though, as you can still integrate it on your own.
We've got you covered, and we've prepared a tutorial on how to install custom Kiali in Kyma.

Security

Istio upgraded to 1.15.0

In this Kyma release, Istio was upgraded to version 1.15.0.

For more details on the changes, read the official Istio 1.15.0 release notes.

Istio CNI plugin

Breaking changes

This Kyma version introduces the Istio CNI plugin. The plugin replaces the istio-init container, and it provides the same networking functionality, but it doesn't require Istio users to have elevated Kubernetes RBAC permission.

To learn more, read about the Istio CNI plugin.

If initContainers starting in a Pod with sidecar injection enabled need to have networking capabilities, you must follow one of the these migration guides:

  • Set the UID of the initContainer to 1337 using runAsUser. 1337 is the UID used by the sidecar proxy. The traffic sent by this UID is not captured by the Istio's iptables rule. Application container traffic is captured as usual.

  • Set the traffic.sidecar.istio.io/excludeOutboundIPRanges annotation to disable. It disables redirecting traffic to any CIDRs that the init containers communicate with.

  • Set the traffic.sidecar.istio.io/excludeOutboundPorts annotation to disable. It disables redirecting traffic to the specific outbound ports that the initContainers use.

Serverless

Serverless engine switched to OTLP

Following the changes in Observability and opening new OTLP-compliant endpoints in Jaeger, the Serverless engine now configures Functions to send trace data to this new endpoint.
Functions built before releasing Kyma 2.8 will continue sending trace data to the previous endpoint.

For more information, see the Environment variables in Serverless.

Changelog

2.8.0-rc2 (2022-10-19)

Eventing

Committers: 1

2.8.0-rc1 (2022-10-17)

Api Gateway

Application Connector

Serverless

Eventing

Read more
Assets 3
Loading

2.8.0-rc2

19 Oct 10:58
@github-actions github-actions
2.8.0-rc2
897167a
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
Compare
Choose a tag to compare
2.8.0-rc2 Pre-release
Pre-release

2.8.0-rc2 (2022-10-19)

Eventing

Committers: 1

2.8.0-rc1 (2022-10-17)

Api Gateway

Application Connector

Serverless

Eventing

Service Mesh

Monitoring

Logging

Tracing

Documentation

Committers: 35

Read more
Assets 3
Loading

2.7.3

19 Oct 10:56
@github-actions github-actions
2.7.3
69ff112
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
Compare
Choose a tag to compare
2.7.3

Eventing

NATS upgraded to 2.9

To improve stability of the bundled eventing solution, we upgraded the NATS server from version 2.8 to 2.9.

For more details on this version, see the official NATS 2.9 release notes.

Changelog

2.7.3 (2022-10-19)

Eventing

Committers: 1

Assets 3
Loading

2.8.0-rc1

17 Oct 14:43
@github-actions github-actions
2.8.0-rc1
ff48819
Compare
Choose a tag to compare
2.8.0-rc1 Pre-release
Pre-release

2.8.0-rc1 (2022-10-17)

Api Gateway

Application Connector

Serverless

Eventing

Service Mesh

Monitoring

Logging

Tracing

Documentation

Committers: 35

Read more
Assets 2
Loading

2.7.2

10 Oct 14:51
@github-actions github-actions
2.7.2
45d584a
Compare
Choose a tag to compare
2.7.2

2.7.2 (2022-10-10)

Monitoring

Logging

Committers: 2

Assets 3
Loading

2.7.1

26 Sep 09:52
@github-actions github-actions
2.7.1
a7c0a2e
Compare
Choose a tag to compare
2.7.1

API Gateway

In Kyma 2.6 we introduced a new version of the APIRule custom resource (CR) - v1beta1. Unfortunately, with this change we also introduced a bug. When an APIRule is created, it is created with certain related sub-resources, which are labeled with the version of this APIRule. These labels are used to fetch the sub-resources for the appropriate version when editing the APIRule. Unfortunately, due to improper adjustment of the labeling when introducing the new APIRule version, in Kyma 2.6, when the user edited an APIRule in version v1alpha1, sub-resources labeled with version v1beta1 were searched instead. Because they were not found, the system recognized them as missing and created those sub-resources in version v1beta1, which was not the desired behavior. As a result, any calls to the exposed workload returned the 5xx errors. This patch release fixes the problem.

For more details, see the GitHub issue.

TIP: See also Release Notes for Kyma 2.7.

Changelog

2.7.1 (2022-09-26)

Api Gateway

  • #15591 Fixing APIRule v1alpha1 sub-resources handling (@barchw)

2.7.0 (2022-09-22)

Application Connector

Documentation

Committers: 2

2.7.0-rc1 (2022-09-19)

Application Connector

  • #15507 Changing images of the components to the commit ones (@mvshao)
  • #15474 Connectivity Validator - change client_golang to 1.11.1 due to CVE in 1.11.0 (@mvshao)
  • #15421 Deletion of the dependence to opsfleet in Application Gateway tests (@mvshao)
  • #14912 Components test of central-application-validator component (@koala7659)
  • #15366 Remove replicas from autoscaled deployments in Application Connector (@janmedrek)
  • #15340 Increase resource requests/limits for Application Connector components (@janmedrek)
  • #15262 Add fixes to Application Connector tutorials' commands (@majakurcius)

Serverless

Eventing

Security

Monitoring

Logging

Tracing

Documentation

Read more
Assets 3
Loading