Kubernetes is the latest the latest hotness when it comes to technology used on the Internet. It has a distinct advantage of some of the previous trends in that it is very easy to get started learning.
Kubernetes and Docker for Mac
Like many people who love technology, I have Docker for Mac installed on my computer at home as well as at work. Why do I bring this up? Because if you have kept the software up to date you also, already, have Kubernetes installed.
If you do not have Docker for Mac installed: Click here.
Open Preferences for Docker in your toolbar and you’ll notice a familiar icon on the top bar:
Next, all you need to do is click the box next to Enable Kubernetes and then the Apply button. Next you’ll see a small popup that Kubernetes needs to be installed, click Install. That’s all it takes and and Kuberentes version 1.10.11 is stating up. Note, that you may want to click on the General tab as well and provide more memory.
Chances are you already have a connection to another cluster, such as one in Google Compute Cloud. You can easily change back and forth between that and your new Docker installation using contexts.
Run kubectl config get-contexts and it will list all of the available options. One of which will be your new installation.
Now, to use your Docker installation run kubectl config use-context docker-for-desktop”
Next to double check that you’re up and running you can run something like kubectl describe nodes and look for a line which will say: OS Image: docker-for-desktop.
Minikube via Brew (Mac)
Installing Minikube on the Mac has a prerequisite in that you need a hypervisor. My recommendation is to go the free route and install Oracle’s VirtualBox.
Next up is to install Brew, if you do not already have it. I find this to be inavaluable installation on any Mac that I’m using.
After that all you need to do is run the following and Minikube will be installed!
brew cask install minikube
The following link will help you get started using Minikube!
Recently I started to get my hands dirty with learning more about DevStack which is a quick way to deploy OpenStack to test with. As with many of open source projects like OpenStack, OpenShift and Cloud Foundry I find the documentation often to be sorely lacking on specifics. In some cases I cannot explain why, in others it’s because they want you to use the paid version instead.
My stepup is on Ubuntu 18.04.1 and the local.conf that I used is below. All I can say is that this worked for me to just get it installed. How exactly functional after that I have not yet gotten to but hopefully this helps someone get started as well.
Note you will likely need to change the FLOATING_RANGE to match your network. The documentation is otherwise decent but I’ll include a few more getting started commands below:
sudo useradd -s /bin/bash -d /opt/stack -m stack
echo “stack ALL=(ALL) NOPASSWD: ALL” | sudo tee /etc/sudoers.d/stack
# Enable Swift
enable_service s-proxy s-object s-container s-account
# Enable sahara
enable_plugin sahara git://git.openstack.org/openstack/sahara
# Enable ceilometer
enable_plugin ceilometer git://git.openstack.org/openstack/ceilometer
# Check out from repos every time stack.sh is run
# This is optional and can be changed to no.
# By default `stack.sh` will only install Python packages if no versi# on is currently installed, or the current version does not match a # specified requirement. If `PIP_UPGRADE` is set to `True` then exist# ing #required Python packages will be upgraded to the most recent v# ersion #that matches requirements. This is generally recommended, # as most of # OpenStack is tested on latest packages, rather than ol# der versions.# The default is False.
# host ip
# Change the FLOATING_RANGE to whatever IPs VM is working in. In NAT # mode it is the subnet VMware Fusion provides, in bridged mode it is# your local network. But only use the top end of the network by usin# g a /27 and starting at the 224 octet.
# By default ``stack.sh`` output only goes to the terminal where it runs. It can be configured to additionally log to a file by setting ``LOGFILE`` to the full path of the destination log file. A timestamp will be appended to the given name.
# Old log files are automatically removed after 7 days to keep things neat. Change the number of days by setting ``LOGDAYS``.
# basic syslog settings
I started out in technical support back in 1997 and I am here today because of the time that others took to help me along the way. Over the past year, I have been working hard to step up my efforts to hopefully do the same for others. Thanks to a program at work I really got to dive into what it means to coach someone in the workplace. Sometimes for technical people, it’s easier to just do it for someone when they ask for help. Yet, while it may be easier and faster it provides no benefit to the other person.
So that being said, this might be a rambling mess, but, I’ll do my best.
So how do you start? You listen. One thing I think that many of us are guilty of sometimes in conversation is that we are just waiting for the other person to stop talking so we can. It is an amazing thing that when you’re describing your problem to someone, seeking their help, that it’s obvious there really paying attention.
Next? Don’t do it for them, don’t give them the full answer. They are not going to learn anything if you give them the full answer. Instead, trust in that you’re working with clever, intelligent people who just need a pointer.
Going back to someone listening. I cannot tell you how many times I’ve come up with the solution myself just having someone listen to me. Three quarters through my rambling I often suddenly stop and go, “Wait a minute, I think I figured it out.” I thank them for their time and they often wonder what it is they did. Verbalizing your problem is an amazing way to find a solution.
Redhat has recently been pushing their new developer portal pretty hard. They have finally, to little to late in some peoples minds, opened up Redhat Enterprise Linux to developers for no charge. Along with this, they have a series of excellent cheat sheets which for those still learning, or just cannot remember every little command I’ve found to be very helpful.