<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Kubernetes on Opslifeuk Limited</title><link>https://opslife.co.uk/kubernetes/</link><description>Recent content in Kubernetes on Opslifeuk Limited</description><generator>Hugo -- gohugo.io</generator><language>en-gb</language><lastBuildDate>Sun, 07 Jun 2020 00:29:48 +0100</lastBuildDate><atom:link href="https://opslife.co.uk/kubernetes/index.xml" rel="self" type="application/rss+xml"/><item><title>Kubernetes Resource Limits and JVM Heap Size</title><link>https://opslife.co.uk/kubernetes/memory/</link><pubDate>Sat, 13 Jun 2020 17:40:34 +0100</pubDate><guid>https://opslife.co.uk/kubernetes/memory/</guid><description>By default, the JVM&amp;rsquo;s maximum heap size is 1/4 of the physical memory available - you can read about this in the Oracle GC tuning guide. This means that if you don&amp;rsquo;t define -Xmx in your JVM parameters, the container will set 1/4 of the host memory as the maximum heap size.
On a recent enough JVM (8u191+ and 10+), the JVM is container-aware: if you set a Kubernetes resource limit, the JVM uses that limit rather than the host&amp;rsquo;s memory to size the heap.</description></item><item><title>Kubernetes Service Accounts and Secrets - Mounting Secrets as Volumes</title><link>https://opslife.co.uk/kubernetes/secrets/</link><pubDate>Fri, 12 Jun 2020 14:00:33 +0100</pubDate><guid>https://opslife.co.uk/kubernetes/secrets/</guid><description>A Service Account provides an identity for processes that run in a pod. When processes inside a pod contact the API server, they are authenticated as a particular Service Account.
Create a Service Account using the YAML below.
apiVersion: v1 kind: ServiceAccount metadata: name: sa-app-name namespace: namespace-name Once the Service Account is created, you can reference it in your pod spec:
apiVersion: v1 kind: Pod metadata: name: app-name spec: serviceAccountName: sa-app-name Now on to Kubernetes Secrets.</description></item></channel></rss>