JumpServer-v2.20.0迁移到K8S运行

最新推荐文章于 2024-01-05 18:22:27 发布
最新推荐文章于 2024-01-05 18:22:27 发布
阅读量1k 收藏
点赞数
分类专栏： Kubernetes 文章标签： centos linux
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/qq_41586875/article/details/123755153
版权

JumpServer-v2.20.0迁移K8S运行

yaml: 相关链接：https://gitee.com/jiayu997/kubernetes/blob/master/Jumpserver-v2.20.0/Jumpserver.tar.gz

测试环境

主机
k8s-master-1192.168.0.10MASTER节点
k8s-node-1192.168.0.11WORK节点
k8s-nfs192.168.0.55提供NFS存储

实际效果

在这里插入图片描述
在这里插入图片描述

jms_configmap

[root@k8s-master-1 yaml]# cat jms_configmap.yaml 
apiVersion: v1
kind: Namespace
metadata:
  name: jms
---
apiVersion: v1
kind: ConfigMap
metadata:
  name: jms-config
  namespace: jms
data:
  MYSQL_DATABASE: "jumpserver"
  my.cnf: |
    [mysqld]
    basedir=/usr/
    datadir=/var/lib/mysql
    pid-file=/var/run/mysqld/mysqld.pid
    socket=/var/run/mysqld/mysqld.sock
    port=3306
    user=mysql
    log_error=/var/lib/mysql/mysql-error.log
    slow-query-log-file=/var/lib/mysql/mysql-slow.log
    log_bin=/var/lib/mysql/mysql-bin.log
    relay-log=/var/lib/mysql/mysql-relay-bin
    server-id=1
    innodb_buffer_pool_size=1024M
    innodb_log_buffer_size=16M
    key_buffer_size=128M
    query_cache_size=256M
    tmp_table_size=128M
    binlog_format=mixed 
    skip-external-locking
    skip-name-resolve
    character-set-server=utf8
    collation-server=utf8_bin
    max_allowed_packet=16M
    thread_cache_size=256
    table_open_cache=4096
    back_log=1024
    max_connect_errors=100000
    interactive_timeout=1800
    wait_timeout=1800
    max_connections=2048
    sort_buffer_size=16M
    join_buffer_size=4M
    read_buffer_size=4M
    read_rnd_buffer_size=16M
    binlog_cache_size=2M
    thread_stack=192K
    max_heap_table_size=128M
    myisam_sort_buffer_size=128M
    bulk_insert_buffer_size=256M
    open_files_limit=65535
    query_cache_limit=2M
    slow-query-log
    long_query_time=2
    expire_logs_days=3
    max_binlog_size=1000M
    slave_parallel_workers=4
    log-slave-updates
    binlog_ignore_db=mysql
    replicate_wild_ignore_table=mysql.%
    sync_binlog=1
    innodb_file_per_table=1
    innodb_flush_method=O_DIRECT
    innodb_buffer_pool_instances=4
    innodb_log_file_size=512M
    innodb_log_files_in_group=3
    innodb_open_files=4000
    innodb_read_io_threads=8
    innodb_write_io_threads=8
    innodb_thread_concurrency=8
    innodb_io_capacity=2000
    innodb_io_capacity_max=6000
    innodb_lru_scan_depth=2000
    innodb_max_dirty_pages_pct=85
    innodb_flush_log_at_trx_commit=2
    sql_mode=NO_ENGINE_SUBSTITUTION,STRICT_TRANS_TABLES
    [mysqldump]
    quick
    quote-names
    max_allowed_packet=16M
    [client]
    default-character-set=utf8
    [mysql]
    default-character-set=utf8
    [isamchk]
    key_buffer=128M
    sort_buffer_size=4M
    read_buffer=2M
    write_buffer=2M
    [myisamchk]
    key_buffer=128M
    sort_buffer_size=4M
    read_buffer=2M
    write_buffer=2M
  redis.conf: |
    daemonize no
    bind 0.0.0.0
    port 6379
    timeout 300
    loglevel notice
    databases 16
    save 900 1
    save 300 10
    save 60 10000
    dbfilename dump.rdb
    rdbcompression yes
    dir /data
    loglevel warning
    logfile "/data/redis.log"
    maxclients 20480
    maxmemory 2g
    maxmemory-policy allkeys-lru
    appendonly no
    appendfilename "appendonly.aof"
    appendfsync no
  nginx.conf: |
    server {
      listen 80;
      client_max_body_size 4096m;
  
      location /ui/ {
        try_files $uri / /index.html;
        alias /opt/lina/;
      }
      
      location /luna/ {
        try_files $uri / /index.html;
        alias /opt/luna/;
      }
  
      location /download/ {
         alias /opt/download/;
      }
  
      location /media/replay/ {
        add_header Content-Encoding gzip;
        root /opt/jumpserver/data/;
      }
  
      location /media/ {
        root /opt/jumpserver/data/;
      }
  
      location /static/ {
        root /opt/jumpserver/data/;
      }
  
      location /koko/ {
        proxy_pass http://jms-koko.jms.svc.cluster.local:5000; 
        proxy_buffering off;
        proxy_http_version 1.1;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection "upgrade";
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header Host $host;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
      }

      location /lion/ {
          proxy_pass http://jms-lion.jms.svc.cluster.local:8081;
          proxy_buffering off;
          proxy_request_buffering off;
          proxy_http_version 1.1;
          proxy_set_header Upgrade $http_upgrade;
          proxy_set_header Connection $http_connection;
          proxy_set_header X-Real-IP $remote_addr;
          proxy_set_header Host $host;
          proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
          proxy_ignore_client_abort on;
          proxy_connect_timeout 600;
          proxy_send_timeout 600;
          proxy_read_timeout 600;
          send_timeout 6000;
      }
  
      # 企业版才有该功能
      #location /omnidb/ {
      #    resolver 127.0.0.11 valid=30s;
      #    set $upstream http://omnidb:8082;
      #    proxy_pass $upstream$request_uri;
      #    proxy_buffering off;
      #    proxy_http_version 1.1;
      #    proxy_set_header Upgrade $http_upgrade;
      #    proxy_set_header Connection $http_connection;
      #    proxy_set_header X-Real-IP $remote_addr;
      #    proxy_set_header Host $host;
      #    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
      #}
  
      location /ws/ {
          proxy_pass http://jms-core.jms.svc.cluster.local:8070;
          proxy_buffering off;
          proxy_http_version 1.1;
          proxy_set_header Upgrade $http_upgrade;
          proxy_set_header Connection "upgrade";
          proxy_set_header X-Real-IP $remote_addr;
          proxy_set_header Host $host;
          proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
      }
  
      location /api/ {
          proxy_pass http://jms-core.jms.svc.cluster.local:8080;
          proxy_set_header X-Real-IP $remote_addr;
          proxy_set_header Host $host;
          proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
      }
  
      location /core/ {
          proxy_pass http://jms-core.jms.svc.cluster.local:8080;
          proxy_set_header X-Real-IP $remote_addr;
          proxy_set_header Host $host;
          proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
      }
  
      location / {
          rewrite ^/(.*)$ /ui/$1 last;
      }
    }
