<p>When running this command for resources ( deployment, ReplicaSet ...) other than Pod</p>
<pre><code>$ kubectl describe deployment xxx-deployment 

----           ------  ------

Events:          &lt;none&gt;
</code></pre>
<p>I have deployed several resources, but I haven't seen the event yet except for Pod.</p>
<p>What type of event will occur if events occur in other resources?</p>
<p>Could you recommend any materials to refer to?</p>

H.jenny
<p>Good explanation what is event in <code>Kubernetes</code> you can find in <a href="https://www.bluematador.com/blog/kubernetes-events-explained#:%7E:text=Kubernetes%20events%20are%20a%20resource,be%20broadcast%20to%20the%20system.&amp;text=Get%20a%20free%20trial%20of%20Blue%20Matador%20Kubernetes%20monitoring%20software." rel="nofollow noreferrer">Types of Kubernetes Events</a> article. Author also mentioned about types of events.</p>
<blockquote>
<p>Kubernetes events are a resource type in Kubernetes that are automatically created when other resources have state changes, errors, or other messages that should be broadcast to the system. While there is not a lot of documentation available for events, they are an invaluable resource when debugging issues in your Kubernetes cluster.</p>
</blockquote>
<p>You can describe not only <code>pod</code>, <code>deployment</code> or <code>replicaset</code> but <strong>almost all</strong> resources in kubernetes.</p>
<p>Examples:</p>
<ul>
<li><code>kubectl describe job pi -n test</code></li>
</ul>
<pre><code>Events:
  Type    Reason            Age   From            Message
  ----    ------            ----  ----            -------
  Normal  SuccessfulCreate  12s   job-controller  Created pod: pi-5rgbz
</code></pre>
<ul>
<li><code>kubectl describe node ubuntu</code></li>
</ul>
<pre><code>Events:
  Type     Reason                   Age                 From                   Message
  ----     ------                   ----                ----                   -------
  Warning  MissingClusterDNS        22h (x98 over 23h)  kubelet, ubuntu-18     kubelet does not have ClusterDNS IP configured and cannot create Pod using &quot;ClusterFirst&quot; policy. Falling back to &quot;Default&quot; policy.
  Normal   Starting                 22h                 kubelet, ubuntu-18     Starting kubelet.
  Warning  InvalidDiskCapacity      22h                 kubelet, ubuntu-18     invalid capacity 0 on image filesystem
  Normal   NodeHasSufficientMemory  22h                 kubelet, ubuntu-18     Node ubuntu-18 status is now: NodeHasSufficientMemory
  Normal   NodeHasSufficientPID     22h    
</code></pre>
<p>To list all resources events you can use
<code>$ kubectl get events --all-namespaces</code></p>
<pre><code>$ kubectl get events --all-namespaces
NAMESPACE     LAST SEEN   TYPE      REASON                    OBJECT                                                           MESSAGE
default       50m         Normal    Starting                  node/gke-cluster-1-default-pool-XXXXXXXXXXXXX                    Starting kubelet.
default       50m         Normal    NodeHasSufficientMemory   node/gke-cluster-1-default-pool-XXXXXXXXXXXXX                    Node gke-cluster-1-default-pool-XXXXXXXXXXXXX status is now: NodeHasSufficientMemory
default       2m47s       Normal    SuccessfulCreate          job/pi                                                           Created pod: pi-5rgbz
kube-system   50m         Normal    ScalingReplicaSet         deployment/fluentd-gcp-scaler                                    Scaled up replica set fluentd-gcp-scaler-6855f55bcc to 1
</code></pre>
<p>In Object column you resource type.</p>
<p>If you would like more detailed information you can use <code>-o wide</code> flag - <code>$ kubectl get events --all-namespaces -o wide</code></p>
<pre><code>$ kubectl get events -o wide
LAST SEEN   TYPE      REASON                    OBJECT                                   SUBOBJECT                      SOURCE                     MESSAGE                                      
                                                                                                                                                                    FIRST SEEN   COUNT   NAME
20m         Normal    Scheduled                 pod/hello-world-86d6c6f84d-8qz9d                                        default-scheduler          Successfully assigned default/hello-world-86d
6c6f84d-8qz9d to ubuntu-18  
</code></pre>
<p>Possibly root cause.</p>
<p>I wasn't able to create deployment without any event at the beginning I would guess that you have set <code>--event-ttl</code> which is described in <a href="https://kubernetes.io/docs/reference/command-line-tools-reference/kube-apiserver/" rel="nofollow noreferrer">Kube-apiserver docs</a>.</p>
<p><code>--event-ttl duration     Default: 1h0m0s</code></p>
<blockquote>
<p>Amount of time to retain events.</p>
</blockquote>
<p>It was also mentioned in <a href="https://github.com/kubernetes/kubernetes/issues/52521" rel="nofollow noreferrer">Github thread</a>.</p>
<p><strong>In short, all events will disappear after 1 hour if you have this flag set.</strong></p>
<p>To check if you have this flag set in <code>kube-apiserver</code> you can check <a href="https://stackoverflow.com/a/50356764/11148139">this StackOverflow thread</a>.</p>
<p><strong>If this didn't help you please edit your question with informations like your configuration YAMLs, what version of K8s are you using, steps to reproduce etc.</strong></p>
