<p>We are investigating an issue that is related to slow pod startups on Azure Kubernetes Services.  Once the pod startup is complete, we are unable to see historical events.  The latest event log appears as <code>&lt;none&gt;</code>.</p>

<p>Here is an example:</p>

<pre class="lang-sh prettyprint-override"><code>sshuser@sandbox-ubuntu-vm:~$ kubectl get pods
NAME                                            READY   STATUS      RESTARTS   AGE
my-service-58bb6868c-rfrgr               1/1     Running     0          4h51m
sshuser@sandbox-ubuntu-vm:~$ kubectl describe pod my-service-58bb6868c-rfrgr
Name:           my-service-58bb6868c-rfrgr
Namespace:      default
Priority:       0
Node:           aks-myproject-41067869-1/10.0.1.163
Start Time:     Thu, 20 Feb 2020 05:25:36 -0500
Labels:         app.kubernetes.io/instance=my-service
                app.kubernetes.io/name=my-service
                pod-template-hash=58bb6868c
Annotations:    &lt;none&gt;
Status:         Running
IP:             10.0.1.183
IPs:            &lt;none&gt;
Controlled By:  ReplicaSet/my-service-58bb6868c
Containers:
  my-service:
    Container ID:   docker://b366fc6459f7dc03287d62da81c9fb1ed2c30ec0ccb4b601d2eea62e644de9f9
    Image:          myacr.azurecr.io/myproject/microservices/my-service:0.0.48
    Image ID:       docker-pullable://myacr.azurecr.io/myproject/microservices/my-service@sha256:cca04f3499271ac5ae383ddccba8c3f716b8f95cd0c06042ef4d7f69626beb8d
    Port:           3000/TCP
    Host Port:      0/TCP
    State:          Running
      Started:      Thu, 20 Feb 2020 05:32:38 -0500
    Ready:          True
    Restart Count:  0
    Liveness:       http-get http://:http/ delay=0s timeout=1s period=10s #success=1 #failure=3
    Readiness:      http-get http://:http/ delay=0s timeout=1s period=10s #success=1 #failure=3
    Environment:
      PORT:                          3000
    Mounts:
      /kvmnt from my-service-kv-volume (ro)
      /var/run/secrets/kubernetes.io/serviceaccount from my-service-token-lbfjg (ro)
Conditions:
  Type              Status
  Initialized       True
  Ready             True
  ContainersReady   True
  PodScheduled      True
Volumes:
  my-service-kv-volume:
    Type:       FlexVolume (a generic volume resource that is provisioned/attached using an exec based plugin)
    Driver:     azure/kv
    FSType:
    SecretRef:  &amp;LocalObjectReference{Name:kvcreds,}
    ReadOnly:   false
    Options:    map[REMOVED]
  my-service-token-lbfjg:
    Type:        Secret (a volume populated by a Secret)
    SecretName:  my-service-token-lbfjg
    Optional:    false
QoS Class:       BestEffort
Node-Selectors:  &lt;none&gt;
Tolerations:     node.kubernetes.io/not-ready:NoExecute for 300s
                 node.kubernetes.io/unreachable:NoExecute for 300s
Events:          &lt;none&gt;
sshuser@sandbox-ubuntu-vm:~$ kubectl get events --all-namespaces
No resources found
sshuser@sandbox-ubuntu-vm:~$
</code></pre>

<p>Is there a periodic purge for the event logs?  We are able to see events when the pod status is <code>ContainerCreating</code>, but then the events are not visible shortly after (unknown how long) the pod goes to a <code>Running</code> state.</p>

<p>The Kubernetes version is 1.14.8.</p>

<p>Any help is greatly appreciated.</p>

<p>Thanks.</p>

<p>Kubernetes has default time to retain event configured to 1hr in <strong>kube-apiserver</strong>. </p>

<p>You can configure the ttl of events by setting the flag <code>--event-ttl</code> durations  of <strong>kube-apiserver</strong>.</p>

<p><strong><a href="https://kubernetes.io/docs/reference/command-line-tools-reference/kube-apiserver/" rel="noreferrer">Find more on Kube-apiserver Documentation</a></strong></p>