---
apiVersion: v1
kind: ConfigMap
metadata:
  name: jms-core-config
  namespace: jms
data:
  SECRET_KEY: "ZWNjNzRkNTYtYWVmOS1jMjE3LWRlNmEtNDI0Zjk2ZWMxYzJk"
  BOOTSTRAP_TOKEN: "ZWNjNzRkNTYtYWVmOS1jMjE3"
  LOG_LEVEL: "ERROR"
  #  MySQL 配置, USE_EXTERNAL_MYSQL=1 表示使用外置 MySQL, 请输入正确的 MySQL 信息
  USE_EXTERNAL_MYSQL: "1"
  DB_HOST: "jms-mysql.jms.svc.cluster.local"
  DB_PORT: "3306"
  DB_USER: "root"
  DB_PASSWORD: "jumpserver"
  DB_NAME: "jumpserver"
  ##  Redis 配置, USE_EXTERNAL_REDIS: 1 表示使用外置 Redis, 请输入正确的 Redis 信息
  USE_EXTERNAL_REDIS: "1"
  REDIS_HOST: "jms-redis.jms.svc.cluster.local"
  REDIS_PORT: "6379"
  REDIS_PASSWORD: "jumpserver"
  # Nginx 配置
  HTTP_PORT: "80"
  SSH_PORT: "2222"
  RDP_PORT: "3389"
  # Task 配置, 是否启动 jms_celery 容器, 单节点必须开启
  USE_TASK: "1"
  # XPack, USE_XPACK: 1 表示开启, 开源版本设置无效
  USE_XPACK: "0"
  # Core 配置, Session 定义, SESSION_COOKIE_AGE 表示闲置多少秒后 session 过期, SESSION_EXPIRE_AT_BROWSER_CLOSE: true 表示关闭浏览器即 session 过期
  # SESSION_COOKIE_AGE: 86400
  SESSION_EXPIRE_AT_BROWSER_CLOSE: "true"
  # Koko Lion XRDP 组件配置
  CORE_HOST: "http://jms-core.jms.svc.cluster.local:8080"
  # Lion 开启字体平滑
  JUMPSERVER_ENABLE_FONT_SMOOTHING: "true"
  # Nginx 文件上传大小
  CLIENT_MAX_BODY_SIZE: "4096m"
  # 终端使用宿主 HOSTNAME 标识
  SERVER_HOSTNAME: "${HOSTNAME}"
  # 额外的配置
  CURRENT_VERSION: "v2.20.0"

jms_secret

[root@k8s-master-1 yaml]# cat jms_secret.yaml 
apiVersion: v1
kind: Secret
metadata:
  name: jms-secret
  namespace: jms
data:                  #密码：echo -n "jumpserver" | base64
  MYSQL_ROOT_PASSWORD: "anVtcHNlcnZlcg=="
  REDIS_PASSWORD: "anVtcHNlcnZlcg=="
---

jms_mysql

[root@k8s-master-1 yaml]# cat jms_mysql.yaml 
apiVersion: apps/v1
kind: Deployment
metadata: 
  name: jms-mysql
  namespace: jms
spec:
  minReadySeconds: 30
  replicas: 1
  selector:
    matchLabels:
      app: jms-mysql
  template:
    metadata:
      name: jms-mysql
      labels:
        app: jms-mysql
    spec:
      restartPolicy: Always
      terminationGracePeriodSeconds: 30
      containers:
      - name: jms-mysql
        image: jumpserver/mysql:5
        imagePullPolicy: Never
        env:
        - name: MYSQL_DATABASE
          valueFrom:
            configMapKeyRef:
              name: jms-config
              key: MYSQL_DATABASE
        - name: MYSQL_ROOT_PASSWORD
          valueFrom:
            secretKeyRef:
              name: jms-secret
              key: MYSQL_ROOT_PASSWORD
        command: ["docker-entrypoint.sh"]
        args: ["--character-set-server=utf8"]
        readinessProbe:
          periodSeconds: 10
          failureThreshold: 3
          successThreshold: 1
          timeoutSeconds: 5
          initialDelaySeconds: 30
          exec: 
            command: ["/bin/bash","-c","mysql -h127.0.0.1 -P$DB_PORT -uroot -p$MYSQL_ROOT_PASSWORD -e 'SHOW DATABASES;'"]
        volumeMounts:
        - name: jms-nfs
          mountPath: /var/lib/mysql
        - name: jms-my-cnf
          mountPath: /etc/mysql
      volumes:
      - name: jms-nfs
        nfs:
          path: /Jumpserver/mysql
          server: 192.168.0.55
      - name: jms-my-cnf
        configMap:
          name: jms-config
          items:
          - key: my.cnf
            path: my.cnf
---
apiVersion: v1
kind: Service
metadata:
  name: jms-mysql
  namespace: jms
spec:
  type: ClusterIP
  clusterIP: None
  selector:
    app: jms-mysql
  ports:
  - name: jms-mysql-3306
    protocol: TCP
    port: 3306
    targetPort: 3306  
  - name: jms-mysql-33060
    protocol: TCP
    port: 33060
    targetPort: 33060

jms_redis

[root@k8s-master-1 yaml]# cat jms_redis.yaml 
apiVersion: apps/v1
kind: Deployment
metadata:
  name: jms-redis
  namespace: jms
spec:
  minReadySeconds: 30
  replicas: 1
  selector:
    matchLabels:
      app: jms-redis
  template:
    metadata:
      name: jms-redis
      labels:
        app: jms-redis
    spec:
      restartPolicy: Always
      terminationGracePeriodSeconds: 30
      containers:
      - name: jms-redis
        image: jumpserver/redis:6-alpine
        imagePullPolicy: Never
        env:
        - name: REDIS_PASSWORD
          valueFrom:
            secretKeyRef:
              name: jms-secret
              key: REDIS_PASSWORD
        command: ["/bin/sh","-c","redis-server /etc/redis.conf --requirepass $REDIS_PASSWORD"]
        readinessProbe:
          periodSeconds: 10
          failureThreshold: 3
          successThreshold: 1
          timeoutSeconds: 5
          initialDelaySeconds: 10
          exec:
            command: ["/bin/sh","-c","redis-cli -h 127.0.0.1 -p 6379 -a $REDIS_PASSWORD info Replication"]
        volumeMounts:
        - name: jms-nfs
          mountPath: /data
        - name: jms-redis-config
          mountPath: /etc/redis.conf
          subPath: redis.conf
      volumes:
      - name: jms-nfs
        nfs:
          path: /Jumpserver/redis
          server: 192.168.0.55
      - name: jms-redis-config
        configMap:
          name: jms-config
---
apiVersion: v1
kind: Service
metadata:
  name: jms-redis
  namespace: jms
spec:
  type: ClusterIP
  clusterIP: None
  selector:
    app: jms-redis
  ports:
  - protocol: TCP
    port: 6379
    targetPort: 6379

jms_core

[root@k8s-master-1 yaml]# cat jms_core.yaml 
apiVersion: apps/v1
kind: Deployment
metadata: 
  name: jms-core
  namespace: jms
spec:
  minReadySeconds: 90
  replicas: 1
  selector:
    matchLabels:
      app: jms-core
  template:
    metadata:
      name: jms-core
      labels:
        app: jms-core
    spec:
      restartPolicy: Always
      terminationGracePeriodSeconds: 30
      containers:
      - name: jms-core
        image: jumpserver/core:v2.20.0
        imagePullPolicy: Never
        tty: true
        envFrom:
        - configMapRef:
            name: jms-core-config
        command: ["/bin/bash","-c","python jms start web"] #command默认没带shell环境
        readinessProbe:
          periodSeconds: 10
          failureThreshold: 3
          successThreshold: 1
          timeoutSeconds: 5
          initialDelaySeconds: 90
          exec: 
            command: ["/bin/sh","-c","curl -fsL http://localhost:8080/api/health/ > /dev/null"]
        volumeMounts:
        - name: jms-nfs-data
          mountPath: /opt/jumpserver/data
        - name: jms-nfs-logs
          mountPath: /opt/jumpserver/logs
      volumes:
      - name: jms-nfs-data
        nfs:
          path: /Jumpserver/core/data
          server: 192.168.0.55
      - name: jms-nfs-logs
        nfs:
          path: /Jumpserver/core/logs
          server: 192.168.0.55
---
apiVersion: v1
kind: Service
metadata:
  name: jms-core
  namespace: jms
spec:
  type: ClusterIP
  clusterIP: None
  selector:
    app: jms-core
  ports:
  - name: jms-core-8070
    protocol: TCP
    port: 8070
    targetPort: 8070
  - name: jms-core-8080
    protocol: TCP
    port: 8080
    targetPort: 8080

jms_celery

[root@k8s-master-1 yaml]# cat jms_celery.yaml 
apiVersion: apps/v1
kind: Deployment
metadata:
  name: jms-celery
  namespace: jms
spec:
  minReadySeconds: 30
  replicas: 1
  selector:
    matchLabels:
      app: jms-celery
  template:
    metadata:
      name: jms-celery
      labels:
        app: jms-celery
    spec:
      restartPolicy: Always
      terminationGracePeriodSeconds: 30
      containers:
      - name: jms-celery
        image: jumpserver/core:v2.20.0
        imagePullPolicy: Never
        tty: true
        envFrom:
        - configMapRef:
            name: jms-core-config
        command: ["/bin/bash","-c","python jms start task"] #command默认没带shell环境
        readinessProbe:
          periodSeconds: 10
          failureThreshold: 3
          successThreshold: 1
          timeoutSeconds: 5
          initialDelaySeconds: 30
          exec:
            command: ["/bin/bash","-c","bash /opt/jumpserver/utils/check_celery.sh"]
        volumeMounts:
        - name: jms-nfs-data
          mountPath: /opt/jumpserver/data
        - name: jms-nfs-logs
          mountPath: /opt/jumpserver/logs
      volumes:
      - name: jms-nfs-data
        nfs:
          path: /Jumpserver/core/data
          server: 192.168.0.55
      - name: jms-nfs-logs
        nfs:
          path: /Jumpserver/core/logs
          server: 192.168.0.55
---
apiVersion: v1
kind: Service
metadata:
  name: jms-celery
  namespace: jms
