Repository navigation
docs: refactor getting started tutorial (ISD-7317) - #147
Merged
Merged
Conversation
erinecon
approved these changes
Nov 19, 2026
erinecon
left a comment
Contributor
There was a problem hiding this comment.
Thank you for updating the tutorial 🚀 some non-blocking nits and comments for your consideration
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Applicable spec: ISD-7317
Overview
Refactors the getting started tutorial following the platform engineering charm template: updated requirements (Concierge, Canonical Kubernetes, MicroCeph for S3), Gateway API Integrator with Ingress Configurator for ingress, an explanation of what each charm is for, a self-signed certificate note, and next steps.
Rationale
The tutorial had outdated requirements and used
nginx-ingress-integrator. It didn't explain why each charm is deployed. Ingress Configurator is needed because theingressrelation of Gateway API Integrator serves apps under a path prefix, which Penpot doesn't support.Tested on a Multipass VM with Canonical Kubernetes. The final ordering of steps wasn't re-run from scratch, and login was checked with
curlonly, not in a browser.Juju Events Changes
None.
Module Changes
None.
Library Changes
None.
Checklist
src-docsurgent,trivial,complex)Unchecked items are not applicable: docs only, no code changes.