mirror of
https://github.com/cozystack/cozystack.git
synced 2026-11-09 22:13:18 +09:00
docs: add changelog for v1.1.7 (#2447)
This PR adds the changelog for release `v1.1.7`.
✅ Changelog has been automatically generated in
`docs/changelogs/v1.1.7.md`.
This commit is contained in:
1 file changed
+27
@@ -0,0 +1,27 @@
|
||||
<!--
|
||||
https://github.com/cozystack/cozystack/releases/tag/v1.1.7
|
||||
-->
|
||||
|
||||
## Fixes
|
||||
|
||||
* **[platform] Migrate ACME HTTP-01 to ingressClassName API**: `ClusterIssuer` HTTP-01 solvers (`letsencrypt-prod`, `letsencrypt-stage`) were hardcoded to ingress class `nginx`, which does not exist on Cozystack clusters — real classes are named after tenant namespaces (e.g. `tenant-root`). Certificate issuance only worked because every ingress overrode the issuer via the deprecated `acme.cert-manager.io/http01-ingress-class` annotation. Both sides are now migrated to the modern cert-manager API: the `ClusterIssuer` uses `http01.ingress.ingressClassName` (parameterized from `_cluster.expose-ingress`, defaulting to `tenant-root`) and all ingress templates switch to the `acme.cert-manager.io/http01-ingress-ingressclassname` annotation. The migration is atomic — mixing the two APIs triggers cert-manager's validation error "fields ingressClassName and class cannot be set at the same time" ([**@myasnikovdaniil**](https://github.com/myasnikovdaniil) in #2436, backport #2439).
|
||||
|
||||
## Documentation
|
||||
|
||||
* **[website] Document tenant namespace layout and parent/child derivation**: Added two new sections to the Tenant System guide describing how tenant workload namespace names are constructed and how downstream integrations should walk the tenant tree without string-parsing namespace names ([**@lexfrei**](https://github.com/lexfrei) in cozystack/website#479).
|
||||
|
||||
* **[website] Document the checkbox-then-edit-CR customization pattern**: Added a *Customizing Tenant Services* section documenting how to configure a tenant-level service (etcd, monitoring, ingress, seaweedfs) beyond the per-tenant boolean flag — enable the flag then `kubectl edit` the downstream `apps.cozystack.io/v1alpha1` CR, with callouts for common wrong approaches ([**@lexfrei**](https://github.com/lexfrei) in cozystack/website#485).
|
||||
|
||||
* **[website] Fix 14 broken links and stale talm anchor across v1 docs**: Automated pass corrected 14 broken `{{% ref %}}`/`{{% relref %}}` shortcode targets and raw markdown links across 11 files, plus updated a stale `talm` anchor ([**@lexfrei**](https://github.com/lexfrei) in cozystack/website#486).
|
||||
|
||||
* **[website] Rewrite external applications guide for ApplicationDefinition API**: Updated the external apps guide to replace outdated `CozystackResourceDefinition` references with the current `ApplicationDefinition` API and conventions ([**@kitsunoff**](https://github.com/kitsunoff) in cozystack/website#488).
|
||||
|
||||
* **[website] Refactor docs versions to major.minor variants**: Restructured the docs versioning from `v0`/`v1` to per-minor-version directories (`v1.0`, `v1.1`, `v1.2`), making the site compatible with the push-based docs update pipeline ([**@myasnikovdaniil**](https://github.com/myasnikovdaniil) in cozystack/website#477).
|
||||
|
||||
* **[website] Update /docs/v1/ redirect to latest v1.2**: Updated the Netlify redirect `/docs/v1/*` to point to `v1.2` (was outdated `v1.0`) and added a Hugo alias for GitHub Pages compatibility ([**@myasnikovdaniil**](https://github.com/myasnikovdaniil) in cozystack/website#492).
|
||||
|
||||
* **[website] Trunk-based versioning with permanent next/ directory**: Replaced the hardcoded draft-directory approach with a permanent `content/en/docs/next/` trunk for upcoming/unreleased Cozystack docs, excluded from production builds and promoted to `vX.Y/` when the upstream release workflow fires ([**@myasnikovdaniil**](https://github.com/myasnikovdaniil) in cozystack/website#495).
|
||||
|
||||
---
|
||||
|
||||
**Full Changelog**: https://github.com/cozystack/cozystack/compare/v1.1.6...v1.1.7
|
||||
Reference in new issue
Block a user