At every job I’ve held, the general opinion about self-reviews tends to fall into one of two categories. Either employees view them as arduous and frustrating or they simply don’t care about them. However, I believe that a well-written self-review can help you accelerate your career, whether your goal is a raise, a promotion, or merely some well-deserved recognition for your efforts. In this article, I’ll discuss my approach to performance reviews. While there is no one-size-fits-all strategy, this approach has served me well through several organizations and positions.
OUR BEST CONTENT, DELIVERED TO YOUR INBOX
Subscribe to our Feed
Here is a preview of what you'll see in your Feed Reader / inbox.
Use https://www.redhat.com/sysadmin/rss.xml for your favorite RSS reader.
If you have used relatively recent versions of OpenShift, you must have come across the
oc debug command (or you can check this man page). One of the interesting things about the new OpenShift is that it suggests not to use SSH directly (you can see this in
sshd_config on the nodes because they have PermitRootLogin no set on them). So if you were to run
oc debug node/node_name, it will create a pod for you and drop you in the shell (TTY) of this pod.
The only network numbers I can keep in my head are now and always have been a Class C network with a 24-bit netmask, such as 192.168.1.0/24. I know there are 254 usable host addresses available with a broadcast address of 192.168.1.255, a gateway/router address of 192.168.1.1 or 192.168.1.254 (depending on who's running the network), and a human-readable netmask of 255.255.255.0. That's my standard network. After all, 254 hosts are enough for any subnet, right? Wrong.
This year I started becoming familiar with Linux kernel namespaces, rootless containers, and the toolchain around Podman. In this article, I share my first experiences with beginners as well as developers, product managers, and solution architects so you all get to know how it feels to be a newbie to the container world.
Rootless Podman containers is a really cool feature that allows users to run almost all containers in their home directory without requiring any additional privileges.
Rootless containers take advantage of the user namespace, as I explained in this blog.
If you're already somewhat familiar with tmux and Irssi, feel free to just refer to the basic steps in the TL;DR section below. For more details and options, check out the more in-depth configuration steps farther down the page.
I'm sitting here one month into 2021 and I was thinking about the challenges that we faced in 2020 and how resilient the tech industry has been. The industry is nothing without the people who do the work. So that got me thinking, "How are people doing?"
I don't know about you but I don't like to reinstall my operating system. I find it a complete waste of my time for something that should just update in place. Some people, often using other platforms, prefer a good once-a-year wipe and reinstall to regain the original speed of their systems. I just don't subscribe to this point of view. There are many ways to maintain a system and I usually prefer some investigative debugging rather than wiping and hoping for the best.
The challenges of the past year have enabled us to do things differently, including the way one learns through online training and testing your skills through certification exams. These self-growth initiatives continue to help you further advance your knowledge and careers as sysadmins. These opportunities also positively impact your organizations.
cert-manager builds on top of Kubernetes, introducing certificate authorities and certificates as first-class resource types in the Kubernetes API. This feature makes it possible to provide Certificates as a Service to developers working within your Kubernetes cluster.
cert-manager is an open source project based on Apache License 2.0 provided by Jetstack. Since
cert-manager is an open source application, it has its own GitHub page.