My journey to Certified Kubernetes Administrator (CKA)

The Journey Is More Important Than the Destination.

  • CKA is the most touching exam I have passed.
  • The Journey Is More Important Than the Destination.
  • Fastest practice skills are crutial.
  • Have fun.

My tips

Use kubectl Cheat Sheet

Kubectl autocomplete – BASH

source <(kubectl completion bash) # setup autocomplete in bash into the current shell, bash-completion package should be installed first.
echo "source <(kubectl completion bash)" >> ~/.bashrc # add permanently

You can also use a shorthand alias for kubectl that also works with completion:

alias k=kubectl
complete -F __start_kubectl k

Kubectl apply 

kubectl apply -f ./my-manifest.yaml            # create resource(s)

Interacting with running Pods

# Run pod nginx and write its spec into a file called pod.yaml
kubectl run nginx --image=nginx --dry-run=client -o yaml > pod.yaml

#Better usage with $do
export do="–dry-run=client -o yaml"
kubectl run nginx --image=nginx $do > pod.yaml

Great Vim

vi ~/.vimrc
set ts=2 sw=2 expandtab ruler

Use tmux

A Ctrl+B Cheat Sheet

Session Commands
  • S: List sessions.
Window Commands
  • C: Create a new window.
  • N: Move to the next window.
  • P: Move to the previous window.
Pane Commands
  • %: Create a horizontal split.
  • “: Create a vertical split.
  • X: Close the current pane.

Cisco UCS Manager Plugin for VMware vSphere HTML Client (Version 3.0(6))

Cisco has released the 3.0(6) version of the Cisco UCS Manager VMware vSphere HTML client plugin. The UCS Manager vSphere HTML client plugin enables a virtualization administrator to view, manage, and monitor the Cisco UCS physical infrastructure. The plugin provides a physical view of the UCS hardware inventory on the HTML client.

I notify BUG “Host not going into monitoring state vCenter restart”. Thank You for fix.

Release 3.0(6)

Here are the new features in Release 3.0(6):

  • Custom fault addition for proactive HA monitoring
  • Resolved host not going into monitoring state vCenter restart
  • Included defect fixes

VMware vSphere HTML Client Releases

Cisco UCS Manager plug-in is compatible with the following vSphere HTML Client releases:

VMware vSphere HTML Client VersionCisco UCS Manager Plugin for VMware vSphere Version
6.73.0(1), 3.0(2), 3.0(3), 3.0(4), 3.0(5), 3.0(6)
7.03.0(4), 3.0(5), 3.0(6)
7.0u1, 7.0u23.0(5), 3.0(6)

Note
VMware vSphere HTML Client Version 7.0u3 is not supported.
More info here.

Extreme Performance Series – VMware+NVIDIA AI…

Extreme Performance Series – VMware+NVIDIA AI Enterprise vGPU Benchmarks

Extreme Performance Series – VMware+NVIDIA AI…

Mark Achtemichuk talks with Uday Kurkure about VMware+NVIDIA AI Enterprise with vGPUs attaining new MLPerf benchmarks as a showcase of performance. Links to additional resources mentioned in the video: VMware and NVIDIA Solutions deliver high performance in machine learning workloads – https://blogs.vmware.com/performance/2021/10/vmware-and-nvidia-solutions-deliver-high-performance-in-machine-learning-workloads.html Machine Learning on Virtualized Accelerators – https://blogs.vmware.com/performance/2021/10/accelerating-and-maximizing-the-performance-of-a-telco-workload-using-virtualized-gpus-in-vmware-vsphere.html Extreme Performance Series 2021 Video Blogs -…Read More


VMware Social Media Advocacy

Updated Plan for CPU Support Discontinuation In Future Major vSphere Releases after 7.0 (82794)

During instalation vSphere 7.0 Update 2 and later we can see new message for Haswell and Broadwell CPUs.

This is the warning message shown by the ESX installer:

CPU_SUPPORT_WARNING: The CPUs in this host may not be supported in future ESXi releases. Please plan accordingly.
Summary for warnings
  • vSphere 7.0
    • onwards for Intel Sandy Bridge, Intel Ivy Bridge-DT CPUs and AMD Bulldozer CPUs.
  • Sphere 7.0 Update 2 and later
    • onwards for Intel Haswell,Broadwell, Avoton CPUs and AMD Piledriver CPUs

I wish we could solve this in the future major release with – How to fix? The CPU in this host is not supported by ESXi 7.0.0. -> allowLegacyCPU=True

Table 1: VMware vSphere Planned Intel CPU Support Discontinuation List

VCG CPU Series NameCPU InfoRaw CPUIDsCode Name
Intel Xeon E3-1200 Series6.2A0x000206A0Intel Xeon E3 (Sandy Bridge)
Intel Xeon E3-1100 Series6.2A0x000206A0Intel Xeon E3 (Sandy Bridge)
Intel Xeon E5-1600 Series6.2D0x000206D0SandyBridge-EP WS
Intel Xeon E5-2600 Series6.2D0x000206D0SandyBridge-EP 2S
Intel Xeon E5-1400 Series6.2D0x000206D0SandyBridge-EN
Intel Xeon E5-4600 Series6.2D0x000206D0SandyBridge-EP 4S
Intel Xeon E5-2400 Series6.2D0x000206D0SandyBridge-EN
    
