Releases: hops-ops/cert-stack
v0.3.0
What's changed in v0.3.0
-
feat: Burstable resource defaults for cert-manager (controller + cainjector + webhook) (by @patrickleet)
All three pods shipped as BestEffort by default; cainjector observed at
163Mi on pat-local. Sized for a small-to-medium cluster; override via
spec.values for larger fleets.Implements [[tasks/cluster-wide-resource-right-sizing-p95-observation]] tier-1 #4
-
: (by @patrickleet)
-
feat: Burstable resource defaults for cert-manager (controller + cainjector + webhook) (by @patrickleet)
All three pods shipped as BestEffort by default; cainjector observed at
163Mi on pat-local. Sized for a small-to-medium cluster; override via
spec.values for larger fleets.Verified on pat-local: new pods cert-manager-78bd57b8b5,
cert-manager-cainjector-7f57f5d8f, cert-manager-webhook-55db5974ff
transitioned to Burstable QoS after install (old BestEffort pods
draining).Implements [[tasks/cluster-wide-resource-right-sizing-p95-observation]] tier-1 #4
See full diff: v0.2.0...v0.3.0
v0.2.0
What's changed in v0.2.0
-
feat(deps): update crossplane-contrib/function-auto-ready docker tag to v0.6.4 (#1) (by @renovate[bot])
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
See full diff: v0.1.0...v0.2.0
v0.1.0
What's changed in v0.1.0
-
feat: cert-manager-stack — standalone cert-manager install (by @patrickleet)
Single-claim Crossplane Configuration that installs cert-manager (CRDs +
controller) on a target Kubernetes cluster as one Helm release.No AWS dependencies. For DNS-01 / Route53 ClusterIssuers + ExternalDNS,
use aws-external-dns-stack instead (or alongside, depending on whether
its certManager.enabled flag is set).Use cases:
- Clusters that need cert-manager but not Route53 (e.g. for the
cnpg-i-scale-to-zero plugin's gRPC self-signed Issuer + Certificates) - Splitting concerns: cert-manager-stack handles cert-manager;
external-dns-stack handles DNS automation
Implements [[tasks/cert-manager-stack]]
Co-Authored-By: Claude Opus 4.7 (1M context) noreply@anthropic.com
- Clusters that need cert-manager but not Route53 (e.g. for the
-
refactor: rename CertManagerStack → CertsStack; move to xrs/stacks/aws/certs (by @patrickleet)
- Group: hops.ops.com.ai → aws.hops.ops.com.ai (this is an AWS-namespaced
stack — composes a PodIdentity for Route53) - Kind: CertManagerStack → CertsStack; plural certmanagerstacks →
certsstacks - Configuration package: cert-manager-stack → aws-certs-stack
- Spec flattened: dropped the spec.aws wrapper. Top-level fields are
region, permissionsBoundaryArn, rolePrefix, tags, awsProviderConfigRef,
kubernetesProviderConfigRef - New: spec.route53.enabled (default true) gates the PodIdentity
composition. Disable for clusters using only HTTP-01 or self-signed
Issuers. - Lifted PodIdentity composition pattern from xrs/stacks/aws/dns —
cert-manager ServiceAccount bound to an IAM role with the four
Route53 actions needed for DNS-01 challenges. - Default labels/tags now derive from lower(kind) like other stacks
(hops.ops.com.ai/certsstack key, not hops.ops.com.ai/cert-manager). - Configuration depsOn: provider-kubernetes + aws-pod-identity
Configuration package added.
Implements [[tasks/cert-manager-stack]]
Co-Authored-By: Claude Opus 4.7 (1M context) noreply@anthropic.com
- Group: hops.ops.com.ai → aws.hops.ops.com.ai (this is an AWS-namespaced
-
rename: CertsStack → CertStack (singular reads better) (by @patrickleet)
- Kind: CertsStack → CertStack
- Plural: certsstacks → certstacks
- XRD metadata.name: certsstacks.aws.hops.ops.com.ai → certstacks.aws.hops.ops.com.ai
- Configuration package: aws-certs-stack → aws-cert-stack
- Directory: xrs/stacks/aws/certs/ → xrs/stacks/aws/cert/
- apis/certsstacks/ → apis/certstacks/
- examples/certsstacks/ → examples/certstacks/
Co-Authored-By: Claude Opus 4.7 (1M context) noreply@anthropic.com
-
feat: cloud-neutral cert-stack — group hops.ops.com.ai, drop AWS coupling (by @patrickleet)
XRD group: aws.hops.ops.com.ai → hops.ops.com.ai. Stack now installs
cert-manager via Helm only; cloud-specific DNS-01 plumbing (Route53
PodIdentity, Cloudflare API token) lives in the corresponding DNS stack.- Drop Route53 PodIdentity composition + AWS provider deps
- Slim XRD to cert-manager Helm essentials (clusterName, namespace,
releaseName, chartVersion, values, overrideAllValues, helmProviderConfigRef) - Tests: unit (test-render) + e2e (e2etest-cert-stack)
- CI: on-pr, on-push-main, on-version-tagged via unbounded-tech workflows
Implements [[tasks/cert-manager-stack]]