kubes 0.7.10 → 0.8.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 6529d951f35f31cf105591f8d5ea0f3b8819e358f0b3388f22d17340af1f2bbf
-  data.tar.gz: d1c6e87a899a75a8f7078046c4058c69c46328c3b7138b4a934dae7fe287be4d
+  metadata.gz: 242d998c0a7f9c86c4db5d79eef556f3d5cac56d7131eedfd9c14b9b96975ef6
+  data.tar.gz: f38ef641ff71c45c84335723b3f0b67abe2a3d26132a8a407738391724a4acf7
 SHA512:
-  metadata.gz: 245ca41ceec0499da84ef056b19ad6f99e422f3c1013718d3e466128aeab6503fc1d0c3be19892633dab1acff1865816885fa6f7d1589c60d5ebe65cfaffab50
-  data.tar.gz: 551a265282d0a6af874517382859492bbe27bcd201790e94f3f7a9540d6ffeb4b6dc678b0aa1cfeab4e5983a0a591625da21ef7ec59bb01fe8c33fdbf681e8c2
+  metadata.gz: 345a9b9bbf12abd164e7aaec68be929cb7d8d61a6f05334a749e987722e2992f828f322a77e6c31a904fa716f984943bd6d638a19830efdfbaa24e0969ab0e80
+  data.tar.gz: 47dc50264262dd94fd085426f99f1e138e61c0362a77c11a087bd9b3a99829897a30aadf52bde6603260386f606059326dbc6cb90bf15c51a5f51755dc6a88ba

data/CHANGELOG.md

