Gitlab K8s executor-非K8s环境的名称空间
我们使用头盔图来为gitlab跑步者提供装备。我们的作业将更改部署到云环境中,而不是k8s集群 两个问题: 问题1 在操作/环境方面,我看到以下内容:Gitlab K8s executor-非K8s环境的名称空间,gitlab,gitlab-ci,gitlab-ci-runner,Gitlab,Gitlab Ci,Gitlab Ci Runner,我们使用头盔图来为gitlab跑步者提供装备。我们的作业将更改部署到云环境中,而不是k8s集群 两个问题: 问题1 在操作/环境方面,我看到以下内容: Kubernetes deployment not found To see deployment progress for your environments, make sure you are deploying to `$KUBE_NAMESPACE` and annotating with `app.gitlab.com/app=$CI
Kubernetes deployment not found To see deployment progress for your environments, make sure you are deploying to `$KUBE_NAMESPACE` and annotating with `app.gitlab.com/app=$CI_PROJECT_PATH_SLUG` and `app.gitlab.com/env=$CI_ENVIRONMENT_SLUG`
为什么以及如何处理它
问题2
尽管在舵配置中我设置了:
environment = ["FF_GITLAB_REGISTRY_HELPER_IMAGE=true"]
[runners.kubernetes]
helper_image = "registry.gitlab.com/gitlab-org/gitlab-runner/gitlab-runner-helper:x86_64-latest"
image_pull_secrets = ["regcred"]
namespace = "gitlab"
privileged = true
poll_interval = 5
poll_timeout = 3600
所有的作业吊舱都在gitlab ns中运行,每个环境都会创建一个新的空名称空间,格式为:“project Projectd envname”
为什么以及如何避免这种情况