save HTTPS cert information in k8s configmap

Currently, HTTPS cert files are not managed in k8s configmap. They only take effects in ./paictl.py service start. This causes problems like:

• Every time the admin starts dev-box, he/she should manually copy certs into it.
• If there are many admins, and one admin updates the cert, then other admins won't be noticed.

Proposal for this issue:

In services-configuration.yaml, save the crt_name and key_name in the cluster field:

cluster:
  crt_name:
  key_name:

Then:

• When paictl.py config push:
  • If cluster.crt_name and cluster.key_name are available:
    • Find the files, and save the files in k8s configmap.
    • If the files are missing, throw an error
  • If cluster.crt_name and cluster.key_name are not available:
    • Do nothing but warn the user if he uses pylon.ssl field.
• When ./paictl config pull:
  • If there are certs in configmap, pull them to <config folder>
• When ./paictl.py service start:
  • Prefer certs in configmap. But certs in file system is also feasible.

Start with services-configuration.yaml and trace the paictl.py config push, config pull, and service start entry points. Check how the cluster fields, pylon.ssl, local certificate files, and Kubernetes ConfigMaps are currently handled. Done means push stores or warns correctly, pull restores available certificates, and service start prefers ConfigMap certificates while retaining filesystem support.