Skip to content

fix: propagate user-supplied altNames.ipAddresses to certificates#393

Open
xrl wants to merge 2 commits into
etcd-io:mainfrom
xrl:pr/fix-ip-sans
Open

fix: propagate user-supplied altNames.ipAddresses to certificates#393
xrl wants to merge 2 commits into
etcd-io:mainfrom
xrl:pr/fix-ip-sans

Conversation

@xrl

@xrl xrl commented Jul 2, 2026

Copy link
Copy Markdown

Setting spec.tls..providerCfg..altNames.ipAddresses had no effect: the controller filled AltNames.IPs with nil placeholders and never read the user-supplied field, so issued certificates carried no IP SANs on either provider. The controller now passes user IPs through on both the custom and default DNS-name paths (rejecting nil/empty entries with an explicit error), the cert-manager provider builds Certificate.Spec.IPAddresses from ip.String() instead of fmt.Sprint, and the auto provider appends the IPs to the transport.SelfCert hosts list so they land in the issued certificate's IP SANs. Verified with go build ./... and go test ./internal/... ./api/... ./pkg/...; new tests assert the emitted Certificate spec (cert-manager) and the parsed x509 IP SANs (auto), and were confirmed to fail against the pre-fix code.


PR series — operability fixes & TLS

Small single-purpose PRs from live kind-cluster testing of the operator. Each stands alone unless an After is listed. → = this PR.

PR Lands After
Reviewable now — small, any order
🟢 #374 Requeue instead of swallowing the client-cert provisioning error
🟢 #391 Grant events.k8s.io RBAC so operator Events are actually recorded
🟢 #392 Correlate members[]/leaderID from one health snapshot (consistent leader)
🟢→ #393 Propagate user-supplied altNames.ipAddresses into certificates
🟢 #394 Accept day-suffix validityDuration (365d, 100d12h) as documented
🟢 #395 Surface early reconcile errors as a Degraded condition (was empty status)
🟢 #379 Configurable reconcile worker pool (--max-concurrent-reconciles)
🟢 #369 kind-based stress/scale e2e harness (1/3/7 members, churn, quorum watcher)
TLS stack — in order
🟢 #376 Independent spec.tls.{peer,client} surfaces (breaking alpha API)
#377 TLSReady condition + TLS lifecycle Events #376
#378 Multi-member TLS quorum e2e + PeerCANotShared #377
Parked as drafts pending #363
#382 Per-cluster domain metrics on the operator /metrics endpoint
#384 EtcdCluster admission webhooks (consolidating with #328) #363
#386 EtcdBackup CR → object storage (S3/GCS) #363
#387 Automatic quorum-loss disaster recovery (bootstrap-latch guarded) #363

🟢 ready · ⚪ draft

createCMCertificateConfig and createAutoCertificateConfig filled
AltNames.IPs with nil placeholders sized by the DNS-name count and never
read the user-supplied field, so spec.tls.*.providerCfg.*.altNames.ipAddresses
was silently dropped from issued certificates. The cert-manager provider
also stringified IPs via fmt.Sprint (rendering nil entries as literal
"<nil>"), and the auto provider never passed IPs to transport.SelfCert
at all.

Pass the user-supplied IPs through on both the custom and default
DNS-name config paths, reject nil/empty IP entries with an explicit
error, build Certificate.Spec.IPAddresses from ip.String() in the
cert-manager provider, and append the IPs to the transport.SelfCert
hosts list in the auto provider so they land in the issued
certificate's IP SANs. Tests assert the emitted Certificate spec
(cert-manager) and the parsed x509 IP SANs (auto).

Signed-off-by: Xavier Lange <xrlange@gmail.com>
@kubernetes-prow

Copy link
Copy Markdown

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: xrl
Once this PR has been reviewed and has the lgtm label, please assign hakman for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@kubernetes-prow

Copy link
Copy Markdown

Hi @xrl. Thanks for your PR.

I'm waiting for a etcd-io member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work.

Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

Signed-off-by: Xavier Lange <xrlange@gmail.com>
@xrl

xrl commented Jul 3, 2026

Copy link
Copy Markdown
Author

Pushed 0f5b174 to fix the golangci-lint prealloc failure: the ipStrings slice in the cert-manager provider is now preallocated with capacity len(cfg.AltNames.IPs).

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.

1 participant