Estos contenidos se han traducido de forma automática para su comodidad, pero Huawei Cloud no garantiza la exactitud de estos. Para consultar los contenidos originales, acceda a la versión en inglés.
Cómputo
Elastic Cloud Server
Bare Metal Server
Auto Scaling
Image Management Service
Dedicated Host
FunctionGraph
Cloud Phone Host
Huawei Cloud EulerOS
Redes
Virtual Private Cloud
Elastic IP
Elastic Load Balance
NAT Gateway
Direct Connect
Virtual Private Network
VPC Endpoint
Cloud Connect
Enterprise Router
Enterprise Switch
Global Accelerator
Gestión y gobernanza
Cloud Eye
Identity and Access Management
Cloud Trace Service
Resource Formation Service
Tag Management Service
Log Tank Service
Config
Resource Access Manager
Simple Message Notification
Application Performance Management
Application Operations Management
Organizations
Optimization Advisor
Cloud Operations Center
Resource Governance Center
Migración
Server Migration Service
Object Storage Migration Service
Cloud Data Migration
Migration Center
Cloud Ecosystem
KooGallery
Partner Center
User Support
My Account
Billing Center
Cost Center
Resource Center
Enterprise Management
Service Tickets
HUAWEI CLOUD (International) FAQs
ICP Filing
Support Plans
My Credentials
Customer Operation Capabilities
Partner Support Plans
Professional Services
Análisis
MapReduce Service
Data Lake Insight
CloudTable Service
Cloud Search Service
Data Lake Visualization
Data Ingestion Service
GaussDB(DWS)
DataArts Studio
IoT
IoT Device Access
Otros
Product Pricing Details
System Permissions
Console Quick Start
Common FAQs
Instructions for Associating with a HUAWEI CLOUD Partner
Message Center
Seguridad y cumplimiento
Security Technologies and Applications
Web Application Firewall
Host Security Service
Cloud Firewall
SecMaster
Data Encryption Workshop
Database Security Service
Cloud Bastion Host
Data Security Center
Cloud Certificate Manager
Situation Awareness
Managed Threat Detection
Blockchain
Blockchain Service
Servicios multimedia
Media Processing Center
Video On Demand
Live
SparkRTC
Almacenamiento
Object Storage Service
Elastic Volume Service
Cloud Backup and Recovery
Storage Disaster Recovery Service
Scalable File Service
Volume Backup Service
Cloud Server Backup Service
Data Express Service
Dedicated Distributed Storage Service
Contenedores
Cloud Container Engine
SoftWare Repository for Container
Application Service Mesh
Ubiquitous Cloud Native Service
Cloud Container Instance
Bases de datos
Relational Database Service
Document Database Service
Data Admin Service
Data Replication Service
GeminiDB
GaussDB
Distributed Database Middleware
Database and Application Migration UGO
TaurusDB
Middleware
Distributed Cache Service
API Gateway
Distributed Message Service for Kafka
Distributed Message Service for RabbitMQ
Distributed Message Service for RocketMQ
Cloud Service Engine
EventGrid
Dedicated Cloud
Dedicated Computing Cluster
Aplicaciones empresariales
ROMA Connect
Message & SMS
Domain Name Service
Edge Data Center Management
Meeting
AI
Face Recognition Service
Graph Engine Service
Content Moderation
Image Recognition
Data Lake Factory
Optical Character Recognition
ModelArts
ImageSearch
Conversational Bot Service
Speech Interaction Service
Huawei HiLens
Developer Tools
SDK Developer Guide
API Request Signing Guide
Terraform
Koo Command Line Interface
Distribución de contenido y cómputo de borde
Content Delivery Network
Intelligent EdgeFabric
CloudPond
Soluciones
SAP Cloud
High Performance Computing
Servicios para desarrolladores
ServiceStage
CodeArts
CodeArts PerfTest
CodeArts Req
CodeArts Pipeline
CodeArts Build
CodeArts Deploy
CodeArts Artifact
CodeArts TestPlan
CodeArts Check
Cloud Application Engine
aPaaS MacroVerse
KooPhone
KooDrive
Centro de ayuda/ Cloud Container Engine/ Guía del usuario/ Gráfico de Helm/ Convertir una versión de Helm v2 a v3

Convertir una versión de Helm v2 a v3

Actualización más reciente 2024-09-10 GMT+08:00

Contexto

CCE es totalmente compatible con Helm v3. Esta sección le guía para convertir una versión de Helm v2 a Helm v3. Helm v3 descarta o reconstruye algunas funciones Helm v2 en la capa inferior. Por lo tanto, la conversión es arriesgada hasta cierto punto. Se requiere simulación antes de la conversión.

Para obtener más información, consulte la documentación de la comunidad.

Precauciones

  • Helm v2 almacena información de lanzamiento en el ConfigMaps. Helm v3 lo hace en secreto.
  • Cuando consulta, actualiza u opera una versión Helm v2 en la consola de CCE, CCE intentará convertir la versión a v3. Si opera en segundo plano, convierta la versión siguiendo las instrucciones que aparecen a continuación.

Proceso de conversión (sin usar el cliente Helm v3)

  1. Descargue el complemento de conversión helm 2to3 en el nodo CCE.

    wget https://github.com/helm/helm-2to3/releases/download/v0.10.2/helm-2to3_0.10.2_linux_amd64.tar.gz

  1. Descomprime el paquete de complementos.

    tar -xzvf helm-2to3_0.10.2_linux_amd64.tar.gz

  1. Realice la conversión simulada.

    Tome la versión test-convert como ejemplo. Ejecute el siguiente comando para simular la conversión: Si se muestra la siguiente información, la simulación se realiza correctamente.

    # ./2to3 convert --dry-run --tiller-out-cluster -s configmaps test-convert
    NOTE: This is in dry-run mode, the following actions will not be executed.
    Run without --dry-run to take the actions described below:
    Release "test-convert" will be converted from Helm v2 to Helm v3.
    [Helm 3] Release "test-convert" will be created.
    [Helm 3] ReleaseVersion "test-convert.v1" will be created.

  2. Realice la conversión. Si se muestra la siguiente información, la conversión se realiza correctamente.

    # ./2to3 convert --tiller-out-cluster -s configmaps test-convert
    Release "test-convert" will be converted from Helm v2 to Helm v3.
    [Helm 3] Release "test-convert" will be created.
    [Helm 3] ReleaseVersion "test-convert.v1" will be created.
    [Helm 3] ReleaseVersion "test-convert.v1" created.
    [Helm 3] Release "test-convert" created.
    Release "test-convert" was converted successfully from Helm v2 to Helm v3.
    Note: The v2 release information still remains and should be removed to avoid conflicts with the migrated v3 release.
    v2 release information should only be removed using `helm 2to3` cleanup and when all releases have been migrated over.

  3. Una vez completada la conversión, simule la liquidación de recursos. Después de la simulación, borre los recursos de la versión v2.

    Espacio libre simulado:

    # ./2to3 cleanup --dry-run --tiller-out-cluster -s configmaps --name test-convert
    NOTE: This is in dry-run mode, the following actions will not be executed.
    Run without --dry-run to take the actions described below:
    WARNING: "Release 'test-convert' Data" will be removed. 
    [Cleanup/confirm] Are you sure you want to cleanup Helm v2 data? [y/N]: y
    Helm v2 data will be cleaned up.
    [Helm 2] Release 'test-convert' will be deleted.
    [Helm 2] ReleaseVersion "test-convert.v1" will be deleted.

    Espacio libre formal:

    # ./2to3 cleanup --tiller-out-cluster -s configmaps --name test-convert
    WARNING: "Release 'test-convert' Data" will be removed. 
    [Cleanup/confirm] Are you sure you want to cleanup Helm v2 data? [y/N]: y
    Helm v2 data will be cleaned up.
    [Helm 2] Release 'test-convert' will be deleted.
    [Helm 2] ReleaseVersion "test-convert.v1" will be deleted.
    [Helm 2] ReleaseVersion "test-convert.v1" d

