Blog Post Publish Date: 2026/07/09
Workstation Setup for Kubernetes Exams (CKA, CKAD & CKS)#
This blog post walks through the workstation optimizations I use to work more efficiently during the exam, including Vim configuration, Bash keybindings, shell aliases, and other tweaks that help reduce friction and save valuable time.
Time management is one of the most critical factors for passing the Linux Foundation Kubernetes certification exams. The CKA, CKAD, and CKS are hands-on exams conducted on remote Ubuntu instances running the XFCE desktop environment, where network latency and the remote desktop experience can slow you down. Check out the following tips to optimize your setup.
Configure the U.S. Keyboard Layout (MacBooks)#
If you’re taking the exam on a MacBook, make sure your keyboard layout is set to U.S.. Otherwise, the remote Linux environment may not recognize certain characters correctly, especially ~ and `. This is a common issue with layouts such as U.S. International - PC and Brazilian – ABNT2.
Before the exam, perform the following steps:
Open System Settings » Keyboard » Input Sources.
Add
U.S.input source.Remove any other input sources so only
U.S.remains.
This helps prevent unexpected keyboard mapping issues during the exam.
Disable Mission Control Shortcuts (MacBooks)#
By default, pressing CTRL + ←→ switches between macOS Spaces. During the exam, this can be interpreted by the proctor as leaving the exam environment, potentially triggering a warning or even interrupting your session.
Before the exam, perform the following steps:
Open System Settings » Keyboard » Keyboard Shortcuts.
Select Mission Control.
Disable all shortcuts under Mission Control.
This helps prevent accidental desktop switching and reduces the risk of unnecessary proctor alerts or exam suspension on suspicion of consulting unauthorized material.
Disable Window Tiling Apps (MacBook)#
If you use window tiling apps such as Rectangle or Magnet, it’s strongly recommended to disable/close them before the exam. Their keyboard shortcuts can conflict with the exam workstation, causing unexpected behavior when using shortcuts such as ⌘ + ↑↓←→.
History Search by Prefix#
This is probably my most valuable tip!
The exam environment uses Bash as the default shell. Behind the scenes, Bash relies on the GNU Readline library, which provides command-line editing, key bindings, and history navigation. For example, the interactive reverse search that appears when you press CTRL + R is implemented by GNU Readline.
One of Readline’s most useful features is history search by prefix, that is disabled by default. The history-search-backward and history-search-forward functions search your command history using the text that already exists before the cursor, instead of simply moving to the previous or next command.
For example, imagine your command history contains:
kubectl get pods
kubectl get nodes
kubectl describe pod nginx
helm list
If you type:
kubectl g
and press ↑, history-search-backward cycles only through commands that begin with kubectl g:
kubectl get nodes
kubectl get pods
Commands such as kubectl describe pod nginx or helm list are skipped because they do not match the typed prefix.
This is much faster than the default ↑ behavior, which walks through every command in your history, and often more convenient than repeatedly using CTRL + R during the exam.
To enable this behavior, create the ~/.inputrc file and add the following configuration:
"\e[A": history-search-backward # ↑ (previous matching command)
"\e[B": history-search-forward # ↓ (next matching command)
The file is automatically loaded whenever a new Bash session starts. If you modify it during an existing session, reload it with:
bind -f ~/.inputrc
Setting Up Vim#
The exam workstation includes VSCodium. However, every exam task requires you to connect to a remote node via SSH, and VSCodium is not available on those remote machines. In addition, the exam workstation often has high latency, making mouse operation unreliable, this is where Vim shines.
The following settings provide a much better editing experience for Kubernetes YAML manifests.
Create the ~/.vimrc file and add the following configuration:
set nu " Show line numbers
set ai " Preserve indentation while editing
set et " Convert tabs into spaces
set ts=2 " Display tabs as two spaces
set sw=2 " Indent and unindent using two spaces
set sts=2 " Make Tab and Backspace use two-space indentation
set hls " Highlight search matches
set cuc " Highlight the current cursor column
syntax on " Enable syntax highlighting
Avoid using set mouse=a due to the exam workstation’s high connection latency. Also, the clipboard settings with clipboard+=unnamedplus,autoselect does not work on the exam workstations.
I have created a blog post Vim for Kubernetes Certification Exams (CKA, CKAD & CKS) with editing techniques I use most frequently during exams.
Kubectl Aliases and Shortcuts#
Each remote exam node already contains a preconfigured ~/.bashrc file with several useful settings. A handy trick is to copy it to main workstation, append your own aliases, and then copy it back to the question nodes.
First, copy the ~/.bashrc from question node:
scp cks1234:~/.bashrc ~/.bashrc
Append the following aliases to the end of the file:
### omitted the .bashrc copied from question node
alias kgp="kubectl get pods"
alias kaf="kubectl apply -f"
alias kdel="kubectl delete --now"
alias kdelp="kubectl delete pod --now"
alias kns="kubectl config set-context --current --namespace"
alias kctx="kubectl config use-context"
export x="--dry-run=client -oyaml"
INFO: The
export xis useful shorthand for generating YAML in imperative kubectl commands such ask run nginx --image nginx:latest $x > nginx.yaml
Copy Settings to Exam Question Node#
All exam tasks are required to be performed on the remote question node via SSH. A convenient workflow is to create your configuration files once on the main instance and then copy them to the question node before starting the task.
scp ~/.inputrc ~/.vimrc ~/.bashrc cks1234:~/
ssh cks1234