Developer Tools

Problem: The customer upgraded their Kubernetes cluster from version 1.19 to 1.24.8. Following this upgrade, they lost access to the PodPreset feature, which was removed in Kubernetes version 1.20. The customer needed a replacement for this functionality and identified Admission Webhooks as a potential solution. However, despite following RedHat’s procedure for implementing Admission Webhooks, the […]

Problem: Zipkin version 2.24.2 does not support Elasticsearch 8.x, which poses a significant obstacle as many of our clusters are already upgraded to Elasticsearch 8.x. This compatibility issue needs to be addressed to ensure seamless operation of our monitoring and tracing functionalities. Solution: Assessment and Documentation: Conducted thorough analysis and documented the current compatibility status […]

Problem: The kube-api pod was frequently restarting with the error message: apiserver received an error that is not a metav1.Status: rpctypes.EtcdError{code:0xe, desc:”etcdserver: request timed out”}. This issue began following an etcd data migration from a single-node Kubernetes cluster to a multi-node cluster using an unconventional method. Despite multiple attempts to resolve the issue, the problem […]

Problem: The client was operating Jenkins 2.344 on Apache Tomcat 8.5.41 and required redirection from port 8084 (HTTP) to port 8443 (HTTPS). Although the “server.xml” and “web.xml” files were configured in the $CATALINA_HOME/conf/ directory, leading to successful redirection from http://jenkins:8084 to https://jenkins:8443, accessing http://jenkins:8084/jenkins (the application) did not redirect to port 8443. The cancellation of […]

Problem: The client encountered a recurring issue within the Docker Swarm environment, wherein containers sporadically crashed with exit code 137. This behavior, indicative of potential memory-related issues, was exacerbated by the absence of corresponding container logs, complicating the diagnostic process. Process: Initial Inquiry and Investigation: Prompted by the client’s request for a Root Cause Analysis […]

Problem: The client reported sudden high CPU utilization on their RHEL 7.5 Nexus server. Despite disabling tasks and restarting the server, the issue persisted. Logs indicated that the Nexus process was the top contributor to CPU utilization. Process: Steps and measures undertaken to investigate the issue: Requesting Information: Furnished JVM logs, Nexus application logs, and […]

Title: Stabilizing Applications Amidst DNS Challenges: Tackling Intermittent Connection Issues in Kubernetes Problem: The customer is facing intermittent connection issues in their application, resulting in “connection refused” errors in the logs. These errors are linked to DNS resolution failures and connection timeouts. As a temporary fix, the customer is restarting the CoreDNS pod every hour, […]