<p>I am trying to set up hive using mr3 on a kubernetes cluster hosted on AWS ec2. When I run the command run-hive.sh, Hive-server starts and the master-DAg is initialised but then it gets stuck on pending. When I describe the pod. This is the error message shows. I have kept the resources to minimum so it should not be that issue and I do not have any tainted nodes. If you know any alternative for running hive on Kubernetes with access to S3 or a better way to implement mr3 hive on Kubernetes cluster, please share.</p>

<p><a href="https://i.stack.imgur.com/MR8Pi.png" rel="nofollow noreferrer">One of the node description</a></p>

Manik Malhotra
<p>Based on the topic i think the problem here is your cluster have not enough resources on your worker nodes, and a master node is <a href="https://kubernetes.io/docs/concepts/configuration/taint-and-toleration/" rel="nofollow noreferrer">tainted</a>.</p>
<p>So the option here is either inreasing the resources on workers or taint the master node so You would be able to schedule pods there.</p>
<blockquote>
<p>Control plane node isolation</p>
<p>By default, your cluster will not schedule pods on the control-plane node for security reasons. If you want to be able to schedule pods on the control-plane node, e.g. for a single-machine Kubernetes cluster for development, run:</p>
</blockquote>
<pre><code>kubectl taint nodes --all node-role.kubernetes.io/master-
</code></pre>
<blockquote>
<p>This will remove the node-role.kubernetes.io/master taint from any nodes that have it, including the control-plane node, meaning that the scheduler will then be able to schedule pods everywhere</p>
</blockquote>
