|
| 1 | +[id="serverless-rn-1-19-0_{context}"] |
| 2 | += Release Notes for Red Hat {ServerlessProductName} 1.19.0 |
| 3 | + |
| 4 | +[id="new-features-1-19-0_{context}"] |
| 5 | +== New features |
| 6 | + |
| 7 | +* {ServerlessProductName} now uses Knative Serving 0.25. |
| 8 | +* {ServerlessProductName} now uses Knative Eventing 0.25. |
| 9 | +* {ServerlessProductName} now uses Kourier 0.25. |
| 10 | +* {ServerlessProductName} now uses Knative `kn` CLI 0.25. |
| 11 | +* {ServerlessProductName} now uses Knative Kafka 0.25. |
| 12 | +* The `kn func` CLI plug-in now uses `func` 0.19. |
| 13 | + |
| 14 | +* The `KafkaBinding` API is deprecated in {ServerlessProductName} 1.19.0 and will be removed in a future release. |
| 15 | + |
| 16 | +* HTTPS redirection is now supported and can be configured either globally for a cluster or per each Knative service. |
| 17 | + |
| 18 | +[id="fixed-issues-1-19-0_{context}"] |
| 19 | +== Fixed issues |
| 20 | + |
| 21 | +* In previous releases, the Kafka channel dispatcher waited only for the local commit to succeed before responding, which might have caused lost events in the case of an Apache Kafka node failure. The Kafka channel dispatcher now waits for all in-sync replicas to commit before responding. |
| 22 | + |
| 23 | +[id="known-issues-1-19-0_{context}"] |
| 24 | +== Known issues |
| 25 | + |
| 26 | +* In `func` version 0.19, some runtimes might be unable to build a function by using podman. You might see an error message similar to the following: |
| 27 | ++ |
| 28 | +[source,terminal] |
| 29 | +---- |
| 30 | +ERROR: failed to image: error during connect: Get "http://%2Fvar%2Frun%2Fdocker.sock/v1.40/info": EOF |
| 31 | +---- |
| 32 | ++ |
| 33 | +** The following workaround exists for this issue: |
| 34 | + |
| 35 | +.. Update the podman service by adding `--time=0` to the service `ExecStart` definition: |
| 36 | ++ |
| 37 | +.Example service configuration |
| 38 | +[source,terminal] |
| 39 | +---- |
| 40 | +ExecStart=/usr/bin/podman $LOGGING system service --time=0 |
| 41 | +---- |
| 42 | +.. Restart the podman service by running the following commands: |
| 43 | ++ |
| 44 | +[source,terminal] |
| 45 | +---- |
| 46 | +$ systemctl --user daemon-reload |
| 47 | +---- |
| 48 | ++ |
| 49 | +[source,terminal] |
| 50 | +---- |
| 51 | +$ systemctl restart --user podman.socket |
| 52 | +---- |
| 53 | + |
| 54 | +** Alternatively, you can expose the podman API by using TCP: |
| 55 | ++ |
| 56 | +[source,terminal] |
| 57 | +---- |
| 58 | +$ podman system service --time=0 tcp:127.0.0.1:5534 & |
| 59 | +export DOCKER_HOST=tcp://127.0.0.1:5534 |
| 60 | +---- |
0 commit comments