janhoy opened a new pull request, #863:
URL: https://github.com/apache/solr-operator/pull/863

   Part of the overall epic #813
   
   Follows #814, which added the publishing tooling without changing anything 
users see. This one makes the switch.
   
   Makes `oci://ghcr.io/apache/solr-operator/helm` the documented way to 
install both charts, and marks `https://solr.apache.org/charts` as deprecated. 
Installing from OCI needs no `helm repo add` and no credentials.
   
   ```bash
   helm install solr-operator 
oci://ghcr.io/apache/solr-operator/helm/solr-operator --version 0.10.0
   helm install example       oci://ghcr.io/apache/solr-operator/helm/solr 
--version 0.10.0
   ```
   
   ## Deprecation plan
   
   Charts go to **both** channels throughout the 0.x releases, so no patch 
upgrade breaks. **From `v1.0.0`, the OCI registry only** — a major version 
gives a version-anchored deadline instead of a date that slips.
   
   ## What changed
   
   - Both chart READMEs lead with OCI, HTTPS documented as deprecated. The two 
paths sit in separate fenced blocks, so copy-pasting one does not run both.
   - Top-level `README.md` and the `running-the-operator`, `local-tutorial` and 
`upgrade-notes` Antora pages lead with OCI.
   - `upgrade-notes.adoc` gains a "Where the Helm charts are published" section 
and a v0.10.0 entry pointing at it.
   - Both `Chart.yaml` files gain `artifacthub.io/changes` entries, so the 
switch shows up in the Artifact Hub changelog.
   
   ## Verified before opening
   
   v0.8.1 and v0.9.1 are published and anonymously pullable from the OCI 
registry with `helm pull --verify`, no credentials and no `helm registry login`.
   
   ## Not in this PR
   
   Re-configuring Artifact Hub to list the OCI charts is manual work in their 
control panel and is tracked in #862. Until that is done the Artifact Hub pages 
keep showing `helm repo add`, which is why this PR documents the OCI commands 
directly rather than deferring to Artifact Hub.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to