-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Differentiate between oss commands and MC #25
Conversation
Emphasize on Mission Control offerings and Open core concept. Signed-off-by: Lucille Hua <[email protected]>
README.md
Outdated
|
||
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.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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.
README.md
Outdated
|
||
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.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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
README.md
Outdated
|
||
### 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. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
++
Signed-off-by: Lucille Hua <[email protected]>
Signed-off-by: Lucille Hua <[email protected]>
Signed-off-by: Lucille Hua <[email protected]>
Summary
Emphasize on Mission Control offerings and Open core concept.
How was it tested?
readme markdown preview
Is this change backwards-compatible?
yes