Kuibernetes cmdb_ci_linux_server CI is optionalDescriptionSome customers reuse server names frequently and they would like to disable creating cmdb_ci_linux and cmdb_ci_win_server records by Kubernetes patterns.Since Kubernetes pattern can't discover serial_number server CIs will be identified by names only which will cause unwanted merges due to hostname recycling.The solution is to introduce a MID server property which will control server CIs creation. The default value will be true which will make sure the defaultbehavior won't change. If somebody sets the value to false Kubernetes patterns will stop creating server CIs.Steps to Reproduce 1. Discover Kubernetes 2. Destroy Kubernetes Cluster Node 3. Create a new VM and reuse the hostname 4. Run Discovery 5. ServiceNow won't be aware the VM has been replaced by the new VM.WorkaroundCommit the attached update set if you Discovery and Service Mapping Pattern version is older than August 2024 (sys_remote_update_set_6693d3ee3bf9461028726c1c95e45a91.xml)By deflault Kubernetes will create cmdb_ci_linux_server CI (MID Server Property sn_itom_pattern.kubernetes_create_server = true)If you decide to prevent cmdb_ci_linux_server CIs creation you will set MID Server Property sn_itom_pattern.kubernetes_create_server = falseUpdate MID configurationRe-run discoveryRelated Problem: PRB1757488