Skip to content

feat: expose publishNotReadyAddresses for broker services (#244)#1

Open
gomitrah wants to merge 2 commits into
masterfrom
feat/expose-publish-not-ready-addresses
Open

feat: expose publishNotReadyAddresses for broker services (#244)#1
gomitrah wants to merge 2 commits into
masterfrom
feat/expose-publish-not-ready-addresses

Conversation

@gomitrah

Copy link
Copy Markdown
Owner

Description

Adds a publishNotReadyAddresses field to the KafkaCluster CRD spec and propagates it to the
non-headless broker Services created by the operator: the per-broker Services (kafka-{id}) and
kafka-all-broker.

Type of Change

  • Bug Fix
  • New Feature
  • Breaking Change
  • Refactor
  • Documentation
  • Other (please describe)

Checklist

  • I have read the contributing guidelines
  • Existing issues have been referenced (where applicable)
  • I have verified this change is not present in other open pull requests
  • Functionality is documented
  • All code style checks pass
  • New code contribution is covered by automated tests
  • All new and existing tests pass

@gomitrah gomitrah closed this Jul 13, 2026
@gomitrah gomitrah reopened this Jul 13, 2026
@gomitrah
gomitrah force-pushed the feat/expose-publish-not-ready-addresses branch from a4d324a to fd22b43 Compare July 15, 2026 06:51
amuraru and others added 2 commits July 16, 2026 22:42
* chore(e2e): reduce log noise from kubectl output

Terratest echoes every stdout line of the kubectl commands it runs. Two
spots dominated the e2e log volume:

- listK8sResourceKinds dumped ~100+ api-resource names per call, twice
  per cluster snapshot.
- getBrokerConfigMapLogDirs dumped the full broker-config ConfigMap for
  all 3 brokers on every multi-disk-removal poll iteration.

Both now use the existing runKubectlSilent bypass. The multi-disk poller
additionally logs only the parsed log.dirs, which is all it inspects.

Also removes the dead setupReducedLogging(): its TEST_LOG_LEVEL /
KUBECTL_* env vars have no effect on terratest v1.0.1's logger, which is
why the line-dumping persisted.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

* fix(e2e): trim trailing newline in listK8sResourceKinds output

runKubectlSilent uses cmd.Output(), which preserves kubectl's trailing
newline (terratest's runner stripped it). listK8sResourceKinds split on
"\n" without trimming, producing an empty-string kind element that got
joined into the `kubectl get` args during cluster snapshotting:

  error: the server doesn't have a resource type ""

TrimRight the trailing newline before splitting, matching getK8sResources
and getK8sResourcesQuiet.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

* fix(e2e): harden listK8sCRDs output parsing

listK8sCRDs split kubectl output on "\n" without trimming the trailing
newline and without dropping warning lines - the same latent bug fixed
in listK8sResourceKinds. It currently uses terratest's runner (which
strips the trailing newline) so it isn't broken today, but it would
break the moment it's switched to runKubectlSilent.

TrimRight the trailing newline, guard empty output, and run
kubectlRemoveWarnings - consistent with getK8sResources and
getK8sResourcesQuiet.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@gomitrah
gomitrah force-pushed the feat/expose-publish-not-ready-addresses branch from fd22b43 to a85e688 Compare July 17, 2026 08:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants