Add k8s master code

[lixiaoyuner]

Why I did it

Currently, k8s master image is generated from a separate branch which we created by ourselves, not release ones. We need to commit these k8s master related code to master branch for a better way to do k8s master image build out.

Work item tracking

• Microsoft ADO (number only):
  19998138

How I did it

• Install k8s dashboard docker images
• Install geneva mds and mdsd and fluentd docker images and tag them as latest, tagging latest will help create container always with the latest version
• Install azure-storage-blob and azure-identity, this will help do etcd backup and restore.
• Install kubernetes python client packages, this will help read worker and container state, we can send these metric to Geneva.
• Remove mdm debian package, will replace it with the mdm docker image
• Add k8s master entrance script, this script will be called by rc-local service when system startup. we have some master systemd services in compute-move repo, when VMM service create master VM, VMM will copy all master service files inside VM, the entrance script will setup all services according to the service files.
• When the entrance script content changed, the PR build will set include_kubernetes_master=y to help do validation for k8s master related code change. The default value of include_kubernetes_master should be always n for public master branch. We will generate master image from internal master branch

How to verify it

Build with INCLUDE_KUBERNETES_MASTER = y

Which release branch to backport (provide reason below if selected)

• 201811
• 201911
• 202006
• 202012
• 202106
• 202111
• 202205
• 202211

Tested branch (Please provide the tested image version)

Description for the changelog

Link to config_db schema for YANG module changes

A picture of a cute animal (not mandatory but encouraged)