2.14.0 backports 1 #28909
Merged
2.14.0 backports 1 #28909
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Fixes: quarkusio#28625 (cherry picked from commit 56b52b9)
Fix quarkusio#28738 (cherry picked from commit b773a33)
Fixes: quarkusio#28677 (cherry picked from commit f4fd3cf)
(cherry picked from commit 5f9a4cc)
(cherry picked from commit 111dfe5)
These changes also ensures that not duplicated ingress rules are generated.
#### Adding Ingress rules
To customize the default `host` and `path` properties of the generated Ingress resources, you need to apply the following configuration:
```
quarkus.kubernetes.ingress.expose=true
# To change the Ingress host. By default, it's empty.
quarkus.kubernetes.ingress.host=prod.svc.url
# To change the Ingress path of the generated Ingress rule. By default, it's "/".
quarkus.kubernetes.ports.http.path=/prod
```
This would generate the following Ingress resource:
```yaml
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
labels:
app.kubernetes.io/name: kubernetes-with-ingress
app.kubernetes.io/version: 0.1-SNAPSHOT
name: kubernetes-with-ingress
spec:
rules:
- host: prod.svc.url
http:
paths:
- backend:
service:
name: kubernetes-with-ingress
port:
name: http
path: /prod
pathType: Prefix
```
Additionally, you can also add new Ingress rules by adding the following configuration:
```
# Example to add a new rule
quarkus.kubernetes.ingress.rules.1.host=dev.svc.url
quarkus.kubernetes.ingress.rules.1.path=/dev
quarkus.kubernetes.ingress.rules.1.path-type=ImplementationSpecific
# by default, path type is Prefix
# Exmple to add a new rule that use another service binding
quarkus.kubernetes.ingress.rules.2.host=alt.svc.url
quarkus.kubernetes.ingress.rules.2.path=/ea
quarkus.kubernetes.ingress.rules.2.service-name=updated-service
quarkus.kubernetes.ingress.rules.2.service-port-name=tcpurl
```
This would generate the following Ingress resource:
```yaml
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
labels:
app.kubernetes.io/name: kubernetes-with-ingress
app.kubernetes.io/version: 0.1-SNAPSHOT
name: kubernetes-with-ingress
spec:
rules:
- host: prod.svc.url
http:
paths:
- backend:
service:
name: kubernetes-with-ingress
port:
name: http
path: /prod
pathType: Prefix
- host: dev.svc.url
http:
paths:
- backend:
service:
name: kubernetes-with-ingress
port:
name: http
path: /dev
pathType: ImplementationSpecific
- host: alt.svc.url
http:
paths:
- backend:
service:
name: updated-service
port:
name: tcpurl
path: /ea
pathType: Prefix
```
Fix quarkusio#28812
Fix quarkusio#26747
(cherry picked from commit 8cce3d5)
(cherry picked from commit b40e64d)
Users should always be encouraged to use the latest release of a feature release, i.e., prefer 22.3.1 over 22.3.0. Micro releases (called CPU releases in GraalVM) should not break compatibility, instead they should only bring bug fixes. As a result they should be considered safe to use. This change also enables referecing the version specific graalvm docs as discussed in https://github.com/quarkusio/quarkus/pull/28628/files#r996786908 (cherry picked from commit 8353a19)
Java 8 in JVM mode is no longer supported and the default native builder images are now Java 17 based. Furthermore, the minimum supported GraalVM version is now 22.2 so any reference to earlier versions is obsolete. (cherry picked from commit 4f2c4f2)
* Use major.minor version of GraalVM to pin links to the corresponding documentation * Replace links to the github repository's master branch with links to the published documentation for the corresponding GraalVM version (cherry picked from commit 4f852f2)
… pom The properties defining the GraalVM version are already located in different files. Moving these properties to docs/pom.xml avoids running all the CI jobs when altering them (which is the right thing to do as they only affect the documentation). (cherry picked from commit 080dc77)
We essentially make the first letter of every part an uppercase letter for consistence Part of quarkusio#13665 (cherry picked from commit 684f553)
Closes: quarkusio#13665 (cherry picked from commit d93345c)
- remove `@CheckedFragment`
- introduce `@CheckedTemplate#ignoreFragments()`
- change the syntax used to include a fragment; `{#include foo[bar] /}`
-> `{#include foo$bar /}`
- resolves quarkusio#28753
(cherry picked from commit 9668146)
The output format of a few commands has changed between Redis 5 and 6. This PR allows us to verify the compatibility with Redis 5, 6, and 7. Note that it's the best effort, and we do not intend full compatibility with Redis 5, only the main use cases. Typically, Redis Stack is only supported with Redis 7. (cherry picked from commit 112a397)
(cherry picked from commit 438d132)
…and @PreDestroy), and validate their signature. In this case, a DefinitionException is thrown, indicating that the method signature is invalid. Fix quarkusio#27591 according to the discussion. (cherry picked from commit cb2c0d5)
* Relocate GC logging FAQ info to native memory management . (cherry picked from commit 28da40c)
(cherry picked from commit 6b53eca)
(cherry picked from commit 47f4a1d)
quarkus-bot
bot
added
area/arc
quarkus-bot
bot
added
area/jakarta
area/kubernetes
area/maven
area/platform
This comment has been minimized.
This comment has been minimized.
For the metadata, this was done in https://github.com/quarkusio/quarkus/pull/28047/files (cherry picked from commit ae559d5)
(cherry picked from commit f19b0aa)
(cherry picked from commit 66e953a)
… client - Also use hyphenate on `@RestHeader` on client fields on bean params quarkusio#13665 - Added test for client bean param on fields, getters and regular parameters for good measure Fixes quarkusio#28782 (cherry picked from commit 368b496)
Closes: quarkusio#28863 (cherry picked from commit e928dc5)
Bumps [smallrye-common-bom](https://github.com/smallrye/smallrye-common) from 1.13.1 to 1.13.2. - [Release notes](https://github.com/smallrye/smallrye-common/releases) - [Commits](smallrye/smallrye-common@1.13.1...1.13.2) --- updated-dependencies: - dependency-name: io.smallrye.common:smallrye-common-bom dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <[email protected]> (cherry picked from commit 81fc1db)
…t failed to provide a resource (cherry picked from commit c6d299a)
(cherry picked from commit 3256d27)
(cherry picked from commit ff1aa6c)
With these changes, users can also manually append the parts of the form using the class `MultipartFormDataOutput` as: ```java import javax.ws.rs.GET; import javax.ws.rs.Path; import javax.ws.rs.Produces; import javax.ws.rs.core.MediaType; import org.jboss.resteasy.reactive.server.core.multipart.MultipartFormDataOutput; @path("multipart") public class Endpoint { @get @produces(MediaType.MULTIPART_FORM_DATA) @path("file") public MultipartFormDataOutput getFile() { MultipartFormDataOutput form = new MultipartFormDataOutput(); form.addFormData("person", new Person("John"), MediaType.APPLICATION_JSON_TYPE); form.addFormData("status", "a status", MediaType.TEXT_PLAIN_TYPE) .getHeaders().putSingle("extra-header", "extra-value"); return form; } } ``` Fix quarkusio#28631 This last approach allows you adding extra headers to the output part. (cherry picked from commit 6967fbc)
Before, we were using a ByteArrayOutputStream because some message writers are closing the original output stream when writing the entity (like JSON). The problem is that this approach needs the double of space (keeping the data in the bytearray output stream and then copy the data to the original output stream). With these changes, we are proxying the original output stream and preventing the message writers to not close the output stream (this was already being used in the JsonbMessageBodyWriter). Fix quarkusio#28920 (cherry picked from commit 25722b7)
(cherry picked from commit ee81686)
…bled (cherry picked from commit 2cc4313)
(cherry picked from commit af39006)
I didn't add any test to cover this change because it's easier to fix than to replicate the conditions to reproduce it in either the extension or an integration test than expected taking into account we have a reproducer. Still let me know if you want it to cover it and maybe I can add wiremock in the integration-tests/rest-client-reactive. Fix quarkusio#28922 (cherry picked from commit 1d074d6)
gsmet
force-pushed
the
2.14.0-backports-1
branch
from
f51c5ba to
b78106d
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Please don't merge, I will merge it myself.