Skip to content

Debulleting the Porch - Concepts pages#484

Open
lovesprung wants to merge 1 commit intonephio-project:mainfrom
nokia:debulleting_concepts
Open

Debulleting the Porch - Concepts pages#484
lovesprung wants to merge 1 commit intonephio-project:mainfrom
nokia:debulleting_concepts

Conversation

@lovesprung
Copy link

@lovesprung lovesprung commented Mar 12, 2026

Title

Debulleting the Porch - Concepts pages


Description

Minor rewrites to make the text more readable.


Type of Change

  • Bug fix
  • New feature
  • Enhancement
  • Refactor
  • Documentation
  • Tests
  • Other: ________

Checklist

  • Code follows project style guidelines
  • Self-reviewed changes
  • Tests added/updated
  • Documentation added/updated
  • All tests and gating checks pass

@netlify
Copy link

netlify bot commented Mar 12, 2026

Deploy Preview for porch ready!

Name Link
🔨 Latest commit 8629d3f
🔍 Latest deploy log https://app.netlify.com/projects/porch/deploys/69b28d10adb4a90008e44c4c
😎 Deploy Preview https://deploy-preview-484--porch.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@dosubot dosubot bot added size:L This PR changes 100-499 lines, ignoring generated files. documentation Improvements or additions to documentation labels Mar 12, 2026

* **Standard kpt packages**
Packages remain standard kpt packages. No vendor lock-in or Porch specific DSL "code" in kpt packages.
With Porch, you can manage packages through Kubernetes resources (PackageRevision, Repository) instead of direct Git operations. Use kubectl, client-go, or any Kubernetes tooling, or Porch's `porchctl` CLI utility. Packages move through lifecycle stages (Draft → Proposed → Published) with **approval workflows** and explicit approval gates, which helps prevent accidental publication of unreviewed changes. **Automatic package discovery** lets you register a Git or OCI repository once; Porch then discovers all packages in it, so there is no need for manual inventory management. **Function execution** applies KRM functions to transform and validate packages; functions run in isolated containers and their results are recorded in package history. **Package cloning and upgrades** let you clone packages from upstream sources and upgrade them automatically when new upstream versions are published, with a three-way merge preserving local customizations. **GitOps integration** means all changes are committed to Git with full history, and Porch works with [Flux](https://fluxcd.io/), [Config Sync](https://docs.cloud.google.com/kubernetes-engine/config-sync/docs/how-to/installing-config-sync), and other GitOps deployment tools. **Multi-repository orchestration** lets you manage packages across multiple Git and OCI repositories from a single control plane, and controllers can automate cross-repository operations. **Collaboration and governance** allow multiple users and automation to work on packages at the same time, with draft revisions providing workspace isolation before publication. **Repository synchronization** lets Porch detect changes made directly in Git (outside Porch) and update its cache, and it supports both Porch-managed and externally-managed packages. Packages remain **standard kpt packages**, with no vendor lock-in or Porch-specific DSL in the kpt package content.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i am a little concerned about this block in particular. i know we are "de-bulleting" but i think this one block pushes too much content into just one paragraph. i think it could do with a bit more segmentation in this instance.

reading all the "benefits/reasons to use porch" is far easier in segmented chunks than one big paragraph of this length.

The rest of the PR looks great.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

bit of a question. why are we making bulletining the "Overview" section in the "Debulleting the Porch - Concepts pages" PR? should this not be in #485?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation size:L This PR changes 100-499 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants