tree: a5f4f3b4cff5f456433f8da26361d664d13cf6d5 [path history] [tgz]
  1. delete.sh
  2. ingress-nginx-controller.yaml
  3. ingress.yaml
  4. init.sh
  5. linkis-bml-configmap.yaml
  6. linkis-bml-deployment.yaml
  7. linkis-dsm-server-configmap.yaml
  8. linkis-dsm-server-deployment.yaml
  9. linkis-eureka-configmap.yaml
  10. linkis-gateway-configmap.yaml
  11. linkis-gateway-deployment.yaml
  12. linkis-gateway-service.yaml
  13. linkis-mdm-server-configmap.yaml
  14. linkis-mdm-server-deployment.yaml
  15. linkis-mdm-service-es-configmap.yaml
  16. linkis-mdm-service-es-deployment.yaml
  17. linkis-mdm-service-hive-configmap.yaml
  18. linkis-mdm-service-hive-deployment.yaml
  19. linkis-mdm-service-mysql-configmap.yaml
  20. linkis-mdm-service-mysql-deployment.yaml
  21. linkis-metadata-configmap.yaml
  22. linkis-metadata-deployment.yaml
  23. linkis-publicservice-configmap.yaml
  24. linkis-publicservice-deployment.yaml
  25. linkis-resourcemanager-configmap.yaml
  26. linkis-resourcemanager-deployment.yaml
  27. linkis-ujes-hive-enginemanager-configmap.yaml
  28. linkis-ujes-hive-enginemanager-deployment.yaml
  29. linkis-ujes-hive-entrance-configmap.yaml
  30. linkis-ujes-hive-entrance-deployment.yaml
  31. linkis-ujes-jdbc-entrance-configmap.yaml
  32. linkis-ujes-jdbc-entrance-deployment.yaml
  33. linkis-ujes-mlsql-entrance-configmap.yaml
  34. linkis-ujes-mlsql-entrance-deployment.yaml
  35. linkis-ujes-pipeline-enginemanager-configmap.yaml
  36. linkis-ujes-pipeline-enginemanager-deployment.yaml
  37. linkis-ujes-pipeline-entrance-configmap.yaml
  38. linkis-ujes-pipeline-entrance-deployment.yaml
  39. linkis-ujes-python-enginemanager-configmap.yaml
  40. linkis-ujes-python-enginemanager-deployment.yaml
  41. linkis-ujes-python-entrance-configmap.yaml
  42. linkis-ujes-python-entrance-deployment.yaml
  43. linkis-ujes-shell-enginemanager-configmap.yaml
  44. linkis-ujes-shell-enginemanager-deployment.yaml
  45. linkis-ujes-shell-entrance-configmap.yaml
  46. linkis-ujes-shell-entrance-deployment.yaml
  47. linkis-ujes-spark-enginemanager-configmap.yaml
  48. linkis-ujes-spark-enginemanager-deployment.yaml
  49. linkis-ujes-spark-entrance-configmap.yaml
  50. linkis-ujes-spark-entrance-deployment.yaml
  51. README.MD
  52. register.yaml
  53. scriptis.yaml
k8s/README.MD

Linkis on kubernetes

#重点解决问题 1.每个人在部署过程中,都会遇到包冲突,操作系统不兼容,openjdk,hotspot jdk兼容问题,docker交付可以从根本上解决这些问题

2.docker基于cgroup资源隔离,共享文件系统,namespace 可以轻量限制计算资源,秒级扩缩容 例如:限制某个进程只能使用CPU一个核的20%资源 cd /sys/fs/cgroup/cpu touch test $ echo 10000 > cpu.cfs_quota_us $ echo 50000 > cpu.cfs_period_us 启动一个进程,请不要在生产做这样操作!!!!
$ while :; do :; done & 记录当前进程Id $ echo pid >> tasks

#部署文档

环境变量设置

设置harbor的地址环境变量

export HARBOR=

##基础镜像及各服务镜像编译方法 registry.yaml 修改对应harbor的账号,密码,镜像内网地址 基础镜像基于centos最新版本 目录结构如下 --linkis --emr-base --Dockerfile --README.MD --hadoop --etc --conf -- hdfs-site.xml -- yarn-site.xml -- map-red.xml ... -- hive --conf -- jdk-8u211-linux-x64.tar.gz -- scala-2.11.0.tgz -- spark-2.4.4-bin-hadoop2.7.tgz

###基础镜像编译 cd emr-base docker build -t $HARBOR/library/linkis:emr-base-spark2.4.4 . 推送基础镜像到harbor docker push $HARBOR/library/linkis:emr-base-spark2.4.4

###编译各微服务镜像 各个微服务basedir下面有对应module 的dockerfile 与公司内部的CI/CD集成,可以通过mvn docker插件直接编译docker 镜像 编译 Linkis 根目录执行 mvn clean package -f gateway/gateway-ujes-support/pom.xml docker images | grep linkis-gateway 可以看到已经编译好的镜像 docker push $HARBOR/library/linkis:linkis-gateway

#K8S部署 1.修改k8s目录下的docker secret register.yaml 镜像地址,账号,密码 2.修改k8s目录下的linkis-*- configmap.yaml 例如gateway/linkis.properties 复制到k8s/linkis-gateway-configmap.yaml 3.运行k8s 目录下的 sh init.sh