Proceso de conversión (con el cliente de Helm v3)

  1. Instale el cliente de Helm v3. Para obtener más información, véase Instalación de Helm v3.
  2. Instale el complemento de conversión.

    # helm plugin install https://github.com/helm/helm-2to3
    Downloading and installing helm-2to3 v0.10.2 ...
    https://github.com/helm/helm-2to3/releases/download/v0.10.2/helm-2to3_0.10.2_linux_amd64.tar.gz
    Installed plugin: 2to3

  3. Compruebe si el complemento ha sido instalado.

    # helm plugin list
    NAME VERSION DESCRIPTION                                                               
    2to3  0.10.2      migrate and cleanup Helm v2 configuration and releases in-place to Helm v3

  4. Realice la conversión simulada.

    Tome la versión test-convert como ejemplo. Ejecute el siguiente comando para simular la conversión: Si se muestra la siguiente información, la conversión simulada se realiza correctamente.

    # helm 2to3 convert --dry-run --tiller-out-cluster -s configmaps test-convert
    NOTE: This is in dry-run mode, the following actions will not be executed.
    Run without --dry-run to take the actions described below:
    Release "test-convert" will be converted from Helm v2 to Helm v3.
    [Helm 3] Release "test-convert" will be created.
    [Helm 3] ReleaseVersion "test-convert.v1" will be created.

  5. Realice la conversión. Si se muestra la siguiente información, la conversión se realiza correctamente.

    # helm 2to3 convert --tiller-out-cluster -s configmaps test-convert
    Release "test-convert" will be converted from Helm v2 to Helm v3.
    [Helm 3] Release "test-convert" will be created.
    [Helm 3] ReleaseVersion "test-convert.v1" will be created.
    [Helm 3] ReleaseVersion "test-convert.v1" created.
    [Helm 3] Release "test-convert" created.
    Release "test-convert" was converted successfully from Helm v2 to Helm v3.
    Note: The v2 release information still remains and should be removed to avoid conflicts with the migrated v3 release.
    v2 release information should only be removed using `helm 2to3` cleanup and when all releases have been migrated over.

  6. Después de la conversión, puede ver la versión convertida ejecutando helm list.

    # helm list
    NAME                NAMESPACE    REVISION UPDATED                           STATUS      CHART              APP VERSION
    test-convert      default   1                2022-08-29 06:56:28.166918487 +0000 UTC       deployed    test-helmold-1 

  7. Una vez completada la conversión, simule la liquidación de recursos. Después de la simulación, borre los recursos de la versión v2.

    Espacio libre simulado:

    # helm 2to3 cleanup --dry-run --tiller-out-cluster -s configmaps --name test-convert
    NOTE: This is in dry-run mode, the following actions will not be executed.
    Run without --dry-run to take the actions described below:
    WARNING: "Release 'test-convert' Data" will be removed. 
    [Cleanup/confirm] Are you sure you want to cleanup Helm v2 data? [y/N]: y
    Helm v2 data will be cleaned up.
    [Helm 2] Release 'test-convert' will be deleted.
    [Helm 2] ReleaseVersion "test-convert.v1" will be deleted.

    Espacio libre formal:

    # helm 2to3 cleanup --tiller-out-cluster -s configmaps --name test-convert
    WARNING: "Release 'test-convert' Data" will be removed. 
    [Cleanup/confirm] Are you sure you want to cleanup Helm v2 data? [y/N]: y
    Helm v2 data will be cleaned up.
    [Helm 2] Release 'test-convert' will be deleted.
    [Helm 2] ReleaseVersion "test-convert.v1" will be deleted.
    [Helm 2] ReleaseVersion "test-convert.v1" deleted.
    [Helm 2] Release 'test-convert' deleted.
    Helm v2 data was cleaned up successfully.

Utilizamos cookies para mejorar nuestro sitio y tu experiencia. Al continuar navegando en nuestro sitio, tú aceptas nuestra política de cookies. Descubre más

Comentarios

Comentarios

Comentarios

0/500

Seleccionar contenido

Enviar el contenido seleccionado con los comentarios