Wei
1. If want to deploy the `ui`, we need to install npm on host machine, but it's better to deploy with container. 2. it's better to deploy `ui` with one...
So after this merged, we should build a image(in dir `opencost/ui`) based on the docker file: ```shell docker build -t quay.io/kubecost1/opencost-ui:latest -f Dockerfile ./ ``` And then push it
cc @jessegoodier
cc @Poor12 @lonelyCZ @XiShanYongYe-Chang @RainbowMango
cc @lonelyCZ
Other lgtm
cc @RainbowMango
/kind cleanup /remove-kind feature
Have a questison, why not define the `PropagatePriority` in `ReplicaScheduling`? If define in `ClusterAffinity`, if it's static weight scheduling strategy, the priority will works? @Garrybest
It must be the file of `ClusterAffinity`(Will it make customers confused because of scheduling strategy)? I think the only benifit is it can use label selector to give a priority...