Nimble Storage Array 660x495

Nimble Storage – How to configure a device from scratch (Using the CLI)

The other day, I posted about how to setup a volume on a Nimble Storage device, so this post is a bit backwards, as now we look at setting up a device from scratch using the CLI first rather than the Nimble Discovery tool. Lets get started; 1. Rack your device, cable it up, and … Continue reading Nimble Storage – How to configure a device from scratch (Using the CLI)

site announcement

HP Chassis and Virtual Connect Firmware Upgrades – Don’t bother

So last night was a busy one thanks to the HP Chassis and “fantastic” Virtual Connect system. Bare with this article, as its part what happens blah blah, and part, how to install firmware on Virtual Connect The environment So the environment consists of; HP C7000 Chassis 6 x HP BL460c Blade Servers 2 x … Continue reading HP Chassis and Virtual Connect Firmware Upgrades – Don’t bother

helm header image

Helm upgrade –reuse-values Fails with Nil Pointer Error After a Chart Version Bump

If you have been running a Helm chart for a while and using –reuse-values to carry your previous configuration forward on upgrades, you may have hit an error like the one below after bumping to a new chart version: Running the same upgrade with an explicit values file works without issue: Read on to understand … Continue reading Helm upgrade –reuse-values Fails with Nil Pointer Error After a Chart Version Bump

Cisco Live Header

Bridging Old Hypervisors to Cloud Native Platforms: What You’ll Learn at Cisco Live Amsterdam

Are you planning or already facing a migration from legacy hypervisors to modern, cloud native platforms? The toughest part usually isn’t compute or storage, it’s networking. If static IPs, subnet constraints, and complex topologies are slowing you down, Cisco Live Amsterdam is the place to fix that. This year, I’m delivering two brand-new sessions focused … Continue reading Bridging Old Hypervisors to Cloud Native Platforms: What You’ll Learn at Cisco Live Amsterdam

Kubernetes Header Image

How to Increase CPU & Memory Limits and Set Node Selector for Splunk Operator on Kubernetes

The Issue When deploying a Splunk instance using the Splunk Operator on Kubernetes, the default resource limits are set to 4 CPUs and 8GB of RAM. Users often want to increase these limits to better utilize available hardware resources. Additionally, users may want to schedule the Splunk pods on a specific Kubernetes node by using … Continue reading How to Increase CPU & Memory Limits and Set Node Selector for Splunk Operator on Kubernetes