Improper defaults in KubernetesClientBuildConfig #43474
Labels
Milestone
Comments
|
/cc @geoand (kubernetes), @iocanel (kubernetes), @radcortez (config) |
metacosm
added a commit
to metacosm/quarkus
that referenced
this issue
Sep 24, 2024
Fixes quarkusio#43474 Signed-off-by: Chris Laprun <[email protected]>
This was referenced Sep 24, 2024
metacosm
added a commit
to quarkiverse/quarkus-operator-sdk
that referenced
this issue
Sep 24, 2024
This should be removed when the underlying issue is fixed. See quarkusio/quarkus#43474 Signed-off-by: Chris Laprun <[email protected]>
metacosm
added a commit
to quarkiverse/quarkus-operator-sdk
that referenced
this issue
Sep 25, 2024
This should be removed when the underlying issue is fixed. See quarkusio/quarkus#43474 Signed-off-by: Chris Laprun <[email protected]>
metacosm
added a commit
to metacosm/quarkus
that referenced
this issue
Sep 25, 2024
Fixes quarkusio#43474 Signed-off-by: Chris Laprun <[email protected]>
metacosm
added a commit
to quarkiverse/quarkus-operator-sdk
that referenced
this issue
Sep 25, 2024
This should be removed when the underlying issue is fixed. See quarkusio/quarkus#43474 Signed-off-by: Chris Laprun <[email protected]>
|
This would be a good candidate for backporting, imo. |
mskacelik
pushed a commit
to mskacelik/quarkus
that referenced
this issue
Sep 27, 2024
Fixes quarkusio#43474 Signed-off-by: Chris Laprun <[email protected]>
gsmet
pushed a commit
to gsmet/quarkus
that referenced
this issue
Oct 21, 2024
Fixes quarkusio#43474 Signed-off-by: Chris Laprun <[email protected]> (cherry picked from commit 243b4d3)
2 tasks
bschuhmann
pushed a commit
to bschuhmann/quarkus
that referenced
this issue
Nov 16, 2024
Fixes quarkusio#43474 Signed-off-by: Chris Laprun <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
Not strictly a bug but rather an annoyance: the default values that are provided in
KubernetesClientBuildConfigare not up-to-date which leads to behavioral changes between a default configured client and one that's injected by Quarkus.Expected behavior
The defaults should be consistent with what users would expect when they're not using Quarkus
Actual behavior
The defaults do not match the current implementation anymore.
How to Reproduce?
No response
Output of
uname -aorverNo response
Output of
java -versionNo response
Quarkus version or git rev
No response
Build tool (ie. output of
mvnw --versionorgradlew --version)No response
Additional information
From a maintenance perspective, providing such defaults opens the door to the current issue where defaults are not in synch. The implementation is already set up to inherit defaults from the implementation so we should use that instead.
The text was updated successfully, but these errors were encountered: