<p>I was trying to do a configuration on my cluster and I found out that there's an object called NodeConfig with the tags</p>
<pre><code>apiVersion: acm.vmware.com/v1alpha1
kind: NodeConfig
spec:
  config: |
    nicNaming:
    - match:
        deviceLabel: Ethernet1
      targetName: XXXXX
    - match:
        deviceLabel: Ethernet2
      targetName: XXXXX
    - match:
        deviceLabel: Ethernet3
      targetName: XXXXX
</code></pre>
<p>Is suppose, ConfigMap does the same thing of doing or still there's a difference?</p>

Shoaib Mohammed
<p><code>NodeConfig</code> is the Custom Resource Definition (CRD) under Node Operator created by VMWare. According to the VMWare's definition <a href="https://docs.vmware.com/en/VMware-Telco-Cloud-Platform-5G-Edition/1.0/telco-cloud-platform-5G-edition-reference-architecture/GUID-8572C7D2-11D7-4800-A744-784B82A7CA48.html" rel="nofollow noreferrer">here</a>, <code>NodeConfig</code> is used for the definition in the Node under VMWare's Cloud Platform</p>
<p><code>ConfigMap</code> is a built-in Kubernetes object for storing the configuration you needed for application.</p>
<p>They are totally two different things in general. CRD is a way to extend the functionality of Kubernetes. There will be a custom controller for reconciliation, in other word, handling the CRUD logic of the resource. You can use your own controller to extend the feature under Kubernetes. In your case, VMWare uses the CRD to let you configure the Node within the cluster.</p>