spec:
  type: ClusterIP
  clusterIP: None
  selector:
    app: jms-celery
  ports:
  - name: jms-celery-8070
    protocol: TCP
    port: 8070
    targetPort: 8070
  - name: jms-celery-8080
    protocol: TCP
    port: 8080
    targetPort: 8080

jms_koko

[root@k8s-master-1 yaml]# cat jms_koko.yaml 
apiVersion: apps/v1
kind: Deployment
metadata:
  name: jms-koko
  namespace: jms
spec:
  minReadySeconds: 10
  replicas: 1
  selector:
    matchLabels:
      app: jms-koko
  template:
    metadata:
      name: jms-koko
      labels:
        app: jms-koko
    spec:
      restartPolicy: Always
      terminationGracePeriodSeconds: 30
      containers:
      - name: jms-koko
        image: jumpserver/koko:v2.20.0
        imagePullPolicy: Never
        tty: true
        envFrom:
        - configMapRef:
            name: jms-core-config
        readinessProbe:
          periodSeconds: 10
          failureThreshold: 3
          successThreshold: 1
          timeoutSeconds: 5
          initialDelaySeconds: 10
          exec:
            command: ["/bin/sh","-c","curl -fsL http://localhost:5000/koko/health/ > /dev/null"]
        volumeMounts:
        - name: jms-nfs-koko
          mountPath: /opt/koko/data
      volumes:
      - name: jms-nfs-koko
        nfs:
          path: /Jumpserver/koko/data
          server: 192.168.0.55
---
apiVersion: v1
kind: Service
metadata:
  name: jms-koko
  namespace: jms
spec:
  type: ClusterIP
  clusterIP: None
  selector:
    app: jms-koko
  ports:
  - name: jms-koko-2222
    protocol: TCP
    port: 2222
    targetPort: 2222
  - name: jms-koko-5000
    port: 5000
    targetPort: 5000

jms_lion

[root@k8s-master-1 yaml]# cat jms_lion.yaml 
apiVersion: apps/v1
kind: Deployment
metadata:
  name: jms-lion
  namespace: jms
spec:
  minReadySeconds: 10
  replicas: 1
  selector:
    matchLabels:
      app: jms-lion
  template:
    metadata:
      name: jms-lion
      labels:
        app: jms-lion
    spec:
      restartPolicy: Always
      terminationGracePeriodSeconds: 30
      containers:
      - name: jms-lion
        image: jumpserver/lion:v2.20.0
        imagePullPolicy: Never
        tty: true
        envFrom:
        - configMapRef:
            name: jms-core-config
        readinessProbe:
          periodSeconds: 10
          failureThreshold: 3
          successThreshold: 1
          timeoutSeconds: 5
          initialDelaySeconds: 10
          exec:
            command: ["/bin/sh","-c","curl -fsL http://localhost:8081/lion/health/ > /dev/null"]
        volumeMounts:
        - name: jms-nfs-lion
          mountPath: /opt/lion/data
      volumes:
      - name: jms-nfs-lion
        nfs:
          path: /Jumpserver/lion/data
          server: 192.168.0.55
---
apiVersion: v1
kind: Service
metadata:
  name: jms-lion
  namespace: jms
spec:
  type: ClusterIP
  clusterIP: None
  selector:
    app: jms-lion
  ports:
  - name: jms-lion-4822
    protocol: TCP
    port: 4822
    targetPort: 4822
  - name: jms-lion-8081 #dockerfile本身没有暴露该端口，但是由于nginx有流量转发到这里，所以开端口了
    protocol: TCP
    port: 8081
    targetPort: 8081

jms_nginx

[root@k8s-master-1 yaml]# cat jms_nginx.yaml 
apiVersion: apps/v1
kind: Deployment
metadata:
  name: jms-nginx
  namespace: jms
spec:
  minReadySeconds: 180
  replicas: 1
  selector:
    matchLabels:
      app: jms-nginx
  template:
    metadata:
      name: jms-nginx
      labels:
        app: jms-nginx
    spec:
      restartPolicy: Always
      terminationGracePeriodSeconds: 30
      containers:
      - name: jms-nginx
        image: jumpserver/web:v2.20.0
        imagePullPolicy: Never
        tty: true
        readinessProbe:
          periodSeconds: 10
          failureThreshold: 3
          successThreshold: 1
          timeoutSeconds: 5
          initialDelaySeconds: 50
          exec:
            command: ["/bin/sh","-c","curl -fsL http://localhost/ > /dev/null"]
        volumeMounts:
        - name: jms-core-data
          mountPath: /opt/jumpserver/data
        - name: jms-nginx-logs
          mountPath: /var/log/nginx
        - name: jms-nginx-config
          mountPath: /etc/nginx/conf.d/default.conf
          subPath: nginx.conf
      volumes:
      - name: jms-core-data
        nfs:
          path: /Jumpserver/core/data
          server: 192.168.0.55
      - name: jms-nginx-logs
        nfs:
          path: /Jumpserver/nginx/data/logs
          server: 192.168.0.55
      - name: jms-nginx-config
        configMap:
          name: jms-config
---
apiVersion: v1
kind: Service
metadata:
  name: jms-nginx
  namespace: jms
spec:
  type: ClusterIP
  clusterIP: None
  selector:
    app: jms-nginx
  ports:
  - name: jms-nginx
    protocol: TCP
    port: 80
    targetPort: 80

jms_ingress

[root@k8s-master-1 yaml]# cat jms_ingress.yaml 
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: jms-ingress
  namespace: jms
  annotations:
    kubernetes.io/ingress.class: "nginx"
    nginx.ingress.kubernetes.io/ssl-redirect: "true"
    nginx.ingress.kubernetes.io/proxy-body-size: "4096m"
    nginx.ingress.kubernetes.io/ssl-ciphers: "ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:DHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES256-GCM-SHA384"
spec:
  tls:
  - hosts:
    - www.jumpserver.com
    secretName: jms-ingress
  rules:
  - host: www.jumpserver.com
    http:
      paths:
      - backend:
          service:
            name: jms-nginx
            port:
              number: 80
        path: /
        pathType: Prefix

运行

[root@k8s-master-1 yaml]# kubectl apply -f jms_configmap.yaml 
namespace/jms created
configmap/jms-config created
configmap/jms-core-config created
[root@k8s-master-1 yaml]# kubectl apply -f jms_secret.yaml 
secret/jms-secret created
[root@k8s-master-1 yaml]# kubectl apply -f jms_mysql.yaml 
deployment.apps/jms-mysql created
service/jms-mysql created
[root@k8s-master-1 yaml]# kubectl apply -f jms_redis.yaml 
deployment.apps/jms-redis created
service/jms-redis created
[root@k8s-master-1 yaml]# kubectl apply -f jms_core.yaml 
deployment.apps/jms-core created
service/jms-core created
[root@k8s-master-1 yaml]# kubectl apply -f jms_celery.yaml 
deployment.apps/jms-celery created
service/jms-celery created
[root@k8s-master-1 yaml]# kubectl apply -f jms_koko.yaml 
deployment.apps/jms-koko created
service/jms-koko created
[root@k8s-master-1 yaml]# kubectl apply -f jms_lion.yaml 
deployment.apps/jms-lion created
service/jms-lion created
[root@k8s-master-1 yaml]# kubectl apply -f jms_nginx.yaml 
deployment.apps/jms-nginx created
service/jms-nginx created
[root@k8s-master-1 yaml]# kubectl apply -f jms_ingress.yaml 
ingress.networking.k8s.io/jms-ingress created

# 查看状态
[root@k8s-master-1 yaml]# kubectl get pods -n jms
NAME                         READY   STATUS    RESTARTS   AGE
jms-celery-b59bd98f8-m8wsz   1/1     Running   0          7m14s
jms-core-67ffc475b6-6hgps    1/1     Running   0          7m18s
jms-koko-69c9557bd6-4mzsz    1/1     Running   0          7m5s
jms-lion-7b57997486-n445g    1/1     Running   0          6m59s
jms-mysql-5898bb7d79-947gg   1/1     Running   0          7m27s
jms-nginx-cf4bf56f6-pfbv5    1/1     Running   4          6m52s
jms-redis-57b8b7b9f-8nchq    1/1     Running   0          7m23s
旺仔_牛奶
关注
  • 0
    点赞
  • 踩
  • 0
    收藏
    觉得还不错? 一键收藏
  • 打赏
    打赏
  • 0
    评论
专栏目录
K8S安装Jumpserver
彼岸吖的博客
04-11 1579
目录 一.Jumpserver介绍 二.安装Jumpserver K8S安装Jumpserver 源码安装Jumpserver 一.Jumpserver介绍 JumpServer 是全球首款开源的堡垒机，使用 GNU GPL v3.0 开源协议，是符合 4A 规范的运维安全审计系统。 JumpServer 使用 Python / Django 为主进行开发，遵循 Web 2.0 规范，配备了业界领先的 Web Terminal 方案，交互界面美观、用户体验好。 JumpServer 采纳
在k8s上部署Jumpserver
范一刀的博客
11-27 2792
0. 环境 本次演示环境使用metersphere版本：v1.13.0 设置k8s节点包括1台master和1台worker； 应用部署控制管理器使用deployment； 持久化存储使用hostPath写入到NFS挂载目录。 NFS挂载方式如下： 在master配置了nfs服务，并将nfs共享目录/nfs_storage挂在到了两个节点中的/opt/nfs; 如下图所示： 1. 导入镜像 将Jumpserver安装包中的镜像一次导入到系统中，或导入到harbor中； 此次演示环境没有配置harbor，直
EKS【k8s】集群使用helm部署 jumpServer
ma_qi_chao的博客
01-05 1047
【代码】EKS集群使用helm部署 jumpServer。
k8s集群部署jumpserver v3.3.1(helm)
qq_31292011的博客
12-11 1407
ReadWriteMany #注意，这里用ceph做动态存储的把这个参数改成ReadWriteOnce （单机访问，不然创建出来会报错，pvc），不止这里，下面还有。volume.beta.kubernetes.io/storage-class: "managed-nfs-storage" #这里改成自己的动态存储名。imageRegistry: "docker.io" # 千万别听他的用国内的，那真是一点都下载不下来。
subPathExpr 使用
运维那些事儿
12-02 1445
1、如下yaml文件 apiVersion: apps/v1 kind: Deployment metadata: annotations: deployment.kubernetes.io/revision: "7" generation: 7 labels: k8s-app: busybox qcloud-app: busybox managedFields: - apiVersion: apps/v1 manager: tke-apiserver
log4j-api-2.20.0.jar
04-21
log4j-api.jar 免费下载 如果不能免费下载，关注我，评论区联系我索要！
python3-requests-2.20.0-2.1.el8_1.noarch(1).rpm
12-06
官方离线安装包，亲测可用
编译好的dlt-viewer-2.20.0
10-27
【标题】"编译好的dlt-viewer-2.20.0" 是一个已经预先编译完成的软件版本，主要用于查看和分析DLT（Diagnostic Log and Trace）日志文件。DLT是一种广泛用于嵌入式系统和汽车电子行业的日志格式，它允许开发者收集、...
docker-compose-V2.20.2.tar.gz
最新发布
05-06
为了安装这个离线包，你需要解压“docker-compose”文件，然后将其放到Docker的安装目录下的bin文件夹里，或者将解压后的可执行文件路径添加到系统的PATH环境变量中，这样就可以在任何地方运行`docker-compose`命令...
fast-classpath-scanner-2.20.0.jar
06-01
优步快速、超轻量级的 Java 类路径和模块路径扫描器。 通过直接解析类文件二进制格式而不是使用反射来扫描类路径和模块路径。...io.github.lukehutch/fast-classpath-scanner/2.20.0/fast-classpath-scanner-2.20.0.jar
k8s-jumpserver:K8S容器版跳板机，POD自注册，还原传统体验 方便开发调试及线上问题排查。 国内仓库：
05-30
k8s-jumpserver K8S容器版跳板机，POD自注册，还原传统体验 方便开发调试及线上问题排查 一、部署拓扑 1.全内置： jumpserver无状态 2.Jumpserver外置，可与物理机混合管理，可管理多个K8S集群 二、Modules 1.jumpregister Jumpserver自注册 2.jumpserver 0.3.x版Jumpserver跳板机 3.alpine-ext:weak 轻量sshd (业务负载的基础镜像层) 三、快速开始 帐号信息 web: jumpadmin jumpadmin 端口:8888 ssh: jumpadmin jumpadmin 端口:2222 1.一条指令快速初始 (现有集群，jumpserver内置版) kc apply -k https://gitee.com/infrastlabs/k8s-jumpserver//deplo
kubernetes 部署jumpserver yaml 文件
10-27
下载后，在k8s集群执行 kubectl apply -f jumpserver.yaml 注意：pvc是自动创建，nodename 需要匹配自己集群中的node
K8S系列文章之 开源的堡垒机 jumpserver
Coder_Boy_的博客
08-06 1244
一、jumpserver作为一款开源的堡垒机，不管是企业还是个人，我觉得都是比较合适的，而且使用也比较简单。五、最后在说一下，可以使用堡垒机的2222端口，通过账号连接，也是比较方便的。资产添加不用细讲，主要是配置过程，举个例子，适用window系统，配置方式。四、jumpserver很不错的一个堡垒机/跳板机。目前没有看到3版本的，3版本的功能更加强大，可以官网学习一下。其他的资产和应用这里不讲，主要弄一下k8s的管理。1、安装，直接docker不是就行。a、在master节点，进行。
单点jumpserver结合ceph，在k8s下运行
xiaoqingyu123的博客
09-09 387
总结： 实现的效果，数据在ceph中持久化，单点jumpserver可以在k8s集群中任意node迁移。 前提说明： 1，有ceph集群环境 2，有k8s集群环境 创建pool ceph osd pool create jumpserver 36 36 注： 36 这个值根据实际情况，填写适当的大小。 初始化pool rbd pool init jumpserver 创建用户 ceph auth get-or-create client.jumpserver mon 'allow
jumpserver添加k8s集群
weixin_33669839的博客
11-01 2507
1、应用yaml文件 ①创建集群权限的SA ，并绑定ClusterRole：cluster-admin。 kubectl apply -f jumpserver-admin.yaml cat jumpserver-admin.yaml apiVersion: v1 kind: ServiceAccount metadata: name: jumpserver-admin namespace: kube-system --- kind: ClusterRoleBinding apiVer
搭建jumpserver
划水的银开的博客
04-04 928
环境 OS: centos 7.6 关闭selinux 关闭防火墙 准备python3 环境 安装依赖 yum -y install wget sqlite-devel xz gcc automake zlib-devel openssl-devel epel-release 下载包 wget https://www.python.org/ftp/python/3.6.1/Python-3.6...
JumpServer
mixboot
05-30 254
系列文章目录 JumpServer JumpServer系列文章目录前言一、JumpServer 搭建离线部署(amd64)安装启动二、使用步骤1.web访问三、配置参考 前言 JumpServer 堡垒机 一、JumpServer 搭建 离线部署(amd64) jumpserver-offline-installer-v2.22.1-amd64-204.tar.gz tar -zxvf jumpserver-offline-installer-v2.22.1-amd64-204.tar.gz
一站式部署Jumpserver
小健健的博客
12-28 540
博文大纲：一、Jumpserver简介二、安装Jumpserver准备环境三、配置Python 3环境四、安装Jumpserver五、安装mariadb、redis并配置jumpserver六、安装coco组件并配置七、安装guacamole及luna八、安装nginx九、客户端访问测试 一、Jumpserver简介 Jumpserver是全球首款完全开源的堡垒机，使用GNU GPL v2.0...
kubernetes离线部署jumpserver开源堡垒机
zhangkangren的博客
04-21 667
堡垒机介绍可以看官方网站：https://kuboard.cn/此文档只是部署前提条件：此文档两个部署在192.168.17.80，可以通过查找更改成自己的。2、redis 5下载镜像。
apiVersion: monitoring.coreos.com/v1 kind: Prometheus metadata: labels: prometheus: k8s name: k8s namespace: monitoring spec: alerting: alertmanagers: - name: alertmanager-main namespace: monitoring port: web image: quay.io/prometheus/prometheus:v2.20.0 nodeSelector: kubernetes.io/os: linux podMonitorNamespaceSelector: {} podMonitorSelector: {} replicas: 2 resources: requests: memory: 400Mi ruleSelector: matchLabels: prometheus: k8s role: alert-rules securityContext: fsGroup: 2000 runAsNonRoot: true runAsUser: 1000 serviceAccountName: prometheus-k8s serviceMonitorNamespaceSelector: {} serviceMonitorSelector: {} version: v2.20.0 请解释一下这个yaml文件
02-17
prometheus: k8s name: k8s namespace: monitoring spec: alerting: alertmanagers: - name: alertmanager-main namespace: monitoring port: web image: quay.io/prometheus/prometheus:v2.20.0 ...
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包

打赏作者

旺仔_牛奶

你的鼓励将是我创作的最大动力

¥1 ¥2 ¥4 ¥6 ¥10 ¥20
扫码支付：¥1
获取中
扫码支付

您的余额不足，请更换扫码支付或充值

打赏作者

实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值