DevOps Console Introduction
Service Overview
DevOps Console integrates standard development tools, making it easy to configure development environments and providing convenience for building and deploying, with the following features.
Key tool integration and unified authentication for Continuous Integration and Deployment (CI/CD Continuous Integration/Continuous Deployment)
Users can access tools responsible for source code repositories, artifact repositories, code analysis, image repositories, and build/deployment with a single login.
Project configuration based on application template
Users can easily configure a project using a wizard-style approach with templates that incorporate development standards.
Major development languages and frameworks provided
Users can select the development languages (Java, C#, Python, Ruby, etc.) and frameworks (SpringBoot, Vue.js, .Net, etc.) required for application development to configure a project for building and deployment.
Automatic Build/Deployment Pipeline Configuration
Users can automatically generate pipeline scripts using the build/deployment pipeline templates included in the application template, or configure each pipeline stage through a GUI-based approach.
Support for multiple deployment methods and rollback
Users can employ deployment strategies (RollingUpdate, Blue-Green) to minimize downtime of running applications, and can roll back to a desired version with a single click. If users wish to use a VM server as the deployment environment, they can deploy to the VM server in the form of packaged files or Docker images.
Custom Release Process Support
Users can define and repeatedly execute various release processes, taking into account the type of application changes.
Component
Users can easily use the DevOps Service through the DevOps Console.
DevOps Console
It provides integrated support for the tools required for application development and build/deployment, allowing easy management of project configuration and build/deployment.
Dev. Starter
It is an application template that provides not only sample code reflecting development standards but also integrated templates required for build and deployment.
IDP(ID Provider)
It manages users centrally and handles authentication.
Source Code Repository
Supports integration with source code version control tools.
Artifact Repository
Supports integration with an artifact repository for storing libraries required for application builds and application artifacts.
code quality
Supports integration with code quality tools that can measure and manage source code quality through static code analysis.
Helm chart repository
In Kubernetes, Helm charts are used to easily install and upgrade software. Users must create Helm charts themselves to install software. It provides ChartMuseum as the default repository for managing Helm charts. It also supports integration with other chart repository tools.
Image Repository
Supports integration with an image registry for storing container images.
VM Server Group
A group of VM servers that serve as the deployment target for the application. Users can register VMs and designate them as deployment targets in the DevOps Console.
Kubernetes Cluster
The cluster that serves as the deployment target for the application. Users can register a Kubernetes Cluster in the DevOps Console and designate it as a deployment target.
DevOps Console can be found in Tool Classification.Key concepts and relationships
System administrators (System Admin) or administrators (Admin) must predefine the tools and application templates required when a user creates a project.
tenant
It is a logical unit that independently provides and shares tools and application templates usable in projects. The system administrator registers a tenant for each organization (or client) unit that must guarantee independence and assigns a tenant administrator. The tenant administrator can register tenant tools, application templates, and tenant members that can be used within that tenant.
Project Group
As a unit for managing individual projects, a member belonging to a specific tenant can create a project group. Therefore, a project group belongs to a single tenant and can utilize the tools and templates configured for that tenant.
project
A project is a unit that develops and manages an application or microservice that is deployed and run independently. Consequently, it is common to structure a project around a single source code repository, but it can be flexibly organized according to the characteristics of the application or the development and operations teams.
tool
It is a development tool that supports source code repositories, image registries, build/deployment pipelines, and code quality used in projects. Each project can use the tools assigned to its project group, tenant, or the Kubernetes Cluster that is the deployment target of the application. Typically, when assigned at the cluster level, the tools support build/pipelines and image registries that affect deployment speed. Tools are broadly classified into three types based on their scope of use.
ProjectGroup Tool: It is a tool that can be used only in projects belonging to a Project Group. Multiple Project Groups can be mapped and used. The Project Group Owner and Master register and manage it.
Tenant Tool: A tool that can only be used within project groups belonging to a tenant. Multiple tenants can be mapped for use. When registering the tool, only the tenant administrator of the initially registered tenant can manage it. Tenants added later to the tool can only use it. Additionally, it can be designated and managed to be usable in clusters accessible to the tenant administrator.
System Tool: DevOps Service is a tool that can be used as a service across the entire project. System administrators designate and manage the tenants and clusters that can be registered and used.
Application Template
This is a template that makes it easy to set up a project. A template that reflects development standards and even provides sample code is called Dev. Starter, while a template that simply supports development environment setup is called Environment Only. Like tools, it is divided into three main types based on the scope of use.
Project Group Template: A template that can be used only by projects belonging to a project group. The project group Owner and Master register and manage it.
Tenant Template: This is a template that can only be used by project groups belonging to a tenant. It is registered and managed by the tenant administrator.
System Template: This template can be used across all projects in DevOps Service. It designates and manages the tenants that system administrators can register and use.