This repository was archived by the owner on Jun 13, 2025. It is now read-only.
Differentiate between oss commands and MC#25
Merged
Conversation
Emphasize on Mission Control offerings and Open core concept. Signed-off-by: Lucille Hua <lucille.hua@jetpack.io>
Lagoja
approved these changes
Nov 15, 2022
| ### Build, publish, and deploy with a single command | ||
|
|
||
| Launchpad can build any image, publish it to your Docker registry, and deploy it to Kubernetes in one step. | ||
| No need to remember which container image you uploaded to where, and what kube-context to use, Launchpad can build any image, publish it to your Docker registry, and deploy it to Kubernetes in one step. |
There was a problem hiding this comment.
I think we should flip the clauses. The first thing I should read is a clear explanation of what Launchpad does:
Launchpad builds any image, publishes it to your Docker Registry, and deploys it to Kubernetes in one step. No need to manually build and push your image, setup your kube-context, or write long pages of Kubernetes YAML.
| ### A consistent deployment setup per project | ||
|
|
||
| Launchpad defines your project's Kubernetes configuration. Whether you are deploying in development, staging, or production environment, whether you are deploying to a local or remote Kubernetes cluster, Launchpad always creates the same set of Kubernetes resources for you each time. | ||
| ### A Heroku-like experience, except on your Kubernetes cluster |
There was a problem hiding this comment.
Lol, when I first read this I thought it meant "A Heroku like Experience [but not] on your Kubernetes cluster". Let's do:
A Heroku-like exprience on your own Kubernetes cluster
|
|
||
| ### With Mission Control, onboarding new members is as easy as "launchpad up" | ||
|
|
||
| Adding a new member to the team? Forget about Registry access, Cluster credentials, Kubernetes configurations, Namespace permissions, and a million other things to take care of. With Mission Control, Launchpad automatically creates all of the above for each new developer. |
added 3 commits
November 15, 2022 16:21
Signed-off-by: Lucille Hua <lucille.hua@jetpack.io>
Signed-off-by: Lucille Hua <lucille.hua@jetpack.io>
Signed-off-by: Lucille Hua <lucille.hua@jetpack.io>
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
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.
Summary
Emphasize on Mission Control offerings and Open core concept.
How was it tested?
readme markdown preview
Is this change backwards-compatible?
yes