Intel i7-3600-QE6.3A0x000306A0IvyBridge-DT
Intel Xeon E3-1200-v2 Series6.3A0x000306A0IvyBridge-DT
Intel i7-3500-LE/UE6.3A0x000306A0IvyBridge-DT
Intel i3-3200 Series6.3A0x000306A0IvyBridge-DT
Intel Pentium B925C6.3A0x000306A0IvyBridge-DT- Gladden
Intel Xeon E3-1100-C-v2 Series6.3A0x000306A0IvyBridge-DT- Gladden
Intel Xeon E5-1600-v2 Series6.3E0x000306E0IvyBridge EP
Intel Xeon E5-2600-v2 Series6.3E0x000306E0IvyBridge EP
Intel Xeon E5-2400-v2 Series6.3E0x000306E0IvyBridge-EN
Intel Xeon E5-1400-v2 Series6.3E0x000306E0IvyBridge-EN
Intel Xeon E5-4600-v2 Series6.3E0x000306E0IvyBridge-EP 4S
Intel Xeon E7-8800/4800/2800-v26.3E0x000306E0IvyBridge-EX
    
Intel i7-4700-EQ Series6.3C0x000306C0Haswell-DT
Intel Xeon E3-1200-v3 Series6.3C0x000306C0Haswell-DT
Intel i5-4500-TE Series6.3C0x000306C0Haswell-DT
Intel i3-4300 Series6.3C0x000306C0Haswell-DT
    
Intel Xeon E5-1600-v3 Series6.3F0x000306F0Haswell-EP
Intel Xeon E5-2600-v3 Series6.3F0x000306F0Haswell-EP
Intel Xeon E5-1400-v3 Series6.3F0x000306F0Haswell-EN
Intel Xeon E5-2400-v3 Series6.3F0x000306F0Haswell-EN
Intel Xeon E5-4600-v3 Series6.3F0x000306F0Haswell-EP
Intel Xeon E7-8800/4800-v3 Series6.3F0x000306F0Intel Haswell-EX
    
Intel Xeon E3-1200-v4 Series6.470x00040670Broadwell-DT
Intel Core i7-5700EQ6.470x00040670Broadwell-H
    
Intel Atom C2700 Series6.4D0x000406D0Intel Avoton 8c
Intel Atom C2300 Series6.4D0x000406D0Intel Avoton 2c
Intel Atom C2500 Series6.4D0x000406D0Intel Avoton 4c

Table 2: VMware vSphere Planned AMD CPU Support Discontinuation List

VCG CPU Series NameCPU InfoRaw CPUIDsCode Name
AMD Opteron 6200 Series15.010x00600F10Interlagos BullDozer G34
AMD Opteron 4200 Series15.010x00600F10Valencia BullDozer C32
AMD Opteron 3200 Series15.010x00600F10Zurich AM3
AMD Opteron 4300 Series15.020x00600F20Piledriver-C32 (seoul)
AMD Opteron 3300 Series15.020x00600F20Piledriver-AM3 (Dehli)
AMD Opteron 6300 Series15.020x00600F20PileDriver-G34 (Abu Dhabi)
AMD Opteron X2250 Series15.300x00630F00Steamroller-Berlin
AMD Opteron X1250 Series15.300x00630F00Steamroller-Berlin
AMD Opteron X1100 Series16.000x00700F00Kyoto
AMD Opteron X2100 Series16.000x00700F00Kyoto

Links:

Extreme Performance Series – vGPU for Machine…

Extreme Performance Series – vGPU for Machine Learning on VMware vSphere

Extreme Performance Series – vGPU for Machine…

Mark Achtemichuk talks with Hari Sivaraman about how VMware uses Machine Learning internally and how to decide the best mode for running your vGPUs. Links to additional resources mentioned in the video: MIG or vGPU Mode for NVIDIA Ampere GPU: Which One Should I Use? https://blogs.vmware.com/performance/2021/09/mig-or-vgpu-part1.html VMware and NVIDIA Solutions deliver high performance in machine learning workloads – https://blogs.vmware.com/performance/2021/10/vmware-and-nvidia-solutions-deliver-high-performance-in-machine-learning-workloads.html Machine Learning on Virtualized Accelerators -…Read More


VMware Social Media Advocacy

A New Chapter for VMware: Spin‑Off from Dell…

A New Chapter for VMware: Spin‑Off from Dell…

VMware and Dell Technologies today announced the completion of the spin-off of VMware from Dell Technologies. The spin-off from Dell Technologies provides VMware increased freedom to execute its multi-cloud strategy, a simplified capital structure and governance model, and additional operational and financial flexibility


VMware Social Media Advocacy

How to fix vCenter password expiration “Exception in invoking authentication handler User password expired”

The Appliance was deployed more than 90 days ago with default settings. Logging in to the VAMI page of a vCenter (https://:5480) fails with the message “Exception in invoking authentication handler User password expired”

Login to the VCSA Appliance Shell (SSH or VM Console) is working.

Check password expiration
root@localhost [ ~ ]# chage -l root
You are required to change your password immediately (password expired)
chage: PAM: Authentication token is no longer valid; new one required
Change password
root@localhost [ ~ ]# passwd root
New password:
Retype new password:
passwd: password updated successfully
Change expiration – use it only for LABs …
root@localhost [ ~ ]# chage -M -1 root

Verify password expiration

root@localhost [ ~ ]# chage -l root
Last password change : Dec 21, 2021
Password expires : never
Password inactive : never
Account expires : never
Minimum number of days between password change : 0
Maximum number of days between password change : -1
Number of days of warning before password expires : 7

Links: