Authing DocsDocuments
Concept
workflow
Guides
Development Integration
Application integration
Concept
workflow
Guides
Development Integration
Application integration
Old Version
Guides
  • Quick start

  • Authenticate the user

  • Authority management for users

  • Authorization

  • Manage user accounts

  • Manage User Directory

  • Management Application

  • Become a source of federal authentication identity

  • Connect to an external identity provider (IdP)

  • Open up WeChat ecology
  • Migrate users to Authing

  • Management organization

  • Expandable capabilities

  • Audit Log

  • Configure security information

  • Configure user pool information

  • Deployment plan

    • Basic deployment mode
    • Docker deployment mode
    • Kubernetes deployment mode
    • Custom Domain Name Configuration Scheme
  • Frequently Asked Questions FAQs

  1. Guides
  2. /
  3. Deployment plan
  4. /
  5. Kubernetes deployment mode

¶ Kubernetes Deployment

Update Time: 2025-02-18 09:00:47
Edit

¶ Overview

Authing will not change the user's existing cloud infrastructure, Authing will be as much as compatible with the user's cloud environment. Therefore, Authing proposed the concepts of "Cloud Neutrality" and "Authing Inside". Authing can maintain it's neutral characteristics in a multi-cloud environment, and it can be deployed in AWS, Tencent Cloud, Alibaba Cloud or private cloud environments.In a hybrid cloud or private cloud environment, Authing will be integrated into the customer's IT system like Intel. This article will introduce the Kubernetes-based deployment plan and specific operation guidance of the Authing IDaaS platform.

¶ Overall structure

The high-availability architecture of the Authing IDaaS platform is running in VPC (virtual private cloud), through LB (load balancing), multi-availability server clusters in the same region are virtualized into a high-performance and highly available service pool as a whole. Based on load balancing Rules, the request from the client is distributed to the availability zone in the service pool.

Each availability zone is composed of a set of Kubernetes Nodes, and each availability zone is equipped with a complete set of Authing IDaaS platform. IDaaS cluster is a stateless service, while the database cluster is a stateful master-slave synchronization architecture. If a server appears in a certain availability zone fails or the server is unavailable, LB will transfer the traffic to another available zone, which will also assign the role of master cluster. Load balancing will detect the health status of each availability zone in real time, and automatically isolate the availability zones with abnormal states, thereby improving the overall service capabilities of the application.

Deployment plan

1. Component planning

serverComponent packageFunction Description
ElasticSearchelasticsearch-7.7.0Search engine, log service
Authing ServerAuthing-server-1.2.0Authing main service
Redisredis-4.0.0Cache service
PostgreSQLpostgres-12.5Database service
Logstashlogstash-7.7.0Log collection and analysis service
JDBC-Riverjdbc-logstash-river:1.0.0Background data service
StaticfilesAuthing-staticfiles:1.0.0Static resource service

2. System environment requirements

During the software installation, configuration, and commissioning process, a Kubernetes cluster needs to be prepared. The cluster requirements are as follows:

Kubernetes version requirements:

projectversion
Client Versionv1.19.4 and above
Server Versionv1.18.3 and above

Docker version requirements:

projectversion
Client19.03.14 and above
Server19.03.14 and above

Operating system environment requirements:

projectMinimum configurationRecommended configuration
Operating system platformlinux/amd64-
Kernel versionlinux 3.10.0 and above-

Kubernetes Master node configuration requirements:

projectMinimum configurationRecommended configuration
CPUX86 64 bit 2 coresX86 64 bit 4 cores
RAM8 GB and above16 GB and above
hard disk500 GB1 TB
Intranet bandwidth1 Gbps10 Gbps

Kubernetes Worker node configuration requirements:

projectMinimum configurationRecommended configuration
CPUX86 64 bit 4 coresX86 64 bit 8 core
RAM16 GB and above32 GB and above
hard disk1 TB5 TB
Intranet bandwidth1 Gbps10 Gbps

3. Related Documents

nameDescription
"Authing IDaaS Platform User Guide Version 1.2.0"Introduce Authing IDaaS platform operation guide
"Authing IDaaS Platform Product Documentation Version 1.2.0"Introduce Authing IDaaS platform product features

Note: Please contact the pre-sales staff for the above resources

4. Installation package

nameDescription
Authing-jdbc-logstash-river-1.0.0-90875fa84d87.tarAuthing back-end data service image package
Authing-server-1.2.0-32d8b4130bae.tarAuthing main service image package
Authing-staticfiles-1.0.0-a70a58e3c115.tarStatic resource service image package
elasticsearch-7.7.0-7ec4f35ab452.tarSearch and data statistics service mirror package
logstash-7.7.0-30dcca1db5e9.tarLog collection and analysis service image package
postgres-12.5-386fd8c60839.tarDatabase service mirroring package
redis-4.0.0-3189e099eb0f.tarCache service image package

Note: Please contact the pre-sales staff for the above resources

5. Compose files

nameDescription
namespace.yamlNamespace orchestration file
Authing-jdbc-logstash-river-deployment.yamlAuthing back-end data service orchestration file
Authing-server--deployment.yamlAuthing main service orchestration file
Authing-staticfiles-deployment.yamlStatic resource service orchestration file
elasticsearch-deployment.yamlSearch, data statistics service layout file
logstash-deployment.yamlLog collection, analysis service orchestration file
postgres-deployment.yamlDatabase Service Orchestration File
redis-deployment.yamlCache service orchestration file

Note: Please contact the pre-sales staff for the above resources

Prev: Docker deployment mode Next: Custom Domain Name Configuration Scheme
  • Overview
  • Overall structure

User identity management

Integrated third-party login
Mobile phone number flash check (opens new window)
Universal login form component
Custom authentication process

Enterprise internal management

Single Sign On
Multi-factor Authentication
Authority Management

Developers

Development Document
Framework Integration
Blog (opens new window)
GitHub (opens new window)
Community User Center (opens new window)

Company

400 888 2106
sales@authing.cn
16 / F, Block B, NORTH STAR CENTURY CENTER, Beijing(Total)
room 406, 4th floor, zone B, building 1, No. 200, Tianfu Fifth Street, Chengdu(branch)

Beijing ICP No.19051205-1

© Beijing Steamory Technology Co.