首頁 探索 說明
登入
akillibulut
/
porter
镜像来自 https://github.com/porter-dev/porter
2
0
複刻 0
檔案 問題管理 0 Wiki

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

目錄樹: 74e66cc1e2
分支列表 標籤列表
porter
ZIP TAR.GZ
jusrhee 74e66cc1e2 preview old revisions on click (graph, list, yaml) 5 年之前
cli 2878611187 comment 5 年之前
cmd 3ca584ab73 init on startup 5 年之前
dashboard 74e66cc1e2 preview old revisions on click (graph, list, yaml) 5 年之前
docker 3ca584ab73 init on startup 5 年之前
docs 8ee2294c52 graph per release 5 年之前
internal 8ee2294c52 graph per release 5 年之前
server d482360246 Merge pull request #67 from porter-dev/onboarding 5 年之前
.air.toml e71b846b93 ignore dashboard in air.toml 6 年之前
.dockerignore d7b83fb445 onboarding with default sqlite 5 年之前
.gitignore e00e0bbf39 gitignore yaml 6 年之前
.goreleaser.yml 8ee2294c52 graph per release 5 年之前
README.md baf156f021 add roadmap to docs 5 年之前
docker-compose.dev.yaml 9eb5469cc8 yaml in nodes 5 年之前
go.mod 8ee2294c52 graph per release 5 年之前
go.sum 558c04888a cli generate command 5 年之前
package-lock.json 97c6704158 handle specrel in default namespace 5 年之前

README.md

Porter

Porter is a dashboard for Helm with support for 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, download our CLI and grab the latest release via:

TBD

Then run the dashboard (Docker engine must be running on the host machine):

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.