英文:
Upgrading Google Cloud Composer maintaining the same environment and related resources
问题
我正在使用Google Cloud Composer 2在GCP上。
我使用的是Composer版本2.1.11和Airflow版本2.4.3。我想将我的Composer环境升级到（目前最新的）composer-2.3.0-airflow-2.5.1版本。
在官方文档中，报告如下：
当您更改环境中使用的Airflow或Cloud Composer的版本时，您的环境会升级。升级不会更改您连接到环境资源的方式，例如您环境的存储桶的URL或Airflow Web服务器。
这是您期望的行为，否则可能会导致许多问题。然而，第一次我升级它（几个月前），我的当前Composer环境被删除并创建了一个新的，具有不同的URL，不同的Google Cloud存储桶等等。
我做错了什么？我已经尝试过使用terraform和UI两种方式。
我知道这个功能在文档中仍然处于预览状态。但是，如果环境被删除并重新创建，我认为这个功能将不再有用。
英文:
I am using Google Cloud Composer 2 on GCP.
I am on Composer version 2.1.11 and Airflow version 2.4.3. I want to upgrade my Composer environment to the (currently latest) composer-2.3.0-airflow-2.5.1 version.
In the official docs, it's reported:
> When you change the version of Airflow or Cloud Composer used by your environment, your environment upgrades. Upgrading does not change how you connect to the resources in your environment, such as the URL of your environment's bucket, or Airflow web server.
This is something you would expect, otherwise It can potentially break many things. However, the first time I upgraded it (a couple of months ago), my current Composer environment was erased and a new one created, with different URL, different bucket on GS, etc.
What am I doing wrong? I have tried both via terraform and the UI.
I am aware that this functionality is still in Preview as reported in the docs. However, if the environment is deleted and recreated I think this feature is not useful at all anymore.
答案1
得分: 1
我复制了您的关注点。您可以继续执行更新。如下所示，在执行次要升级时没有更改。要进行升级，请参阅此文档。<br><br>
<br><br>
<br><br>
英文:
I replicated your concern. You can go ahead and proceed with the update. As shown in the mages below, there are no changes when doing a minor upgrade. For upgrading, refer to this documentation.<br><br><br><br><br><br>
通过集体智慧和协作来改善编程学习和解决问题的方式。致力于成为全球开发者共同参与的知识库，让每个人都能够通过互相帮助和分享经验来进步。
评论