Skip to content

[chore][pkg/kafka/configkafka] resolve_canonical_bootstrap_servers_only is ignored for franz-go#45319

Closed
carsonip wants to merge 2 commits intoopen-telemetry:mainfrom
carsonip:canonical-bootstrap
Closed

[chore][pkg/kafka/configkafka] resolve_canonical_bootstrap_servers_only is ignored for franz-go#45319
carsonip wants to merge 2 commits intoopen-telemetry:mainfrom
carsonip:canonical-bootstrap

Conversation

@carsonip
Copy link
Copy Markdown
Contributor

@carsonip carsonip commented Jan 9, 2026

Description

Update docs and comment to state that franz-go does not support resolve_canonical_bootstrap_servers_only

Link to tracking issue

Testing

Documentation

@carsonip carsonip changed the title [chore] configkafka: resolve_canonical_bootstrap_servers_only is ignored for franz-go [chore][pkg/kafka/configkafka] resolve_canonical_bootstrap_servers_only is ignored for franz-go Jan 9, 2026
@paulojmdias
Copy link
Copy Markdown
Member

paulojmdias commented Jan 9, 2026

@carsonip Thanks for your PR.

Sarama was completely removed from those packages, if this parameter is unused in franz-go, we should completely remove it. WDYT ?

I could also check what is needed for franz-go support it

@carsonip
Copy link
Copy Markdown
Contributor Author

carsonip commented Jan 9, 2026

Sarama was completely removed from those packages

Thanks for pointing that out. I was not aware. Then we'll need to follow the deprecation process to clear out sarama-specific config. But in this resolve_canonical_bootstrap_servers_only case, if we manage to either contribute to franz-go or build this into configkafka, a deprecation won't be needed. Let me put this PR into draft and think about it.

@carsonip carsonip marked this pull request as draft January 9, 2026 23:52
@axw
Copy link
Copy Markdown
Contributor

axw commented Jan 12, 2026

Looks like franz-go doesn't directly support this, but enables it by allowing you to inject a Dialer. Relevant KIPs:

OTOH nobody has raised any fuss about the config not working since we switched to franz-go... 🤷‍♂️

Maybe we deprecated and remove resolve_canonical_bootstrap_servers_only, and on request we could add client_dns_lookup, like client.dns.lookup specified in the KIPs?

@paulojmdias
Copy link
Copy Markdown
Member

Maybe we deprecated and remove resolve_canonical_bootstrap_servers_only, and on request we could add client_dns_lookup, like client.dns.lookup specified in the KIPs?

I'm ok with this approach. I think it is better to support client.dns.lookup with their supported values instead of supporting only the resolve_canonical_bootstrap_servers_only.

@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Feb 2, 2026

This PR was marked stale due to lack of activity. It will be closed in 14 days.

@github-actions github-actions Bot added the Stale label Feb 2, 2026
@github-actions
Copy link
Copy Markdown
Contributor

Closed as inactive. Feel free to reopen if this PR is still being worked on.

@github-actions github-actions Bot closed this Feb 16, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants