You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
tls: wire signer certs to read PKI config via SignerKeyParams
Introduce SignerKeyParams, a WritableAsset with zero dependencies that
reads install-config.yaml via AssetBase.LoadFromFile (strict YAML,
deprecated field conversion, defaults) and extracts the effective PKI
configuration via EffectiveSignerPKIConfig(). When no install-config
is present, Load() returns (false, nil) so the asset store falls back to
the state file between multi-step invocations (e.g. create manifests
followed by create cluster, where install-config.yaml is consumed after
the first step). In the agent flow where neither file nor state exists,
Generate() leaves PKIConfig nil (RSA-2048).
SignerKeyParams is explicitly added to the Manifests and agent
target asset lists so that its PKIConfig is persisted to the state
file, ensuring correct key algorithms in multi-step flows where
install-config.yaml is consumed between commands.
Signers that previously had zero dependencies now depend on
SignerKeyParams instead of InstallConfig, avoiding validation that
would reject configs valid in the agent flow. Signers that already
depended on InstallConfig use EffectiveSignerPKIConfig() to resolve
the effective PKI config including feature gate defaults.
With TechPreview enabled and no explicit pki config, all signer certs
are generated with RSA-4096 (the current DefaultPKIProfile default).
Assisted-by: Claude Code (Opus 4.6)
0 commit comments