Kubernetes/AKS CIs not progressing to End of Life despite Kubernetes Visibility agent reporting Install Status = Absent<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Issue Kubernetes and AKS class CIs discovered by the Kubernetes Visibility agent (KVA) do not progress to an end-of-life state even though the integration reports Install Status = Absent. Life Cycle Sync has been run and no conflicting mappings exist. Symptoms AKS / Kubernetes CIs remain active in the CMDB after KVA reports Install Status = AbsentEnable Life Cycle Sync has been run but the CIs do not move to End of LifeNo existing Life Cycle Mapping is present for Install Status = Absent Cause Out of the box, there is no Life Cycle Mapping that drives End of Life from Install Status = Absent. The OOB mapping drives End of Life only from Install Status = Retired. End of Life is a two-field pair (Life Cycle Stage = End of Life and Life Cycle Stage Status = Retired), not a single field, so an Absent status alone does not transition the CI. Resolution Do not rely on a direct Install Status = Absent to End of Life mapping for ephemeral Kubernetes CIs, as pod churn will cause the CIs to thrash between states.Instead, configure a CMDB Data Manager retirement policy that filters on Absent CIs not discovered for a defined number of days, then retires them.Confirm the retirement policy sets both Life Cycle Stage = End of Life and Life Cycle Stage Status = Retired.Validate that affected CIs transition to End of Life after the retirement policy runs.