Update deployment files to support new architecture

[floreks]

TBD

[codecov]

Codecov Report

Merging #7544 (71775cb) into master (ce15290) will decrease coverage by 0.01%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##           master    #7544      +/-   ##
==========================================
- Coverage   42.19%   42.18%   -0.01%     
==========================================
  Files         218      218              
  Lines       12099    12099              
  Branches      179      179              
==========================================
- Hits         5105     5104       -1     
- Misses       6709     6710       +1     
  Partials      285      285              

[romdhanisam]

You can explain more about new architecture!

[marcosdiez]

From what I understood,
the main dashboard container will be split into two:

one for the backend and one for the frontend.

the backend will receive /api/* ( or /api/v1/*)
the rest should go to the frontent

that means a router will be needed in front of it, so the setup will be more complex.

[floreks]

@romdhanisam

You can explain more about new architecture!

@marcosdiez is correct.

From what I understood, the main dashboard container will be split into two:

one for the backend and one for the frontend.

the backend will receive /api/* ( or /api/v1/*) the rest should go to the frontent

that means a router will be needed in front of it, so the setup will be more complex.

We will utilize cert-manager and ingress-nginx to expose dashboard by default on a localhost domain. Since API and Web UI are in separate containers now we are using Ingress as a gateway that connects them together. In the future, we will probably use a dedicated gateway to leverage API and merge multiple API services into a single API. cert-manager is used to allow HTTPS access as it can generate self-signed cert used by ingress controller to expose the application.

kind: Ingress
apiVersion: networking.k8s.io/v1
metadata:
  labels:
    k8s-app: kubernetes-dashboard
  annotations:
    nginx.ingress.kubernetes.io/ssl-redirect: "true"
    cert-manager.io/issuer: selfsigned
  name: kubernetes-dashboard
spec:
  ingressClassName: nginx
  tls:
  - hosts:
    - localhost
    secretName: kubernetes-dashboard-certs
  rules:
  - host: localhost
    http:
      paths:
      - path: /
        pathType: Prefix
        backend:
          service:
            name: dashboard-web
            port:
              name: http
      - path: /api/v1
        pathType: Prefix
        backend:
          service:
            name: dashboard-api
            port:
              name: API

[maciaszczykm]

/lgtm

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: floreks, maciaszczykm

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 [floreks,maciaszczykm]

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