blog.kaniski.eu I just wanna learn!

8Sep/200

Having fun with Helm and file encoding

Had some spare time, so I've tried to learn a bit more about Helm, the package manager for Kubernetes.

I've decided to follow the relatively new Pluralsight course called - Kubernetes Package Administration with Helm, done by my MVP colleague Andrew Pruski. And it was great - not too long, clear and easy to follow, with only a handful of prerequisites if you want to follow along! Great job!

Of course, there is also the nice, official documentation.

But why am I writing this post?

I was normally following this course on my Windows 10 laptop, using Visual Studio Code, as suggested, and also using PowerShell terminal, with Helm v3.3.1.

It all went well until the part when we are creating our Helm Chart, more specifically - when we're filling up our deployment.yaml and service.yaml files. Suggested (and simplest) method is to use the simple output redirection (with ">"), like this:

But, this gave me the following error when trying to deploy the chart:

It's quite obvious - Helm works with UTF-8, and my .yaml files seem to be encoded differently. Quick look at the bottom of my VSCode confirms it:

How can I fix it?

As I'm using PowerShell, it's pretty easy - instead of doing the simple output redirection (">"), I pipe output to Out-File cmdlet with -Encoding UTF8 option, in all cases, which takes care of the encoding (and sets it to UTF-8 with BOM, which is just fine for Helm):

So, long story short - if you run into the error above ("Error: unable to build kubernetes objects from release manifest: error parsing : error converting YAML to JSON: yaml: invalid leading UTF-8 octet"), remember to check your file's encoding (and change it to UTF-8, if needed)! 🙂

Cheers!

P.S. Thanks to good people at Pluralsight for providing me a complimentary subscription!

3Nov/140

Hosts have “Needs Attention” status after installing the VMM 2012 R2 UR4

For those who installed the Update Rollup 4 for System Center 2012 R2 Virtual Machine Manager, you may be facing this somewhat “strange issue” right after the installation – your hosts will have the “Needs Attention” status.

image

And now the “strange” part – if you open the host Properties window, and check the Status tab, you’ll may see that everything is green.

image

So, what needs the attention then?
The answer is – VMM agent needs the attention, and that’s the cause of this “issue” (you’ll need to run Update Agent action on affected hosts).

image

And, finally, status of your hosts should be OK again.

image

Hope this helps!

P.S. Read the KB document thoroughly – there is a part which mentions the manual update of System Center Virtual Machine Manager DHCP Server (x64) component. It should be like this:

image

15May/140

Latest “Patch Tuesday” – errors installing update

Latest “Patch Tuesday” (May 13th, 2014) has brought us a pack of updates (you can read all the details about them here and here), but one of them was making trouble for me. The update I’m talking about is called “Security Update for Windows Server 2012 R2 (KB2920189)”. You can read more about this update in KB2920189.

I’ve tried to install it on a number of my Hyper-V virtual machines (Generation 2), but the update keeps failing with error 800F0922:

image

ISSUE:
This error and its cause is described in
KB2962824. In short, this update expects that the BitLocker feature is installed (not enabled or used, but installed) – in my case, the problem was Secure Boot, which is enabled by default on Generation 2 virtual machines.

RESOLUTION/WORKAROUND:
You can install the BitLocker feature on your Windows Server 2012 R2 servers before installing this update, or you can switch the Secure Boot off, install the update and switch it back on (I’ve decided to do the latter).

After switching the Secure Boot off, installing the update and switching it on again, the update installed successfully:

image

Have fun!