250 likes | 278 Vues
Deploying your Applications. In a Repeatable Way on Kubernetes. Kubernetes Master Class. Chris Kim Field Engineer @Oats871. Matthew Scheer Marketing Manager @ matthew_scheer. #RancherK8s. Rancher Master Class Series: Trying to keep this to 40-45 minutes
E N D
Deploying your Applications In a Repeatable Way on Kubernetes Kubernetes Master Class
Chris Kim Field Engineer @Oats871 Matthew Scheer Marketing Manager @matthew_scheer #RancherK8s
Rancher Master Class Series: Trying to keep this to 40-45 minutes Questions are always welcome Use the questions tab to write your questions We may respond to all, so mark your question as private if needed. #Rancherk8s
This session is being recorded! http://youtube.com/c/rancher #Rancherk8s
Join the conversation on Slack http://slack.rancher.io #masterclass #RancherK8s
Upcoming Classes http://rancher.com/kubernetes-master-class/ #RancherK8s
Deploying your Applications In a Repeatable Way on Kubernetes
Key Topics • Introduction to Helm • Helm vs. Rancher 2 Catalog • Creating your own Helm/Catalog Repository • Creating a questions.yml for Custom Catalog Apps • Managing the Lifecycle of your Applications
Introduction to Helm • Helm is a package manager for Kubernetes • Allows you to package your application using a Chart • Charts allow you to templatize the Kubernetes manifests required to make your application work • Does not eliminate CI/CD Pipelines • More information can be found at https://helm.sh/docs/
Helm vs. Rancher 2 Catalog • Rancher 2 Catalogs provide a user interface to interact with Helm Charts • Rancher provides a curated Catalog library • Custom repositories can also be added, whether Git or Helm based
Helm vs. Rancher 2 Catalog • With a little bit of metadata, you can make your charts interactive • This means adding a question/answer interface • This allows for point-and-click deployments of Helm charts
Demo of Wordpress Catalog App • I will demo using the Wordpress Catalog App to install Wordpress
Creating your own Helm/Catalog Repository • As mentioned earlier, Rancher allows you to add your own “custom” Catalog repository
Creating your own Helm/Catalog Repository • Conveniently, Rancher provides a Chart Museum chart • It’s important to set the ”Absolute URL for tgzs in index.yaml”
Demo of Catalog Repository • Create Chart Museum • Add Chart to Chart Museum • Add Custom Repo to Rancher
Creating a questions.yml • Rancher Catalogs are powered by two additional metadata files • questions.yml • app-readme.md • Detailed documentation on these can be found here: https://rancher.com/docs/rancher/v2.x/en/catalog/custom/creating/
Inspecting the Submariner questions.yml • We will take a quick look at the submariner questions.yml file
Managing the Lifecycle of your Application • Helm stores application configuration as a configmap • Because of this, Helm conveniently has a “rollback” capability • Regardless, thinking forward, as you release new versions of your app and have Rancher refresh your catalog, you can perform “upgrades” • These are very similar to a helm upgrade
Rancher, RancherOS, RKE are in GitHub http://github.com/rancher
@Rancher_Labs · #Rancherk8s Rancher.com/kubernetes-master-class Rancher.com/training Thank you!