Skip to content

2.2.0
Compare
Choose a tag to compare
@github-actions github-actions released this 04 May 07:24
· 10 commits to refs/heads/release-2.2 since this release
2.2.0
16d6352
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.

Not so long ago in a galaxy not so far away, there was a friendly kingdom of Kyma-land ruled by king Kyma the Wise. The king once said: “It is time to improve our kingdom so that we all can lead even happier lives”. As the king had never made an empty promise, he introduced many features, such as a complete setup of the Istio metrics, Istio upgrade to 1.13.2, overriding Function runtime image and improved Eventing backend custom resource (CR) status. Read more if you want to learn about other ideas the king came up with!

API Gateway

ORY stack deprecation note

Due to the growing demand for a closer integration with our Service Mesh Istio implementation, we decided to gradually switch from the current implementation behind Kyma API Gateway (ORY Hydra and ORY Oathkeeper) to Authentication and Authorization features that Istio provides out of the box. With this change, we introduce more options in terms of configuration, flexibility, and performance to our customers. Additionally, we want to keep the Kyma stack as lean as possible.

The changes will be introduced gradually. We plan to provide as much automated migration as possible to ensure the smooth growth of Kyma API Gateway. This is just initial information, no action is required.

CLI

Removed support for Kyma 1.x

As announced in the Kyma 2.0 release notes, starting from the version 2.2, Kyma CLI no longer supports Kyma 1.x versions. All the deprecated commands have been removed and are no longer available:

  • kyma install: Kyma 2.x equivalent is kyma deploy
  • kyma upgrade: Kyma 2.x equivalent is kyma deploy
  • kyma console: Kyma 2.x equivalent is kyma dashboard
  • kyma provision minikube: Kyma 2.x equivalent is kyma provision k3d

Eventing

Improved Eventing backend CR status

We have made the Eventing backend CR status more verbose. We've replaced two of the three booleans, publisherProxyReady and subscriptionControllerReady, with the Kubernetes conditions. The eventingReady boolean remains unchanged.

Observability

Improved documentation on monitoring limitations

We added a new section outlining the limits of the shipped monitoring stack running on the production profile with the default settings. Read Monitoring limitations for more information.

Cleanup of rules and dashboards

We've continued to clean up Prometheus rules and Grafana dashboards. Several rules for Kubernetes introduced by Kyma itself have been removed, as they overlapped with the community-based rules. With that, the monitoring chart is fully based on the rules provided by the community upstream chart. Also, one more Kubernetes-related Grafana dashboard called Kyma / Pods has been removed, as it overlapped with the existing dashboards.

Complete Istio metrics

The Istio metrics setup, coming with the Kyma monitoring feature, now follows the approach recommended by Istio and provides all Istio metrics as aggregations over workload. Read Observability Best Practices for more information.

Minor upgrade of Fluent Bit

The Fluent Bit log collector, included in the Kyma logging stack, has been updated to the 1.9 release series. It brings major improvements in stability and performance.

Minor upgrade of Kiali

Kiali has been upgraded to version 1.49 and is fully supporting Istio 1.13.

Serverless

Overrides for the Function runtime image

We've extended the definition of the Function CR. Now you can override the base image of the Serverless runtime with a custom Docker image.

You may need this feature if you want to build your Functions on top of a runtime with tooling that is not included in the default Alpine-based runtime (for example, the GCC compiler).

Remember that, if you use a custom base image for your Functions, you are responsible for scanning and assessing any potential risks related to commonly known vulnerabilities that are potentially exploitable.

There is a dedicated example defining a custom runtime and a tutorial explaining how to use it in your Functions.

Service Mesh

Revert to distroless Istio images provided by Istio

With the 2.2 Kyma release, both Istio control plane and data plane again use distroless images provided by Istio.

Istio upgraded to 1.13.2

We've upgraded Istio from 1.12.3 to 1.13.2. For more details on the introduced changes, read the official Istio 1.13.2 release notes.

2.2.0-rc1 (2022-04-28)

Application Connector

  • #14102 Prow approval flow is not used. OWNERS files are not needed. (@dekiel)
  • #14008 Bump Compass Runtime Agent (@franpog859)
  • #13837 Update OWNER files in application-connector to new guidelines (@koala7659)
  • #13810 Fix Application connector port names in services to comply with Isti… (@cnvergence)
  • #13571 Add correlation ID to requests in compass runtime agent (@krasish)
  • #13627 Change the commerce-mock version used in fast integration tests (@mvshao)

Serverless

Eventing

Security

Service Mesh

Installation

Monitoring

Logging

Tracing

  • #14102 Prow approval flow is not used. OWNERS files are not needed. (@dekiel)
  • #13820 updated alpine and debian base image for several images (@a-thaler)

Documentation

CI

Core and Supporting

Committers: 40

Assets 3