Revert "Templatizing priotityClassName, hostNetwork, and additionalLabels in node-daemonset.yaml"

[seanzatzdev-amazon]

Reverts #1281

Setting hostNetwork=False on the Node Daemonset will cause mounts to hang at upgrade time. See this Github issue:
#1270.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: seanzatzdev-amazon

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [seanzatzdev-amazon]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[aaroniscode]

@seanzatzdev-amazon I believe the issue referenced is only about changing hostNetwork from true to false or vice-versa. Creating a brand new install using hostNetwork: false should be fine. The original PR doesn't change the default so I'm not sure it creates an issue?

[levinedaniel]

Echoing @aaroniscode, we are actively using aws-efs-csi-driver with hostnet set to false. We have seen the break when switching, but upon a clean install and actively upgrading using just hostnet=false we have been operating fully functionally.

[seanzatzdev-amazon]

/lgtm

[k8s-ci-robot]

@seanzatzdev-amazon: you cannot LGTM your own PR.

In response to this:

/lgtm

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[mskanth972]

/lgtm

[Adityashar]

Hi @seanzatzdev-amazon

We faced an incident due to this change of hostNetwork: true post the upgrade to aws-efs-csi-driver-v3.0.6 helm chart.
Could we please revert this field back to a configurable field so that the users have an option to manually choose between enabling or disabling this option?

hostNetwork: {{ .Values.node.hostNetwork }}