气流集群应该与dev-vpc
中的资源进行通信,我注意到我应该将气流集群放置在相同的vpc上并将vpc-native设置为打开,以便使用私有ip访问资源。
下面的图片是我的网络设置。
但是,Kubernetes集群无法正确启动,并显示以下错误。
Status details
All cluster resources were brought up, but: only 2 nodes out of 3 have registered; this is likely due to Nodes failing to start correctly; try re-creating the cluster or contact support if that doesn't work.
以下日志是从Cloud Composer记录的错误。
{
insertId: "-<my_insert_id>"
logName: "projects/<my_project_name>/logs/cloudaudit.googleapis.com%2Factivity"
operation: {
id: "projects/new-life-experience/locations/asia-northeast3/operations/<operation_id>"
last: true
producer: "composer.googleapis.com"
}
protoPayload: {
@type: "type.googleapis.com/google.cloud.audit.AuditLog"
authenticationInfo: {
principalEmail: "<my_email>"
}
methodName: "google.cloud.orchestration.airflow.service.v1.Environments.CreateEnvironment"
resourceName: "projects/<my_project_name>/locations/asia-northeast3/environments/<my_composer_name>"
serviceName: "composer.googleapis.com"
status: {
code: 2
message: "Composer Backend timed out. Currently running tasks are [stage: CP_COMPOSER_AGENT_RUNNING
description: "RPC Successful: Pull"
response_timestamp {
seconds: 1591150022
nanos: 653000000
}
]."
}
}
receiveTimestamp: "2020-06-03T02:09:01.854953208Z"
resource: {
labels: {
environment_name: "<my_composer_name>"
location: "asia-northeast3"
project_id: "<my_project_id>"
}
type: "cloud_composer_environment"
}
severity: "ERROR"
timestamp: "2020-06-03T02:09:01.232Z"
我已经检查了实例的配额,但是所有配额足以为Composer分配三个节点。
我不知道为什么在创建kubernetes集群时为什么只成功分配了三个节点中的两个。
答案 0 :(得分:0)
此答案由@astrohsy在评论部分提供:
我今天在相同的环境下启动了Composer集群,但是 它工作正常。我认为
<p-tree [value]="files"> <ng-template let-node pTemplate="picture"> <img [attrs.src]="picture.path"> </ng-template> <ng-template let-node pTemplate="default"> <input [(ngModel)]="node.label" type="text" style="width:100%"> </ng-template> </p-tree>
上有一个错误 地区,目前已发布。