<p>I am trying to understand the difference between Nginx ingress controller</p>
<pre><code>kind:service 
</code></pre>
<p>vs</p>
<pre><code>kind: Ingress
</code></pre>
<p>vs</p>
<pre><code>kind: configMap
</code></pre>
<p>in Kubernetes but a little unclear.
Is kind: Service same as Kind: Ingress in Service and Ingress?</p>

Jainam Shah
<p><strong>kind</strong> represents the type of Kubernetes objects to be created while using the <strong>yaml</strong> file.</p>
<blockquote>
<p><a href="https://kubernetes.io/docs/concepts/overview/working-with-objects/kubernetes-objects/" rel="nofollow noreferrer">Kubernetes objects</a> are persistent entities in the Kubernetes
system. Kubernetes uses these entities to represent the state of your
cluster. Specifically, they can describe:</p>
<ul>
<li>What containerized applications are running (and on which nodes)</li>
<li>The resources available to those applications</li>
<li>The policies around how those applications behave, such as restart    policies, upgrades, and fault-tolerance</li>
</ul>
<p><a href="https://kubernetes.io/docs/concepts/configuration/configmap/" rel="nofollow noreferrer">ConfigMap</a> Object: A ConfigMap is an API object used to store
non-confidential data in key-value pairs. Pods can consume ConfigMaps
as environment variables, command-line arguments, or as configuration
files in a volume.</p>
<p><a href="https://kubernetes.io/docs/concepts/services-networking/ingress/" rel="nofollow noreferrer">Ingress</a> Object: An API object that manages external access to the
services in a cluster, typically HTTP. Ingress may provide load
balancing, SSL termination and name-based virtual hosting.</p>
<p><a href="https://kubernetes.io/docs/concepts/services-networking/service/" rel="nofollow noreferrer">Service</a> Object: In Kubernetes, a Service is an abstraction which
defines a logical set of Pods and a policy by which to access them
(sometimes this pattern is called a micro-service).</p>
</blockquote>
