- 概述
- 要求
- 安装
- 安装后
- 集群管理
- 监控和警示
- 迁移和升级
- 特定于产品的配置
- 最佳实践和维护
- 故障排除
- 无法获取沙盒映像
- Pod 未显示在 ArgoCD 用户界面中
- Redis 探测器失败
- RKE2 服务器无法启动
- 在 UiPath 命名空间中找不到密码
- ArgoCD 在首次安装后进入“进行中”状态
- 意外不一致;手动运行 fsck
- MongoDB Pod 处于 CrashLoopBackOff 状态或在删除后处于“等待 PVC 配置”状态
- MongoDB Pod 从 4.4.4-ent 升级到 5.0.7-ent 失败
- 集群还原或回滚后服务运行状况不佳
- Pod 在 Init:0/X 中卡住
- Prometheus 处于 CrashLoopBackoff 状态,并出现内存不足 (OOM) 错误
- 监控仪表板中缺少 Ceph-rook 指标
- 使用 Automation Suite 诊断工具
- 使用 Automation Suite 支持包工具
- 探索日志
轮换 Blob 存储凭据
要在 Automation Suite 中轮换 Process Mining 的 Blob 存储凭据,管理员需要有权使用 kubectl、lens 或其他工具访问 Kubernetes 集群密码。必须使用新凭据更新以下详述的存储密码,并且需要重新启动 Airflow 和 Process Mining 的 Pod,以确保这些服务的所有 Pod 都收到新凭据。
UiPath 命名空间
processmining-service-rook-ceph-secret.OBJECT_STORAGE_ACCESSKEY
processmining-service-rook-ceph-secret.OBJECT_STORAGE_SECRETKEY
Airflow 命名空间
airflow-rook-ceph-secret.OBJECT_STORAGE_ACCESSKEY
airflow-rook-ceph-secret.OBJECT_STORAGE_SECRETKEY
processmining-service-rook-ceph-secret.OBJECT_STORAGE_ACCESSKEY
processmining-service-rook-ceph-secret.OBJECT_STORAGE_SECRETKEY
ceph-object-store-secret.OBJECT_STORAGE_ACCESSKEY
ceph-object-store-secret.OBJECT_STORAGE_SECRETKEY
UiPath 命名空间
processmining-external-storage-secret.ACCESSKEY
processmining-external-storage-secret.SECRETKEY
Airflow 命名空间
processmining-external-storage-secret.ACCESSKEY
processmining-external-storage-secret.SECRETKEY
processmining-external-storage-secret.connection
UiPath 命名空间
processmining-external-storage-secret.ACCESSKEY
processmining-external-storage-secret.SECRETKEY
Airflow 命名空间
processmining-external-storage-secret.ACCESSKEY
processmining-external-storage-secret.SECRETKEY
processmining-external-storage-secret.connection
UiPath 命名空间
processmining-external-storage-secret.ACCOUNTNAME
processmining-external-storage-secret.ACCOUNTKEY
Airflow 命名空间
processmining-external-storage-secret.ACCOUNTNAME
processmining-external-storage-secret.ACCOUNTKEY
processmining-external-storage-secret.connection
urlencode -d "wasb%3A%2F%2Fazureuser%40%3Fextra__wasb__connection_string%3DDefaultEndpointsProtocol%3Dhttps%3BEndpointSuffix%3Dcore.windows.net%3BAccountName%3Dazureuser%3BAccountKey%3DACCOUNT_KEY%3BBlobEndpoint%3Dhttps%3A%2F%2Fexample.blob.core.windows.net%2F%3BFileEndpoint%3Dhttps%3A%2F%2Fexample.file.core.windows.net%2F%3BQueueEndpoint%3Dhttps%3A%2F%2Fexample.queue.core.windows.net%2F%3BTableEndpoint%3Dhttps%3A%2F%2Fexample.table.core.windows.net%2F%26extra__wasb__sas_token%3D%26extra__wasb__shared_access_key%3D%26extra__wasb__tenant_id%3D"
urlencode "wasb://azureuser@?extra__wasb__connection_string=DefaultEndpointsProtocol=https;EndpointSuffix=core.windows.net;AccountName=azureuser;AccountKey=ACCOUNT_KEY;BlobEndpoint=https://example.blob.core.windows.net/;FileEndpoint=https://example.file.core.windows.net/;QueueEndpoint=https://example.queue.core.windows.net/;TableEndpoint=https://example.table.core.windows.net/&extra__wasb__sas_token=&extra__wasb__shared_access_key=&extra__wasb__tenant_id="
urlencode -d "wasb%3A%2F%2Fazureuser%40%3Fextra__wasb__connection_string%3DDefaultEndpointsProtocol%3Dhttps%3BEndpointSuffix%3Dcore.windows.net%3BAccountName%3Dazureuser%3BAccountKey%3DACCOUNT_KEY%3BBlobEndpoint%3Dhttps%3A%2F%2Fexample.blob.core.windows.net%2F%3BFileEndpoint%3Dhttps%3A%2F%2Fexample.file.core.windows.net%2F%3BQueueEndpoint%3Dhttps%3A%2F%2Fexample.queue.core.windows.net%2F%3BTableEndpoint%3Dhttps%3A%2F%2Fexample.table.core.windows.net%2F%26extra__wasb__sas_token%3D%26extra__wasb__shared_access_key%3D%26extra__wasb__tenant_id%3D"
urlencode "wasb://azureuser@?extra__wasb__connection_string=DefaultEndpointsProtocol=https;EndpointSuffix=core.windows.net;AccountName=azureuser;AccountKey=ACCOUNT_KEY;BlobEndpoint=https://example.blob.core.windows.net/;FileEndpoint=https://example.file.core.windows.net/;QueueEndpoint=https://example.queue.core.windows.net/;TableEndpoint=https://example.table.core.windows.net/&extra__wasb__sas_token=&extra__wasb__shared_access_key=&extra__wasb__tenant_id="