DOCSEARCHbyAlgolia
Submit Docs

Kuboard Kubernetes Management GUI

repository·master·Indexed 12 days ago

https://github.com/eip-work/kuboard-press

A comprehensive Kubernetes management tool designed to simplify cluster administration, multi-cluster management, and microservice visualization. It provides a graphical interface for resource management, diagnostics, and operations, including web-based CLI tools like KuboardProxy and PortForward. Features include RBAC, SSO support (GitHub/GitLab), CI/CD integration for automated image updates, and an extensible Addon system for injecting context-aware monitoring and logging tools into the UI.

Tokens
264.7K
Snippets
546
Records
1.2K
Agent score
97%

What's inside Kuboard

  1. Overview of Kubernetes Learning Path

    master

    The Kubernetes tutorial provides a structured learning path ranging from basic concepts to advanced production practices. It is designed for both beginners and technical enthusiasts who want to deploy microservices (like Spring Cloud) on Kubernetes.

    Learning Stages:

    1. Introduction: Basic definitions and component overviews.
    2. Experience: Hands-on cluster installation and management interface setup.
    3. Basics: Deploying apps, viewing Pods/Nodes, exposing apps, scaling, and rolling updates.
    4. Intermediate: Deep dives into architecture, objects (Namespaces, Labels, Annotations), Workloads (Pods, Deployments, StatefulSets, Jobs), Networking (Services, Ingress, DNS), Storage (Volumes, PV/PVC, StorageClass), and Configuration (ConfigMaps, Secrets, Resource Management).
    5. Advanced: Troubleshooting, Logging (Loki), Scheduling tuning, Security (RBAC, Authentication), and Monitoring/Alerting.

  2. Overview of the SpringBlade Microservice Development Platform

    master

    SpringBlade is a microservice development platform based on the SpringCloud ecosystem. Key features include:

    • Frontend Frameworks: Supports two open-source frameworks: Sword (React + Ant Design) and Saber (Vue + Element-UI).
    • Core Framework: Uses BladeTool, a highly encapsulated SpringCloud component library available via Maven.
    • Stability & Traffic Control: Integrates Sentinel for flow control, circuit breaking, and system load protection.
    • Service Discovery & Configuration: Uses Nacos as the registry and configuration center.
    • Reverse Proxy: Uses Traefik for automated configuration updates and reverse proxying.
    • Multi-tenancy: Includes a simplified, extensible SaaS multi-tenant system.
    • Security: Implements a multi-terminal authentication system inspired by OAuth2 and a Secure module using JWT for token authentication (extensible with Redis).

  3. Overview of Kuboard Features

    master

    Kuboard is a free management interface designed for Kubernetes (compatible with version 1.13 and above). Key capabilities include:

    • Authentication: Supports built-in user libraries, GitLab/GitHub SSO, or LDAP. Administrators can configure password policies and expiration settings.
    • Multi-cluster Management: Import multiple Kubernetes clusters and use permission controls to assign specific clusters or namespaces to users/groups.
    • Microservice Visualization: Displays workloads in a layered microservice architecture view within a namespace, with support for custom namespace layouts.
    • Workload Management: Provides intuitive views for Deployment history, Pod lists, Pod events, and container information. Supports graphical editing for various Kubernetes objects (Node, Namespace, Deployment, StatefulSet, DaemonSet, Secret, ConfigMap, Service, Ingress, StorageClass, PVC, etc.) without manual YAML editing.
    • Storage Support: Integrates with NFS and CephFS; supports expansion and snapshot operations for CephFS PersistentVolumeClaims.
    • CLI-like Interoperability: Provides browser-based access to kubectl features such as top nodes/pods, container logs, terminal access, and a file browser (supporting file upload/download to/from containers). Includes KuboardProxy for kubectl proxy functionality.
    • Extensible Suites: Supports plugin-like suites for:
      • Monitoring: Prometheus/Grafana-based monitoring for clusters, nodes, workloads, and containers (CPU, memory, network, disk).
      • Logging: Grafana/Loki/Promtail-based log aggregation.
      • Storage Browser: For viewing and operating on storage volume contents.

  4. Overview of Kuboard for Kubernetes Management

    master

    Kuboard is a free graphical management tool for Kubernetes designed to lower the barrier to entry for container orchestration. It addresses common Kubernetes challenges such as complex cluster installation, steep learning curves, and the difficulty of managing manual YAML files across multiple environments.

    Key resources provided by Kuboard include:

    • Kubernetes Installation Documentation: Guides for rapid Kubernetes installation.
    • Free Kubernetes Tutorials: Educational content for learning Kubernetes concepts.
    • Kubernetes Management Interface: A GUI that allows users to deploy and manage applications without writing YAML files.
    • Kubernetes + SpringCloud Practice: Step-by-step documentation for deploying and managing Spring Cloud microservice architectures on Kubernetes.

  6. Overview of High-Availability Kubernetes Installation (v1.16.2)

    master

    This guide describes how to install a production-ready, high-availability (HA) Kubernetes cluster using kubeadm.

    Key Specifications:

    • Kubernetes Version: 1.16.2
    • Networking (CNI): Calico 3.9
    • Ingress Controller: nginx-ingress 1.5.3
    • Container Runtime: Docker 18.09.7
    • HA Architecture:
      • Master Nodes: Requires at least three master nodes forming a cluster, using an internal network load balancer for high availability. Using fewer than three nodes may lead to "split-brain" (脑裂) scenarios.
      • Worker Nodes: Multiple worker nodes forming a cluster, using an external network load balancer for load balancing.

    Note for beginners: If you are new to Kubernetes, it is recommended to follow the Single Master Node Installation guide instead.

  7. What is Kuboard and how can it be used?

    master
    Kuboard is a free Kubernetes management tool designed to help enterprises build private cloud platforms with minimal cost. It provides a graphical interface for managing Kubernetes resources and diagnosing cluster issues. By combining Kubernetes, Kuboard, and other open-source software, you can establish a complete container cloud platform for deploying, diagnosing, and operating microservices.

  8. Overview of Kuboard Addons (套件)

    master

    Kuboard Addons are not package managers like Helm; instead, they are designed to provide application-context-aware features within the Kuboard interface, such as monitoring and log viewing.

    Key features include:

    • Rapid Installation: Uses addon configuration files and Kuboard's built-in import functionality.
    • Initialization: Supports automated initialization scripts (e.g., configuring Grafana DataSources or dashboards) after resources are deployed.
    • UI Context Integration: Addons can inject functional buttons into specific Kuboard UI layers: Node, Pod, and Container.
    • Lifecycle Management: Easy installation and uninstallation via the Kuboard interface.
    • Extensibility: The API is open for creating custom addons tailored to specific middleware (MySQL, Nginx) or tracing/logging stacks (Pinpoint, Skywalking, ELK).

  9. Overview of Kuboard Design Goals

    master

    Kuboard is designed to achieve two primary objectives:

    1. Lower the barrier to entry for Kubernetes: It allows beginners to start using Kubernetes immediately and gradually learn underlying concepts through practical use.
    2. Enhance Kubernetes operations: It provides a graphical interface for experienced operators to perform daily maintenance tasks without relying solely on the kubectl command line.

  10. Overview of High Availability Kubernetes v1.15.3 Installation

    master

    This guide describes how to install a production-ready High Availability (HA) Kubernetes cluster using kubeadm.

    Cluster Specifications

    • Kubernetes Version: 1.15.3
    • Calico: 3.8.2
    • Nginx-Ingress: 1.5.3
    • Docker: 18.09.7

    Topology

    • Master Nodes: A cluster of at least three master nodes. High availability is achieved via an internal network Load Balancer for the API Server. Using fewer than three masters may lead to a "split-brain" scenario.
    • Worker Nodes: Multiple worker nodes forming the compute cluster, typically accessed via an external network Load Balancer.

  11. Overview of Kuboard for Kubernetes

    master
    Kuboard is a free management interface designed for Kubernetes, compatible with Kubernetes version 1.13 and above. It provides a graphical user interface (GUI) for managing multiple clusters, handling permissions, and accessing monitoring and logging suites. It is used by over 1,000 enterprises in production environments.

  12. Overview of Sealos for Kubernetes Offline Installation

    master

    Sealos is a lightweight, Golang-based tool designed for installing Kubernetes clusters, with a strong focus on offline environments and high availability. It separates the installation tool from the resource packages (binaries, configuration files, images, and YAML files), allowing users to swap resource packages for different versions without changing the tool itself.

    Key Features

    • Offline Support: Decouples the tool from resource packages for easy version management.
    • Certificate Management: Handles certificate expiration/extension automatically.
    • High Availability via Local Load Balancing: Instead of using external tools like Keepalived or HAProxy, Sealos implements local load balancing on each node using the Linux kernel's IPVS. This avoids the resource overhead of user-space proxies (like Envoy or Nginx) and prevents circular dependencies during node joins.
    • Customized kubeadm: Sealos uses a customized version of kubeadm to support long-lived certificates (set to 99 years) and to integrate IPVS rule creation and static pod management directly into the join process.
    • Simplicity: A single binary with no external dependencies (unlike Ansible which requires Python and SSH configurations).