Strona główna Odkrywaj Pomoc
Zaloguj się
akillibulut
/
porter
kopia lustrzana https://github.com/porter-dev/porter
2
0
Forkuj 0
Pliki Problemy 0 Wiki

Kubernetes powered PaaS that runs in your own cloud. https://porter.run

Drzewo: f56998f6e3
Gałęzie Tagi
porter
ZIP TAR.GZ
Alexander Belanger f56998f6e3 Merge branch 'staging' of https://github.com/porter-dev/porter into staging 5 lat temu
cli 2878611187 comment 5 lat temu
cmd 3ca584ab73 init on startup 5 lat temu
dashboard 4c21affec1 graph yaml scroll and resize fixed 5 lat temu
docker 3ca584ab73 init on startup 5 lat temu
docs 92e7afde68 start onboarding docs 5 lat temu
internal d482360246 Merge pull request #67 from porter-dev/onboarding 5 lat temu
server d482360246 Merge pull request #67 from porter-dev/onboarding 5 lat temu
.air.toml e71b846b93 ignore dashboard in air.toml 5 lat temu
.dockerignore d7b83fb445 onboarding with default sqlite 5 lat temu
.gitignore e00e0bbf39 gitignore yaml 5 lat temu
README.md 92e7afde68 start onboarding docs 5 lat temu
docker-compose.dev.yaml 9eb5469cc8 yaml in nodes 5 lat temu
go.mod f26a8df214 start barely usable 5 lat temu
go.sum 558c04888a cli generate command 5 lat temu

README.md

Porter

Description

Porter is a dashboard for Helm. It currently provides the following features:

  • Visualization of all Helm releases with filtering by namespace
  • In-depth view of releases, including revision histories and component graphs
  • Rollback/update of existing releases, including editing of values.yaml

What's next for Porter? View our roadmap, or read our mission statement.

Getting Started

Local Setup

To view the dashboard locally, we expose a porter start command via our CLI. To download the CLI, grab the latest release via:

TBD

And run the dashboard:

porter start

In-Cluster Setup

TBD

Alternative Tools

Mission Statement

kubectl for your fundamental operations. Porter for everything else.

Our mission is to be the go-to tool for interacting with complex Kubernetes deployments as both a beginner and an expert. While our initial focus is on visualizing Helm components, we believe this visualization and editing can be extended to a number of other tools and concepts, including alternative templating tools (kustomize, Terraform), other deployment tools (CI/CD tools, Terraform), Kubernetes package repositories (ChartMuseum, JFrog Artifactory), and even popular Kubernetes packages (nginx-ingress, cert-manager, prometheus, velero).

More specifically, we have the following long-term goals:

  • Design a visual interface for complex deployments and operations
  • Make deployments and operations editable by and accessible for non-Kubernetes experts
  • Improve the development experience for packaging and releasing Kubernetes applications
  • Increase interoperability of Kubernetes tooling without compromising usability

Why did we begin with Helm? Helm is the most popular auxiliary Kubernetes tool, and can function in nearly all parts of deployment lifecycle. We think of the various features of Helm in the following manner, adapted from Brian Grant's Helm Summit talk (slides here): package management, dependency management, application metadata, parameterization, templating, deployment/config revision management, lifecycle management hooks, and application probes. Along with these fundamental features, an expanding number of command plugins for more specific use-cases have started to become popular in the Helm ecosystem. If we can build a better workflow for both application developers and application operators by improving the user experience for most of these Helm features, we can generalize and expand this workflow to support alternative tooling that exists in the Kubernetes application management ecosystem.