Cloud Devops Automation

  Issue:-  When trying to delete the topic in the Amazon MSK kafka clusterr got the following error Error:-    ERROR Uncaught exception in thread 'kafka-admin-client-thread | adminclient-1': (org.apache.kafka.common.utils.KafkaThread) java.lang.OutOfMemoryError: Java heap space Effect:- Was not able to delete the Topic in the MSK kafka cluster due to the above error message. ERROR Uncaught exception in thread 'kafka-admin-client-thread | adminclient-1': (org.apache.kafka.common.utils.KafkaThread) java.lang.OutOfMemoryError: Java heap space at java.base/java.nio.HeapByteBuffer.<init>(HeapByteBuffer.java:61) at java.base/java.nio.ByteBuffer.allocate(ByteBuffer.java:348) at org.apache.kafka.common.memory.MemoryPool$1.tryAllocate(MemoryPool.java:30) at org.apache.kafka.common.network.NetworkReceive.readFrom(NetworkReceive.java:112) at org.apache.kafka.common.network.KafkaChannel.receive(KafkaChannel.java:424) at org.apache.kafka.common.network.KafkaChannel.r...

  Issue:-  After creating a service when I tried to verify if the DNS name for the service is getting resolved or I got the following error.  Error:-   my-service.default.svc: Name or service not known Effect:- I was unable to confirm if the service DNS was actually resolving or not and if there was some issue as the service itself was not accessible via curl or the browser [centos@kubemaster service]$ nslookup my-service.default.svc -bash: nslookup: command not found [centos@kubemaster service]$ dig nslookup my-service.default.svc -bash: dig: command not found [centos@kubemaster service]$ ping nslookup my-service.default.svc ping: my-service.default.svc: Name or service not known [centos@kubemaster service]$ ping my-service.default.svc ping: my-service.default.svc: Name or service not known Resolution:- Follow the following steps 1. Create a pod with the DNS utils installed on it for making the nslookup command work inside the pod kubect...

  Issue:-  When creating the simple resource like pod, replicaset, deployments etc got a groupVersion error specified below.  Error:-   groupVersion shouldn't be empty Effect:- Not able to create the resource because of the above error apiversion: v1 kind: Pod metadata: name: pod2 spec: containers: - name: c1 image: nginx Resolution:- If you look at the above configuration precisely you will find the  apiversion   has been specified incorrectly. It should have been  apiVersion   k.So just a difference of block letter can make that error. The same error will occur even if you forgot to mention the apiVersion in the configuration or it is misspelled. Below configuration will work fine. apiVersion: v1 kind: Pod metadata: name: pod2 spec: containers: - name: c1 image: nginx   Explanation:- apiVersion is hardcoded in the kubernetes. So if you misspell it, not use it or make a e...