Integrated Cluster Management
If the environment is not equipped with Kubernetes such a Bare Metal, VMWare or OpenStack, Cocktail will install Kubernetes. Upgrading Kubernetes and adding nodes to clusters is also possible through Cocktail.
Multi-Cluster, Multi Cloud Management
You do not have to install cocktail for each cluster. Multiple clusters will be integrated and managed in one Cocktail Cloud. You can use different Cloud Providers. It does not matter whether you are using Kubernetes installed by Cocktail, or it is Managed Kubernetes Service of Cloud Providers such as GKE, EKS, AKS.
All interactions with Kubernetes for application management such as build, deployment, operation and monitoring are unified and managed.
Build From Code to Container
Source Build for Multiple Language
You just have to connect Source Repository (Git). We will Source Build regardless of the development language. You can see the build process.
Container Image Build
We will make the application that has been Source Built into executable unit of Container Image. Compatibility is guaranteed with the OCI standard format.
Built-in Private Registry
Private Registry is provided as standard. The created Container Image is automatically stored and versioned in the embedded Registry. When deploying applications, you can select the image version of your choice.
Public Registry Support
You can register and use an external registry in order to use container image of the application that is officially being distributed from vendors.
Deploy One-Click and Continuous
Deployment Version Control
You can select and deploy the version of the built container image of your choice. If a problem occurs after deployment, you can simply return to the previous version.
Continuous Delivery Pipeline
Do not hesitate to modify and deploy applications. When a code is added or modified, the application can be replaced without service downtime. With the prepared pipeline, the process of Source Build, Container Image Build, and Container Update takes place in an instant.
Packaged Application Deploy
Applications composed of multiple containers such as N-tier or Microservice Architecture can be bundled into a single package and be managed in versions. When having to deploy the same application by region, by stage, or by cloud infra, you can deploy in package unit at once on the designated cluster instead of individual containers.
Runtime SW Catalogs
Frequently used runtime SW is provided as a catalog so that it can be deployed and used immediately. It uses the official image that each SW Vendor provides. You can also reuse your own SW configurations at any time while you store and manage them in the Catalog.
Operate Application Oriented
User / Group Management
The workspace for DevOps by project team is provided. You can allocate cluster resources to be used by each team, and you can register your team members and work securely.
It is the space to deploy containers with the same namespace. The cluster to be used by each Application Map selects one of the clusters allowed for the project team. Each project tea can have multiple application maps.
It is the unit of deployment and management on the Application Map. For intuitive management of container, container and related configuration such as resource, network, volume, scaling, update policy is bundled and managed together. Each Cocktail Server can connect the build and configure a convenient deployment environment.
Applications on Multi Cluster
Project teams that have been allocated multiple clusters can freely use the cluster. They can also check the status information of their cluster.
Monitor Full Stack and Integrated
Prometheus is built-in and used to check the status of not only the cluster but also the application. Triggers can be configured with various conditions to deliver alerts to Email or Slack.
Cluster Infra Monitoring
It provides a visual presentation of the cluster, nodes within the cluster, and basic information and resource usage information of Volume. You can also see the status of application arranged for each node. If it is a Cloud Service, it shows the metering information.
It also provides monitoring from the operation viewpoint. You can check the usage amount of resource allocated by Application Map. You can also see the resource usage amount of pod and container for each Cocktail Server in the Application Map.
It visualizes and provides usage amount of resources such as CPU, Memory, and Network from various viewpoints such as Cluster, Node, Application, Pod, and Container.