None of the examples in the Kubernetes documentation for liveness and readiness probes specify a timeoutSeconds field. It’s NOT that the documentation doesn’t address this attribute — it definitely does. But you have to read… you can’t just cut-and-paste! Why should you bother understanding timeoutSeconds? Well, you may find that…

Namespaces are NOT just for clusters with “a few to tens of users”… Sometimes in life we get incorrect advice. The source of the advice may be well-meaning, but no one is perfect. Point in case — the documentation for Kubernetes Namespaces states “For clusters with a few to tens of users, you should not need to create or think about namespaces at…

On Windows, install (if necessary) “Remote Server Administration Tools (RSAT)” Then run nltest /DCLIST:<domainname> You should see the list of domain controllers. For example: c:\>nltest /DCLIST:example.com Get list of DCs in domain ‘example.com’ from ‘\\sv12345h.example.com’. sv2345a.example.com [DS] Site: Site01 sv12345b.example.com [DS] Site: Site03 sv12345c.example.com [DS] Site: Site05 sv12345d.example.com [DS] Site: Site01 sv12345e.example.com [DS] Site: Site04 sv12345f.example.com [DS] Site: Site01 sv12345g.example.com [DS] Site: Site06 sv12345h.example.com [DS] Site: Site01 sv12345i.example.com [PDC] [DS] Site: Site01 sv12345j.example.com [DS] Site: Site01 sv12345k.example.com [DS] Site: Site01 sv12345l.example.com [DS] Site: Site01 The command completed successfully

First, please consider enhancing your application so that it doesn’t require session affinity! The Problem If you absolutely must move forward with session affinity using Ingress-NGINX Controller, you may find that it doesn’t work initially. Consider the following Ingress object: apiVersion: networking.k8s.io/v1 kind: Ingress metadata: name: helloworld-deployment-ingress annotations: nginx.ingress.kubernetes.io/rewrite-target…

Sometimes, you may find that your Kubernetes application doesn’t work properly when you first run more than 1 replica. In my experience, this is most frequently because the application is “Pod-stateful” — for example, the application may store session state in memory or is writing data required during subsequent requests…

Part 1 of this series can be found here. Part 2 of this series can be found here. Part 3 of this series can be found here. ConfigMapGenerator Creating ConfigMaps is a bit of a pain, particularly when you want to create it from a file. You have to put the…

Part 1 of this series can be found here. Part 2 of this series can be found here. Part 4 of this series can be found here. Avoid naming conflicts when deploying multiple applications to the same Namespace with nameSuffix and namePrefix In general, you should try to avoid deploying multiple applications (or application instances) to the same Namespace. To clarify, deploying different components of…

When using a TimeBasedRollingPolicy in Logback, it seems to be fairly common that it doesn’t operate as expected. One setting in particular seems to be a bit misleading — maxHistory. For example, consider the following policy: <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy"> <fileNamePattern>/logs/api-%d{yyyy-MM-dd}.%i.log.json.gz </fileNamePattern> <timeBasedFileNamingAndTriggeringPolicy class="ch.qos.logback.core.rolling.SizeAndTimeBasedFNATP"> …

The day-to-day demands of your job might be causing you to miss seeing opportunities or risks that would otherwise be obvious. Take a look at this short video. Can a gorilla be invisible? Maybe. Or perhaps more accurately, under certain circumstances it might be invisible to you. When you focus…