@@ -3,6 +3,10 @@
 All notable changes to this project will be documented in this file.
 This project *loosely tries* to adhere to [Semantic Versioning](http://semver.org/), even before v1.0.
 
+## [0.8.0] - 2022-02-06
+- [#58](https://github.com/boltops-tools/kubes/pull/58) standalone install docs
+- [#59](https://github.com/boltops-tools/kubes/pull/59) central deployer support
+
 ## [0.7.10] - 2021-12-18
 - [#56](https://github.com/boltops-tools/kubes/pull/56) New hook generator
 - [#57](https://github.com/boltops-tools/kubes/pull/57) Fix activesupport require

data/docs/Gemfile

@@ -2,6 +2,7 @@ source "https://rubygems.org"
 
 gem "html-proofer"
 gem "jekyll"
+gem "jekyll-include-cache"
 gem "opal"
 gem "opal-browser"
 gem "opal-jquery"

data/docs/_config.yml

@@ -70,4 +70,10 @@ defaults:
 plugins_dir:
   # - jekyll-gzip - GitHub pages does not support this plugin.
 
+# List of supported plugins:
+# https://pages.github.com/versions.json
+# https://github.com/github/pages-gem/issues/171
+plugins:
+- jekyll-include-cache # Supported by GitHub pages
+
 ads_url: "https://ads.boltops.com"

data/docs/_docs/config/app-overrides.md

@@ -0,0 +1,7 @@
+---
+title: App Overrides Cheatsheet
+---
+
+Kubes supports app-level overrides. This is especially useful for the [Central Deployer Pattern]({% link _docs/patterns/central-deployer.md %}).
+
+{% include config/app-overrides-cheatsheet.md %}

data/docs/_docs/config/boot.md

@@ -0,0 +1,46 @@
+---
+title: Boot Hooks
+---
+
+If you need to hook into the Kubes boot process super-early on, Kubes boot hooks are designed for that.
+
+* They run very early in the Kubes boot process.
+* They are useful for setting shared global values like env vars.
+* Boot hooks are ruby files that get required. It's nice and simple. There's no interface to learn.
+
+## Hooks
+
+Kubes will searches 2 files in the `config` folder. If the files exist, they will be ran in this order.
+
+1. **.kubes/config/boot.rb**: Always runs.
+2. **.kubes/config/boot/KUBES_ENV.rb**: Runs based on the env. IE: `KUBES_ENV=dev` => `.kubes/config/boot/dev.rb`
+
+Both files are required and ran if they both exists. Since the `KUBES_ENV` one runs second, it can be used to override previously set values.
+
+## Example: Default KUBES_ENV
+
+If you prefer a different default than `KUBES_ENV=dev`.
+
+config/boot.rb
+
+```ruby
+ENV['KUBES_ENV'] ||= 'development'
+```
+
+This changes the default for everyone using the project, but still allows them to control the default by adding `export KUBES_ENV=development` to their `~/.bash_profile`.
+
+## Example: Auto-Switch AWS_PROFILE
+
+One useful example is switching `AWS_PROFILE` based on the `KUBES_ENV`. Example:
+
+config/boot/dev.rb
+
+```ruby
+ENV['AWS_PROFILE'] = 'dev'
+```
+
+This example is for AWS, but you can can do similiar switch logic with `GOOGLE_APPLICATION_CREDENTIALS`, etc.
+
+## Boot Source
+
+Please refer to the boot source code for more details: [kubes/booter.rb](https://github.com/boltops-tools/kubes/blob/master/lib/kubes/booter.rb)

data/docs/_docs/config/env.md

@@ -16,7 +16,9 @@ Kubes.configure do |config|
 end
 ```
 
-## Layering
+## Config Overrides
+
+### Env Overrides
 
 You can override configs on a per-env basis with `config/env` files. Examples:
 
@@ -38,7 +40,32 @@ Kubes.configure do |config|
 end
 ```
 
-For more details refer to the [Layering Docs]({% link _docs/layering.md %}).
+### App Overrides
+
+If KUBES_APP is set, app-scoped configs can be used to override settings further. Here are some with `config/env/app` example files:
+
+.kubes/config/env/app1/dev.rb
+
+```ruby
+Kubes.configure do |config|
+  config.repo = "222222222222.dkr.ecr.us-west-2.amazonaws.com/demo"
+  config.kubectl.context = "dev-cluster"
+end
+```
+
+.kubes/config/env/app2/prod.rb
+
+```ruby
+Kubes.configure do |config|
+  config.repo = "333333333333.dkr.ecr.us-west-2.amazonaws.com/demo"
+  config.kubectl.context = "prod-cluster"
+end
+```
+
+This allows you to set specific app-level settings with:
+
+    KUBES_APP=app1 kubes deploy
+    KUBES_APP=app2 kubes deploy
 
 ## Auto-Switching Context
 

data/docs/_docs/config/reference.md

@@ -8,7 +8,7 @@ auto_prune | Prune and delete old hashed resources like Secret and ConfigMap. |
 builder | What docker build command to use. Can use `docker` or `gcloud` to build the Docker image. | docker
 image | Set a prebuilt Docker image to use. This is optional. Usually, you want to build an image from the Dockerfile.  Setting this will change the `docker_image` helper to use a predefined image. See: [Docker Image]({% link _docs/intro/docker-image.md %}) | nil
 kubectl.context | What kubectl context to auto-switch to. | nil
-kubectl.context_keep | Whether or not to keep the context switched | true
+kubectl.context_keep | Whether or not to keep the context switched | false
 kubectl.exit_on_fail.apply  | Whether or not continue if the `kubectl apply` fails. Note, can use `KUBES_EXIT_ON_FAIL=0` env var to set to false. | true
 kubectl.exit_on_fail.delete | Whether or not continue if the `kubectl delete` fails. | false
 kubectl.order.kinds | Change ordering for Kubernetes Kinds. | See [source code](https://github.com/boltops-tools/kubes/blob/master/lib/kubes/config.rb#L52)
@@ -18,6 +18,6 @@ logger.level | Logger level. Can also be set with `KUBES_LOG_LEVEL` env var | in
 repo | The Docker repo to use. Required to be set. | nil
 repo_auto_auth | Whether or not to try to auth authorize docker repo registry if not yet logged in. Can also be set with env var `KUBES_REPO_AUTO_AUTO` | true
 skip | List of resources to skip. Can also be set with the `KUBES_SKIP` env var. `KUBES_SKIP` should be a list of strings separated by spaces. It adds onto the `config.skip` option. | []
-state.path | Where to store the state file with the last build Docker image. | .kubes/state/KUBES_ENV/data.json
+state.path | Where to store the state file with the last build Docker image. | .kubes/state/KUBES_APP/KUBES_ENV/data.json
 suffix_hash | Whether or not to append suffix hash to ConfigMap and Secret | true
 merger.options | Merger options that control how Hashes are merged. More info: [Merger Options]({% link _docs/layering/merge-options.md %}) | `{overwrite_arrays: true}`

data/docs/_docs/config/skip.md

@@ -56,3 +56,25 @@ You can also us ethe `KUBES_SKIP` env var. It takes list of strings separated by
     KUBES_SKIP="cleanup/job" kubes delete
 
 This can be useful for one-off use cases.
+
+## Skip With kubes skip metdata
+
+You can also skip a resource from being written by using `kubes.skip = true`. This is useful if you want to conditionally not create a resource with a variable. Example:
+
+.kubes/resources/config_map.yaml
+
+```yaml
+<% if @skip %>
+kubes:
+  skip: true
+<% end %>
+metadata:
+  namespace: demo-dev
+  labels:
+    app: demo-dev
+  name: demo-dev-configmap-495c18844b
+apiVersion: v1
+kind: ConfigMap
+```
+
+If the variable is set to `@skip = true`, then the config_map.yaml will not get created.

data/docs/{_includes/intro/install.md → _docs/install/dependencies.md}

@@ -1,10 +1,9 @@
-## RubyGems
+---
+title: Install Dependencies
+---
 
-Install kubes via RubyGems.
+These dependencies are not included with any of the installers. This allows you to install and run the versions you want to use.
 
-    gem install kubes
-
-Ruby 2.7 and above is recommended.
 
 ## kubectl
 

data/docs/_docs/install/gem.md

@@ -0,0 +1,6 @@
+---
+title: Gem Installation
+---
+
+{% include install/gem.md %}
+

data/docs/_docs/install/standalone/centos.md

@@ -0,0 +1,70 @@
+---
+title: "Install: CentOS/RedHat/Fedora"
+nav_text: CentOS
+category: standalone
+order: 2
+---
+
+This page shows you how to install kubes on CentOS, RedHat, Fedora and other Linux systems that use the yum-based package manager.
+
+## CentOS/RedHat/Fedora
+
+Configure repo
+
+    sudo su
+    curl -so /etc/yum.repos.d/boltops.repo https://yum.boltops.com/boltops.repo
+    rpm --import https://yum.boltops.com/boltops-key.public
+
+Install
+
+    yum install -y kubes
+
+Upgrade
+
+    yum makecache
+    yum update -y kubes
+
+Uninstall
+
+    yum remove -y kubes
+
+{% include install/wrapper.md %}
+
+## Fedora Notes
+
+For Fedora, you may also need the libxcrypt-compat package.
+
+    dnf install libxcrypt-compat -y
+
+Or you'll get this error:
+
+    $ kubes -h
+    /opt/kubes/embedded/bin/ruby: error while loading shared libraries: libcrypt.so.1: cannot open shared object file: No such file or directory
+    $
+
+Fedora is a bleeding edge distro and is quicker about upgrading their system. The `libcrypt.so` has been removed. The libxcrypt-compat package installs it back.
+
+## Amazon Linux 2 Notes
+
+The standalone installer does not support Amazon Linux 1.  Please use Amazon Linux 2 instead.
+
+## Rpm Install
+
+You can also download the rpm package and install it directly. Here are the commands:
+
+    wget https://yum.boltops.com/packages/kubes/kubes-latest.rpm
+    sudo su
+    rpm -ivh kubes-latest.rpm
+    kubes -h
+
+To upgrade an existing install also use the `-U` flag.
+
+    rpm -Uivh kubes-latest.rpm
+
+You can check [kubes-latest.rpm.metadata.json](https://yum.boltops.com/packages/kubes/kubes-latest.rpm.metadata.json) to verify the package checksum. Here's the checksum command.
+
+    sha256sum kubes-latest.rpm
+
+To uninstall
+
+    rpm -e kubes-latest.rpm

data/docs/_docs/install/standalone/details/permissions.md

@@ -0,0 +1,44 @@
+---
+title: "Standalone Permissions"
+nav_text: Permissions
+category: standalone-details
+---
+
+The kubes standalone installer will make sure that the owner and permissions of the `/opt/kubes` folder is your user.
+
+If the `/opt/kubes` folder is not owned by your user for whatever reason, here are the commands to change it:
+
+For macosx:
+
+    sudo chown -R `whoami`:staff /opt/kubes
+
+For other Linux OSes, this is generally:
+
+    sudo chown -R `whoami`:`whoami` /opt/kubes
+
+## Why?
+
+When the `/opt/kubes` folder is not owned by your user, you won't be able to write to it without sudo. This results in a sudo prompt when kubes calls `bundle` and tries to install new gems. You will see this:
+
+    => Installing dependencies with: bundle install
+    Following files may not be writable, so sudo is needed:
+      /opt/kubes/embedded/bin
+      /opt/kubes/embedded/lib/ruby/gems/2.7.0
+      /opt/kubes/embedded/lib/ruby/gems/2.7.0/cache
+      /opt/kubes/embedded/lib/ruby/gems/2.7.0/extensions
+      /opt/kubes/embedded/lib/ruby/gems/2.7.0/gems
+      /opt/kubes/embedded/lib/ruby/gems/2.7.0/specifications
+
+    Your user account isn't allowed to install to the system RubyGems.
+      You can cancel this installation and run:
+
+          bundle install --path vendor/bundle
+
+      to install the gems into ./vendor/bundle/, or you can enter your password
+      and install the bundled gems to RubyGems using sudo.
+
+      Password:
+
+To fix this issue, make sure `/opt/kubes` is owned by your user, instead of repeatedly having to type your password for sudo.
+
+Also, running `sudo` means you're using bare shell with pretty much none of your environment settings or variables configured. Though there are ways to [preserve](https://stackoverflow.com/questions/8633461/how-to-keep-environment-variables-when-using-sudo) environment variables with `--preserve-env`, it's often better to avoid sudo as you'll run into different environmental differences and quirks.

data/docs/_docs/install/standalone/details/uninstall.md

@@ -0,0 +1,16 @@
+---
+title: "Uninstall Cleanup"
+nav_text: Uninstall
+category: standalone-details
+order: 4
+---
+
+Some packager managers will not clean up the installed files completely. The apt-get and yum package manager generally cleans up everything. Homebrew doesn't seem to clean up currently though.
+
+To fully clean up and uninstall kubes. First, run the package manger uninstall command and then clean up with:
+
+    rm -rf /opt/kubes
+
+Then remove the kubes wrappers in `/usr/local/bin`. You can remove them with this command:
+
+    grep -l /opt/kubes /usr/local/bin/* | xargs rm -f

data/docs/_docs/install/standalone/details.md

@@ -0,0 +1,20 @@
+---
+title: "Standalone Details"
+nav_text: Details
+category: standalone
+order: 9
+---
+
+The standalone installer packages are built within a few minutes of the kubes gem release. This page covers more details on how the standalone installation works.
+
+## Isolated: /opt/kubes
+
+The standalone kubes package installs kubes in `/opt/kubes`. This folder contains everything like system libraries, Ruby, and gems needed for kubes to work as a standalone package. Additionally, this also makes it easy to remove kubes.
+
+## Wrapper: /usr/local/bin
+
+The installer creates a wrapper script in `/usr/local/bin`.
+
+    /usr/local/bin/kubes
+
+Most users have `/usr/local/bin` configured in there PATH. So this wrapper should work.

data/docs/_docs/install/standalone/macosx.md

@@ -0,0 +1,45 @@
+---
+title: "Install: Mac OSX"
+nav_text: MacOSX
+category: standalone
+order: 1
+---
+
+This page shows you how to install kubes on Mac OSX.
+
+Here's a "Mac OSX Homebrew Install" Video:
+
+## Homebrew
+
+You can install kubes via homebrew.
+
+Install
+
+    brew tap boltops-tools/software
+    brew install kubes
+
+Upgrade
+
+    brew update
+    brew install kubes
+
+Uninstall
+
+    brew uninstall kubes
+
+Cleanup
+
+    rm -rf /opt/kubes
+    grep -l /opt/kubes /usr/local/bin/* | xargs rm -f
+
+{% include install/wrapper.md %}
+
+## DMG
+
+You can also download the dmg and install with the Mac OSX GUI installer.
+
+Download link: [kubes DMG](https://tap.boltops.com/packages/kubes/kubes-latest.dmg)
+
+You can check [kubes-latest.dmg.metadata.json](https://tap.boltops.com/packages/kubes/kubes-latest.dmg.metadata.json) to verify the package checksum. Here's the checksum command.
+
+    shasum -a 256 kubes-latest.dmg

data/docs/_docs/install/standalone/ubuntu.md

@@ -0,0 +1,48 @@
+---
+title: "Install: Ubuntu/Debian"
+nav_text: Ubuntu
+category: standalone
+order: 3
+---
+
+This page shows you how to install kubes on Ubuntu and Debian based linux systems that use the apt package manager.
+
+## Ubuntu/Debian: apt-get install
+
+Configure repo
+
+    sudo su
+    echo "deb https://apt.boltops.com stable main" > /etc/apt/sources.list.d/boltops.list
+    curl -s https://apt.boltops.com/boltops-key.public | apt-key add -
+
+Install
+
+    apt-get update
+    apt-get install -y kubes
+
+Upgrade
+
+    apt-get install -y kubes
+
+Remove
+
+    apt-get remove -y kubes
+
+{% include install/wrapper.md %}
+
+## Deb Install
+
+You can also download the deb package and install it directly. Here are the commands:
+
+Install
+
+    wget https://apt.boltops.com/packages/kubes/kubes-latest.deb
+    dpkg -i kubes-latest.deb
+
+You can check [kubes-latest.deb.metadata.json](https://apt.boltops.com/packages/kubes/kubes-latest.deb.metadata.json) to verify the package checksum. Here's the checksum command.
+
+    sha256sum kubes-latest.deb
+
+Uninstall
+
+    dpkg -r kubes-latest.deb

data/docs/_docs/install/standalone.md

@@ -0,0 +1,43 @@
+---
+title: Standalone Package Installation
+---
+
+You can install Kubes as a standalone package.  The nice thing about this approach is that it is easy. You don't have to have Ruby installed. You don’t have to worry about compatible Ruby versions, gems, or conflicting system packages.
+
+Kubes provides the pre-built binaries. Other tools such as [vagrant](https://www.vagrantup.com/), written in ruby, and the [aws cli](https://aws.amazon.com/cli/), written in python, also work the same way.
+
+Important: If you're using rvm or rbenv and already have Ruby installed, you should [install kubes as a gem]({% link _docs/install/gem.md %}). Otherwise, different gem dependencies from the two installations can be used and cause all kinds of trouble.
+
+Below are quickstart instructions for different OSes.
+
+## Mac OSX
+
+    brew tap boltops-tools/software
+    brew install kubes
+
+More info on [Mac OSX Install]({% link _docs/install/standalone/macosx.md %})
+
+## CentOS/RedHat/Fedora
+
+    sudo su
+    curl -so /etc/yum.repos.d/boltops.repo https://yum.boltops.com/boltops.repo
+    rpm --import https://yum.boltops.com/boltops-key.public
+    yum install -y kubes
+
+More info on [CentOS Install]({% link _docs/install/standalone/centos.md %})
+
+## Ubuntu/Debian
+
+    sudo su
+    echo "deb https://apt.boltops.com stable main" > /etc/apt/sources.list.d/boltops.list
+    curl -s https://apt.boltops.com/boltops-key.public | apt-key add -
+    apt-get update
+    apt-get install -y kubes
+
+More info on [Ubuntu Install]({% link _docs/install/standalone/ubuntu.md %})
+
+{% include install/wrapper.md %}
+
+## How It Works
+
+The standalone installer packages are built within a few minutes of the kubes gem release. Here are also details on how the standalone installer works: [Standalone Details]({% link _docs/install/standalone/details.md %}).

data/docs/_docs/install.md

@@ -0,0 +1,8 @@
+---
+title: Installation
+---
+
+Here are the ways to install Kubes.
+
+1. [Gem]({% link _docs/install/gem.md %}): This is a great way if you already have Ruby on your system.
+2. [Standalone Installer]({% link _docs/install/standalone.md %}): This is a great way if you don't yet have Ruby installed, and want a quick and easy way to install Kubes. There are installers for [Mac OSX]({% link _docs/install/standalone/macosx.md %}), [CentOS]({% link _docs/install/standalone/centos.md %}), [Ubuntu]({% link _docs/install/standalone/ubuntu.md %}), etc.

data/docs/_docs/learn/dsl/install.md

@@ -2,4 +2,4 @@
 title: Install Kubes
 ---
 
-{% include intro/install.md %}
+{% include install/gem.md %}

data/docs/_docs/learn/yaml/install.md

@@ -2,4 +2,4 @@
 title: Install Kubes
 ---
 
-{% include intro/install.md %}
+{% include install/gem.md %}

data/docs/_docs/patterns/central-deployer.md

@@ -0,0 +1,36 @@
+---
+title: Central Deployer Pattern
+nav_text: Central Deployer
+categories: patterns
+---
+
+Kubes can be use as either an app-centric or ops-centric tool.
+
+* **app-centric**: Each app repo has it's own `.kubes` settings files. This is useful if your applications are very differently setup.
+* **ops-centric**: Each app repo has pretty much the same `.kubes` settings files. This is useful if your applications are very similarly setup.
+
+## Setup
+
+With an ops-centric approach, you use the same `.kubes` settings files for the app repos you want to use. For example:
+
+    https://github.com/repo/app1
+    https://github.com/repo/app2
+
+You then also have a
+
+    https://github.com/repo/.kubes
+
+You can simply copy the `.kubes` folder into the app repo folder or even add the `repo/.kubes` as a submodule.
+
+You'll end up with something like this:
+
+    app1/.kubes
+    app2/.kubes
+
+Then to deploy different app level settings.
+
+{% include config/app-overrides-cheatsheet.md %}
+
+The central deployer approach is removes duplication of the kubes config files between projects. Leveraging app-level overrides gives provides a great degree of control.
+
+If the settings start to diverge too much, then it probably makes sense to use separate .kubes files in that app specific repo.

data/docs/_docs/variables/advanced.md

@@ -2,6 +2,7 @@
 title: Advanced Variables
 nav_text: Advanced
 categories: variables
+order: 2
 ---
 
 Basic variables layering should provides enough flexibility and is generally recommended. This page  covers more advanced variables layering.
@@ -44,12 +45,26 @@ And when `KUBES_ENV=prod`:
 
 With advanced layering you can target a specific role and kind. So variables are only scoped to the resources you want.
 
+## App-Level Overrides
+
+If KUBES_APP is set, then app level layer overrides will also be processed. Example:
+
+    KUBES_APP=app1 kubes deploy
+
+Here's an example with some of the additional files that get layered:
+
+    .kubes/variables/app1.rb
+    .kubes/variables/app1/base.rb
+    .kubes/variables/app1/dev.rb
+
+This is useful if you're using kubes as part of a central deployer pattern. For the full list of layers refer to the table below:
+
 ## Full Layering Table
 
 Here's a table showing the the full layering.
 
 Folder/Pattern    | Example
-------------------|--------------------------------------------
+------------------|----------------------------
 base.rb           | base.rb
 ENV.rb            | dev.rb
 base/all.rb       | base/all.rb
@@ -61,4 +76,20 @@ ROLE/KIND.rb      | web/deployment.rb
 ROLE/KIND/base.rb | web/deployment/base.rb
 ROLE/KIND/ENV.rb  | web/deployment/dev.rb
 
+If KUBES_APP is set then these additional layers are also processed:
+
+Folder/Pattern    | Example
+------------------|----------------------------
+APP.rb           | app1.rb
+APP/base.rb           | app1/base.rb
+APP/ENV.rb            | app1/dev.rb
+APP/base/all.rb       | app1/base/all.rb
+APP/base/all/ENV.rb   | app1/base/all/dev.rb
+APP/base/KIND.rb      | app1/base/deployment.rb
+APP/base/KIND/base.rb | app1/base/deployment/base.rb
+APP/base/KIND/ENV.rb  | app1/base/deployment/dev.rb
+APP/ROLE/KIND.rb      | app1/web/deployment.rb
+APP/ROLE/KIND/base.rb | app1/web/deployment/base.rb
+APP/ROLE/KIND/ENV.rb  | app1/web/deployment/dev.rb
+
 {% include variables/generator.md %}

data/docs/_docs/variables/basic.md

@@ -2,6 +2,7 @@
 title: Basic Variables
 nav_text: Basic
 categories: variables
+order: 1
 ---
 
 ## Basic Layering Example

data/docs/_docs/vs/custom.md

@@ -4,6 +4,8 @@ nav_text: Custom Solutions
 categories: vs
 ---
 
+{% include videos/learn/vs.md %}
+
 Kubernetes provides a great platform to run and manage Docker containers. The `kubectl` command is usually how you interact with a Kubernetes cluster.  It does its job well and is quite a powerful tool.
 
 {% include vs/article.md %}

data/docs/_docs/vs/helm.md

@@ -4,6 +4,8 @@ nav_text: Helm
 categories: vs
 ---
 
+{% include videos/learn/vs.md %}
+
 Kubes and Helm are quite different.  Helm is a package manager tool. In contrast, Kubernetes is focused on deploying your application. While you can use package manager tools like Helm to deploy your application, application-focused deploy tools are better for the job. For example, apt-get and yum are also package manager tools. But few companies use `apt-get install` or `yum install` to deploy their application code. Instead, people usually use application-specific tools to deploy their web app.
 
 {% include vs/article.md %}

data/docs/_docs/vs/kustomize.md

@@ -4,6 +4,8 @@ nav_text: Kustomize
 categories: vs
 ---
 
+{% include videos/learn/vs.md %}
+
 Though both Kubes and Kustomize build YAML files, they are quite different beasts. Kustomize is more like a `kubectl` feature that decorates YAML. Kubes is more like a tool. Kubes also builds YAML, but it also provides additional features.
 
 Kustomize lets you customize your Kubernetes YAML files with additional `kustomization.yaml` files. The kustomization.yaml files contain configs that tell `kubectl` how to decorate existing Kubernetes YAML files in a template-free way.