oscerd commented on code in PR #27503:
URL: https://github.com/apache/camel/pull/27503#discussion_r4228441524
##########
docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_23.adoc:
##########
@@ -4766,3 +4766,25 @@ consumes `AiToolResult` and handles its variants
exhaustively — for example an
`AiToolResult.ExecutionError` — must add a branch for `AuthorizationDenied`
and relay its `message()` to the model as
a refusal (do not rethrow). The in-tree adapters (camel-openai,
camel-spring-ai-chat, camel-langchain4j-agent and the
MCP server bridge) already handle it.
+
+=== camel-kubernetes
Review Comment:
Moved — it now sits at `camel-4x-upgrade-guide-4_23.adoc:1879`, directly
after `=== camel-mongodb` and alongside `=== camel-hivemq` / `===
camel-debezium-mongodb`, exactly where the other `insecure:ssl`
reclassifications live.
One thing the rebase turned up that is worth flagging. `main` has since
added its own `=== camel-kubernetes` entry (the `kubernetes-configmaps`
developer console change), and git matched that heading against mine and
conflicted only the *bodies*. Resolving it the obvious way — keeping both sides
— would have filed my `trustCerts` text underneath main's configmaps-console
heading, silently merging two unrelated topics.
So I kept main's entry untouched and re-inserted mine with its own distinct
heading:
```
=== camel-kubernetes - trustCerts is marked insecure:ssl
```
The distinct title is deliberate rather than cosmetic: a second literal `===
camel-kubernetes` would generate a duplicate `#_camel_kubernetes` anchor id in
the same page and break the website link checker.
_Claude Code on behalf of @oscerd_
##########
components/camel-kubernetes/src/main/java/org/apache/camel/component/kubernetes/KubernetesConfiguration.java:
##########
@@ -75,7 +75,7 @@ public class KubernetesConfiguration implements Cloneable {
@UriParam(label = "security", security = "secret")
private String oauthToken;
- @UriParam(label = "security", security = "secret")
+ @UriParam(label = "security", security = "insecure:ssl", insecureValue =
"true")
Review Comment:
Done — the upgrade-guide entry is in, and it documents the
`camel.security.allowedProperties` escape hatch with a concrete
`camel.component.kubernetes-pods.trustCerts` example, as you asked. See the
thread on the guide for where it ended up after the rebase.
_Claude Code on behalf of @oscerd_
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
