...
spec:
config:
network:
defaultExternalScheme: "http"
...
For an overview of OpenShift Serverless functionality, see Getting started with OpenShift Serverless.
|
OpenShift Serverless is based on the open source Knative project. For details about the latest Knative component releases, see the Knative blog. |
The OpenShift Serverless Operator automatically upgrades older resources that use deprecated versions of APIs to use the latest version.
For example, if you have created resources on your cluster that use older versions of the ApiServerSource API, such as v1beta1, the OpenShift Serverless Operator automatically updates these resources to use the v1 version of the API when this is available and the v1beta1 version is deprecated.
After they have been deprecated, older versions of APIs might be removed in any upcoming release. Using deprecated versions of APIs does not cause resources to fail. However, if you try to use a version of an API that has been removed, it will cause resources to fail. Ensure that your manifests are updated to use the latest version to avoid issues.
OpenShift Serverless now uses Knative Serving 0.23.0.
OpenShift Serverless now uses Knative Eventing 0.23.0.
OpenShift Serverless now uses Kourier 0.23.0.
OpenShift Serverless now uses Knative kn CLI 0.23.0.
OpenShift Serverless now uses Knative Kafka 0.23.0.
The kn func CLI plug-in now uses func 0.17.0.
In the upcoming OpenShift Serverless 1.19.0 release, the URL scheme of external routes will default to HTTPS for enhanced security.
If you do not want this change to apply for your workloads, you can override the default setting before upgrading to 1.19.0, by adding the following YAML to your KnativeServing custom resource definition (CRD):
...
spec:
config:
network:
defaultExternalScheme: "http"
...mTLS functionality is now Generally Available (GA).
TypeScript templates are now available when you create a function using kn func.
Changes to API versions in Knative Eventing 0.23.0:
The v1alpha1 version of the KafkaChannel API, which was deprecated in OpenShift Serverless version 1.14.0, has been removed. If the ChannelTemplateSpec parameters of your config maps contain references to this older version, you must update this part of the spec to use the correct API version.
If you try to use an older version of the Knative kn CLI with a newer OpenShift Serverless release, the API is not found and an error occurs.
For example, if you use the 1.16.0 release of the kn CLI, which uses version 0.22.0, with the 1.17.0 OpenShift Serverless release, which uses the 0.23.0 versions of the Knative Serving and Knative Eventing APIs, the CLI does not work because it continues to look for the outdated 0.22.0 API versions.
Ensure that you are using the latest kn CLI version for your OpenShift Serverless release to avoid issues.
Kafka channel metrics are not monitored or shown in the corresponding web console dashboard in this release. This is due to a breaking change in the Kafka dispatcher reconciling process.
If you create a new subscription for a Kafka channel, or a new Kafka source, there might be a delay in the Kafka data plane becoming ready to dispatch messages after the newly created subscription or sink reports a ready status.
As a result, messages that are sent during the time which the data plane is not reporting a ready status might not be delivered to the subscriber or sink.
For more information about this issue and possible workarounds, see Knowledge Article #6343981.
The Camel-K 1.4 release is not compatible with OpenShift Serverless version 1.17.0. This is because Camel-K 1.4 uses APIs that were removed in Knative version 0.23.0. There is currently no workaround available for this issue. If you need to use Camel-K 1.4 with OpenShift Serverless, do not upgrade to OpenShift Serverless version 1.17.0.
OpenShift Serverless now uses Knative Serving 0.22.0.
OpenShift Serverless now uses Knative Eventing 0.22.0.
OpenShift Serverless now uses Kourier 0.22.0.
OpenShift Serverless now uses Knative kn CLI 0.22.0.
OpenShift Serverless now uses Knative Kafka 0.22.0.
The kn func CLI plug-in now uses func 0.16.0.
The kn func emit command has been added to the functions kn plug-in. You can use this command to send events to test locally deployed functions.
You must upgrade OpenShift Container Platform to version 4.6.30, 4.7.11, or higher before upgrading to OpenShift Serverless 1.16.0.
The AMQ Streams Operator might prevent the installation or upgrade of the OpenShift Serverless Operator. If this happens, the following error is thrown by Operator Lifecycle Manager (OLM):
WARNING: found multiple channel heads: [amqstreams.v1.7.2 amqstreams.v1.6.2], please check the `replaces`/`skipRange` fields of the operator bundles.You can fix this issue by uninstalling the AMQ Streams Operator before installing or upgrading the OpenShift Serverless Operator. You can then reinstall the AMQ Streams Operator.
If Service Mesh is enabled with mTLS, metrics for Knative Serving are disabled by default because Service Mesh prevents Prometheus from scraping metrics.
If you want to enable Knative Serving metrics for use with Service Mesh and mTLS, you must complete the following steps:
Specify prometheus as the metrics.backend-destination in the observability spec of the Knative Serving custom resource (CR):
apiVersion: operator.knative.dev/v1alpha1
kind: KnativeServing
metadata:
name: knative-serving
spec:
config:
observability:
metrics.backend-destination: "prometheus"This step prevents metrics from being disabled by default.
Apply the following network policy to allow traffic from the Prometheus namespace:
apiVersion: networking.k8s.io/v1
kind: NetworkPolicy
metadata:
name: allow-from-openshift-monitoring-ns
namespace: knative-serving
spec:
ingress:
- from:
- namespaceSelector:
matchLabels:
name: "openshift-monitoring"
podSelector: {}
policyTypes:
- IngressModify and reapply the default Service Mesh control plane in the istio-system namespace, so that it includes the following spec:
spec:
proxy:
networking:
trafficControl:
inbound:
excludedPorts:
- 8444If you deploy Service Mesh CRs with the Istio ingress enabled, you might see the following warning in the istio-ingressgateway pod:
2021-05-02T12:56:17.700398Z warning envoy config [external/envoy/source/common/config/grpc_subscription_impl.cc:101] gRPC config for type.googleapis.com/envoy.api.v2.Listener rejected: Error adding/updating listener(s) 0.0.0.0_8081: duplicate listener 0.0.0.0_8081 foundYour Knative services might also not be accessible.
You can use the following workaround to fix this issue by recreating the knative-local-gateway service:
Delete the existing knative-local-gateway service in the istio-system namespace:
$ oc delete services -n istio-system knative-local-gatewayCreate and apply a knative-local-gateway service that contains the following YAML:
apiVersion: v1
kind: Service
metadata:
name: knative-local-gateway
namespace: istio-system
labels:
experimental.istio.io/disable-gateway-port-translation: "true"
spec:
type: ClusterIP
selector:
istio: ingressgateway
ports:
- name: http2
port: 80
targetPort: 8081If you have 1000 Knative services on a cluster, and then perform a reinstall or upgrade of Knative Serving, there is a delay when you create the first new service after the KnativeServing custom resource definition (CRD) becomes Ready.
The 3scale-kourier-control service reconciles all previously existing Knative services before processing the creation of a new service, which causes the new service to spend approximately 800 seconds in an IngressNotConfigured or Unknown state before the state updates to Ready.
If you create a new subscription for a Kafka channel, or a new Kafka source, there might be a delay in the Kafka data plane becoming ready to dispatch messages after the newly created subscription or sink reports a ready status.
As a result, messages that are sent during the time which the data plane is not reporting a ready status might not be delivered to the subscriber or sink.
For more information about this issue and possible workarounds, see Knowledge Article #6343981.
OpenShift Serverless now uses Knative Serving 0.21.0.
OpenShift Serverless now uses Knative Eventing 0.21.0.
OpenShift Serverless now uses Kourier 0.21.0.
OpenShift Serverless now uses Knative kn CLI 0.21.0.
OpenShift Serverless now uses Knative Kafka 0.21.1.
OpenShift Serverless Functions is now available as a Technology Preview.
|
The |
If you create a new subscription for a Kafka channel, or a new Kafka source, there might be a delay in the Kafka data plane becoming ready to dispatch messages after the newly created subscription or sink reports a ready status.
As a result, messages that are sent during the time which the data plane is not reporting a ready status might not be delivered to the subscriber or sink.
For more information about this issue and possible workarounds, see Knowledge Article #6343981.
OpenShift Serverless now uses Knative Serving 0.20.0.
OpenShift Serverless uses Knative Eventing 0.20.0.
OpenShift Serverless now uses Kourier 0.20.0.
OpenShift Serverless now uses Knative kn CLI 0.20.0.
OpenShift Serverless now uses Knative Kafka 0.20.0.
Knative Kafka on OpenShift Serverless is now Generally Available (GA).
|
Only the |
The Operator channel for installing and upgrading OpenShift Serverless has been updated to stable for OpenShift Container Platform 4.6 and newer versions.
OpenShift Serverless is now supported on IBM Power Systems, IBM Z, and LinuxONE, except for the following features, which are not yet supported:
Knative Kafka functionality.
OpenShift Serverless Functions developer preview.
Subscriptions for the Kafka channel sometimes fail to become marked as READY and remain in the SubscriptionNotMarkedReadyByChannel state. You can fix this by restarting the dispatcher for the Kafka channel.
If you create a new subscription for a Kafka channel, or a new Kafka source, there might be a delay in the Kafka data plane becoming ready to dispatch messages after the newly created subscription or sink reports a ready status.
As a result, messages that are sent during the time which the data plane is not reporting a ready status might not be delivered to the subscriber or sink.
For more information about this issue and possible workarounds, see Knowledge Article #6343981.
OpenShift Serverless now uses Knative Serving 0.19.0.
OpenShift Serverless uses Knative Eventing 0.19.2.
OpenShift Serverless now uses Kourier 0.19.0.
OpenShift Serverless now uses Knative kn CLI 0.19.1.
OpenShift Serverless now uses Knative Kafka 0.19.1.
A DomainMapping custom resource (CR) has been added to OpenShift Serverless to enable users to map a custom domain name to a Knative Service. See the Knative documentation on Creating a mapping between a custom domain name and a Knative Service.
In Knative Serving 0.19.0, v1alpha1 and v1beta1 versions of the Service, Route, Configuration, and Revision resources have been removed. The OpenShift Serverless Operator automatically upgrades older resources to v1, so no user action is required.
|
New resources must not be created as |
OpenShift Serverless now uses Knative Serving 0.18.2.
OpenShift Serverless uses Knative Eventing 0.18.6.
OpenShift Serverless now uses Kourier 0.18.0.
OpenShift Serverless now uses Knative kn CLI 0.18.4.
OpenShift Serverless now uses Knative Kafka 0.18.0.
In previous versions, if you used a ping source with OpenShift Serverless, after you uninstalled and deleted all other Knative Eventing components, the pingsource-jobrunner deployment was not deleted. This issue is now fixed, and the pingsource-jobrunner deployment has been renamed to pingsource-mt-adapter.
In previous versions, deleting a sink before you delete the SinkBinding resource connected to it caused the resource deletion to hang. This issue is now fixed.
Knative Eventing on OpenShift Serverless is now Generally Available (GA).
Knative Kafka features such as Kafka channel and Kafka event source are now available as a Technology Preview on OpenShift Serverless. Kafka integration is delivered through the OpenShift Serverless Operator and does not require a separate community Operator installation.
OpenShift Serverless Functions is now delivered as a Developer Preview through the standard Knative kn CLI installation. This feature is not yet supported by Red Hat for production deployments, but can be used for development and testing. For more information about using OpenShift Serverless Functions through the kn func CLI, see the OpenShift Serverless Functions Developer Preview documentation.
OpenShift Serverless now uses Knative Serving 0.17.3.
OpenShift Serverless uses Knative Eventing 0.17.2.
OpenShift Serverless now uses Kourier 0.17.0.
OpenShift Serverless now uses Knative kn CLI 0.17.3.
OpenShift Serverless now uses Knative Kafka 0.17.1.
When the horizontal pod autoscaler (HPA) scales up the broker-ingress pod, the imc-dispatcher pod sometimes fails to forward replies. This is because the new broker-ingress pods are Ready before accepting connections, because they lack a readiness probe. If you are using HPA autoscaling and do not want to scale the broker-ingress pod manually, you must configure retries in the Broker.Spec.Delivery.
Using the eventing.knative.dev/scope: namespace annotation with Kafka channels is not supported.
OpenShift Serverless now uses Knative Operator 0.16.0.
OpenShift Serverless now uses Knative Serving 0.16.0.
OpenShift Serverless uses Knative Eventing 0.16.0.
OpenShift Serverless now uses Kourier 0.16.0.
OpenShift Serverless now uses Knative kn CLI 0.16.1.
The annotation knative-eventing-injection=enabled that was previously used to label namespaces for broker creation is now deprecated. The new annotation is eventing.knative.dev/injection=enabled.
Multi-container support is now available on Knative as a Technology Preview feature. You can enable multi-container support in the config-features config map. For more information, see the Knative documentation.
In previous releases, Knative Serving had a fixed, minimum CPU request of 25m for queue-proxy. If your cluster had any value set that conflicted with this, for example, if you had set a minimum CPU request for defaultRequest of more than 25m, the Knative service failed to deploy. This issue is fixed in 1.10.0.