Remove rbenv and any rubies, gems etc.:
$ rm -rf ~/.rbenv
Uninstall rbenv if installed via Homebrew
$ brew uninstall rbenv
Remove references to rbenv in ~/.bash_profile
etc.
Remove rbenv and any rubies, gems etc.:
$ rm -rf ~/.rbenv
Uninstall rbenv if installed via Homebrew
$ brew uninstall rbenv
Remove references to rbenv in ~/.bash_profile
etc.
#!/bin/bash | |
# Author: Erik Kristensen | |
# Email: erik@erikkristensen.com | |
# License: MIT | |
# Nagios Usage: check_nrpe!check_docker_container!_container_id_ | |
# Usage: ./check_docker_container.sh _container_id_ | |
# | |
# Depending on your docker configuration, root might be required. If your nrpe user has rights | |
# to talk to the docker daemon, then root is not required. This is why root privileges are not |
Finding Packer-generated AMIs automatically after builds
The basic technique is to have Packer add a tag with a unique value during the build, and use AWS' built-in filtering capabilities to find that specific AMI after the build finishes.
Run this in order to backup all you k8s cluster data. It will be saved in a folder bkp. To restore the cluster, you can run kubectl apply -f bkp
.
Please note: this recovers all resources correctly, including dynamically generated PV's. However, it will not recover ELB endpoints. You will need to update any DNS entries manually, and manually remove the old ELB's.
Please note: This has not been tested with all resource types. Supported resource types include: