Our DEV instance is unable to start up on Kuberneters pods. When trying to restart the pods we are getting the below error:

WebAppLifeCycleListener] Log4j Shutdownhook disabled Current "user.dir" (default directory) is: / Current pega.logdir is: /usr/local/tomcat/logs/xxxx-pega-batch-6569bc8486-xtpqd Located PegaRULES logging configuration: file:/usr/local/tomcat/webapps/prweb/WEB-INF/classes/prlog4j2.xml WARNING: sun.reflect.Reflection.getCallerClass is not supported. This will impact performance. 2025-06-06 09:00:37,602 main ERROR Unable to locate appender "JSONAppender" for logger config "root" Unable to locate PegaRULES old logging configuration after trying: <properties>         pegauser-prlogging.xml         xxxx-pega-batch-6569bc8486-xtpqd-prlogging.xml         prlogging.xml {"source_host":"xxxx-pega-batch-6569bc8486-xtpqd","level":"INFO","thread_name":"main","appender_ref":"PEGA","logger_name":"com.pega.pegarules.web.servlet.WebAppLifeCycleListener","message":"System Start Date: Fri Jun 06 09:00:52 UTC 2025","version":1,"timestamp":"2025-06-06T09:00:53.819Z"} xtpqd","level":"INFO","thread_name":"main","appender_ref":"PEGA","logger_name":"com.pega.pegarules.priv.context.web.WebEnvironment","message":"Web tier using local JNDI context\nfactory = org.apache.naming.java.javaURLContextFactory\n    url = <not specified>\n   path = java:","version":1,"timestamp":"2025-06-06T09:01:02.083Z"} {"source_host":"xxxx-pega-batch-6569bc8486-xtpqd","level":"INFO","thread_name":"main","appender_ref":"PEGA","logger_name":"com.pega.pegarules.priv.context.JNDIEnvironment","message":"Web-tier default Engine bean name is EngineBMT","version":1,"timestamp":"2025-06-06T09:01:02.084Z"} {"source_host":"xxxx-pega-batch-6569bc8486-xtpqd","level":"INFO","thread_name":"main","appender_ref":"PEGA","logger_name":"com.pega.platform.modules.internal.ModulesBridgeImpl","message":"Initializing engine modules.","version":1,"timestamp":"2025-06-06T09:02:35.134Z"}

Can this be due to any rule configuration changes in Pega Instance? We tried to verify if there were any configuration level changes but none was the case and the environment was up and running till recently until this issue started. So, any insights will help us here.