This is a cloud-native application that focuses on the DevOps area.

centos 7.9系统,一个master,多个worker节点,， 使用kk直接安装k8s和 kubesphere ；升级也是使用kk升级的。

安装的时候kk版本是 v1.2.0； 升级的时候 kk版本是v1.2.1

orgin version: k8s 1.20.4 kuebsphere 3.2.0

upgrade versions: k8s 1.21.5 kubesphere 3.2.1

build the orgin pipeline failure. and the pods of kubesphere-devops-worker is been ContainerCreating-->Terminating --->Destroy 。 升级过后，devops项目中运行流水线，一直卡在如下的界面，查看了下pods，发现 相关devops-worker的pods也是一直在创建和销毁中循环。

Tutorial link: https://jenkins-zh.cn/wechat/articles/2021/01/2021-01-11-exteranl-jenkins-in-kubesphere

I operate according to the tutorial above. The current error is: after creating a new Devops project and pipeline in the project on kubesphere, click the pipeline to report an error like the picture below:

And, the pipeline created by kubesphere cannot be synchronized to the external Jenkins!

Now I want to know the following questions:

1. Does the kubesphere Jenkins auth plug-in of Jenkins need to configure the kubesphere account and password? If necessary, where to configure it? Now I click test connection and an error will occur:

2. In kubesphere configuration, the configuration in configmap: kubesphere system / kubesphere config: how to fill in devops.password: fill in the plaintext or ciphertext of the login password?

Kubesphere and Jenkins can't see the log of errors. Please provide me with ideas to solve the problem. Thank you very much!

Now I want to use kubesphere 3.2 connects external Jenkins. I follow the connection tutorial（ https://cloud.tencent.com/developer/article/1779145 ）Jenkins has been set up well.

Now i need to configure the of kubesphere: do I need to modify kubesphere config or Devops config? Or do both configurations need to be modified? Now kubesphere config is configured as follows: is my configuration correct? Do i need to modify the devopsserviceaddress and endpoint, enable? Note: http://10.133.67.55:8080 This is the external Jenkins address

devops: devopsServiceAddress: devops-apiserver. kubesphere-devops-system:9090 enable: false endpoint: http://devops-apiserver.kubesphere-devops-system:9090 host: http://10.133.67.55:8080/ maxConnections: 100 password: 1133c93065ca0e6948c4455edec15b7525 username: liuhuining

thanks very much!

What type of PR is this?

/kind feature /kind design

What this PR does / why we need it:

• Extend the gitops.kubesphere.io/v1alpha1/Application CRD to Support FluxApp.
• Add fluxcd/application-controller to maintain the fluxcd Kustomization and HelmRelease.
• Update the config/rbac/role.yaml
• Add sample files in config/samples/gitops directory.

Which issue(s) this PR fixes:

Fixes #717 , #718

Special notes for reviewers:

Please check the following list before waiting reviewers:

• [ ] Already committed the CRD files to the Helm Chart if you created some new CRDs
• [ ] Already added the permission for the new API
• [x] Already added the RBAC markers for the new controllers

Does this PR introduce a user-facing change??

None

1. Terminating the mission is wrong. A parameter in url is undefined.
2. I think it is due to the failure of the task to create successfully.
3. After I switched the mirror back to 3.20, the task was running and terminated normally.

Versions Used kubespheredev/devops-controller:master kubespheredev/devops-apiserver:master Kubernetes: 1.20

How To Reproduce Steps to reproduce the behavior:

1. Click the stop run button (All branches behave the same)

What dose this PR?

1. Add devops.kubesphere.io/creator into annotations of PipelineRun
2. Trigger PipelineRun with specific token which is issued by devops.kubesphere.io/creator

Why do we need it?

At present, if we trigger a Pipeline using non-admin account, we will get message Started by admin always.

Steps to test

Docker images for test:

johnniang/devops-apiserver:dev-v3.2.1-rc.1-2debd81
johnniang/devops-controller:dev-v3.2.1-rc.1-2debd81

1. Create a Workspace, DevOps Project, Pipeline using admin account
2. Create another account tester and invite him/her into that Workspace and DevOps Project
3. Trigger that Pipeline using tester account
4. See the Last Message column

/kind bug /milestone v3.2 /cc @kubesphere/sig-devops

What type of PR is this?

/kind bug /kind hacktoberfest /kind hacktoberfest-accepted

What this PR does / why we need it:

Before save resource, we should check branch name whether is valid, and build the label selector to query target PipelineRuns, we should check the branch name of request also.

Which issue(s) this PR fixes:

Fixes #104

Environment

host 3.1 + member 3.1 http://139.198.9.112:30883

How To Reproduce Steps to reproduce the behavior:

1. Go to workspace 'ws3'
2. Go to devops project 'dev3-1'
3. Create credential and pipeline

Expected behavior Pipeline and credential created successfully

Actual behavior Failed to create pipeline and credential

/priority high /area devops /cc @kubesphere/sig-devops /kind bug /milestone 3.1.0

Currently, the default docker registry of ks-devops charts is ghcr.io, which is too slow if you are in Chinese network.

See also: https://github.com/kubesphere-sigs/ks-devops/blob/678147e3ae80f3f12370ee743c03d2041f212864/charts/ks-devops/values.yaml

Suggestions

Change the default docker registry from ghcr.io into docker.io.

/good-first-issue

What this PR dose

• Replace label of SCM ref name with field indexer.
• Remove branch name validation

Why we need it

Please see:

• #104
• #397

Which issue this PR fixes

Fix #397

How to test it

Docker images for test:

johnniang/devops-apiserver:dev-v3.2.1-rc.1-fe5d958
johnniang/devops-controller:dev-v3.2.1-rc.1-fe5d958

1. Create Multi-branch Pipeline, using repo https://gitlab.com/johnniang/jenkinsfile-multi-demo.
2. Click Branches tab and see all branches.
3. Click into branch naming 中文测试分支

Please note that KubeSphere console didn't escape the branch name, so we cannot click branch naming feat/featureA util console fixes it:

/kind bug /cc @kubesphere/sig-devops /cc @mangoGoForward

What I did in this PR:

1. Add jenkins-cli to the client.
2. Add createJobInFolder in jenkins-cli.
3. Create jenkinsClient to the client.
4. replace create project pipeline with the new function.

What is version of KubeSphere DevOps has the issue?

3.2.1

How did you install the Kubernetes? Or what is the Kubernetes distribution?

v1.20.4

What happened?

W0106 09:07:05.778692 1 client_config.go:552] Neither --kubeconfig nor --master was specified. Using the inClusterConfig. This might not work.

I0106 09:07:05.781163 1 server.go:160] setting up manager

I0106 09:07:05.881856 1 listener.go:44] controller-runtime/metrics "msg"="metrics server is starting to listen" "addr"=":8080"

I0106 09:07:05.883985 1 server.go:198] Starting cache resource from apiserver...

I0106 09:07:05.884030 1 server.go:201] Starting the controllers.

I0106 09:07:07.289575 1 jenkinsconfig_controller.go:125] starting Jenkins config controller

I0106 09:07:07.289613 1 pipeline_controller.go:187] starting pipeline controller

I0106 09:07:07.289665 1 jenkinsconfig_controller.go:302] syncing key:kubesphere-devops-system/jenkins-casc-config

I0106 09:07:07.289667 1 devopsproject_controller.go:185] starting devops project controller

I0106 09:07:07.290274 1 devopscredential_controller.go:192] starting devopscredential controller

I0106 09:07:07.290490 1 devopscredential_controller.go:219] namespace 'jusda-cdsd1-sitlxg44/kubeconfig' in work queue no longer exists

I0106 09:07:07.291620 1 controller.go:142] controller "msg"="Starting EventSource" "controller"="pipelinerun" "reconcilerGroup"="devops.kubesphere.io" "reconcilerKind"="PipelineRun" "source"={"Type":{"metadata":{"creationTimestamp":null},"spec":{"pipelineRef":null},"status":{}}}

I0106 09:07:07.292550 1 devopscredential_controller.go:219] namespace 'julink-toolkitsqnhmt/harborid' in work queue no longer exists

I0106 09:07:07.292933 1 controller.go:149] controller "msg"="Starting Controller" "controller"="pipelinerun" "reconcilerGroup"="devops.kubesphere.io" "reconcilerKind"="PipelineRun"

I0106 09:07:07.292965 1 controller.go:176] controller "msg"="Starting workers" "controller"="pipelinerun" "reconcilerGroup"="devops.kubesphere.io" "reconcilerKind"="PipelineRun" "worker count"=1

I0106 09:07:07.293165 1 controller.go:142] controller "msg"="Starting EventSource" "controller"="pipeline" "reconcilerGroup"="devops.kubesphere.io" "reconcilerKind"="Pipeline" "source"={"Type":{"metadata":{"creationTimestamp":null},"spec":{"type":""},"status":{}}}

I0106 09:07:07.293391 1 devopscredential_controller.go:219] namespace 'jusda-lng-sitswszs/kubeconfig' in work queue no longer exists

I0106 09:07:07.293470 1 controller.go:142] controller "msg"="Starting EventSource" "controller"="pipeline" "reconcilerGroup"="devops.kubesphere.io" "reconcilerKind"="Pipeline" "source"={"Type":{"metadata":{"creationTimestamp":null},"spec":{"type":""},"status":{}}}

I0106 09:07:07.297777 1 s2irun_controller.go:172] starting s2irun controller

I0106 09:07:07.297862 1 s2ibinary_controller.go:170] starting s2ibinary controller

I0106 09:07:07.289616 1 internal.go:391] controller-runtime/manager "msg"="starting metrics server" "path"="/metrics"

I0106 09:07:07.298338 1 devopscredential_controller.go:219] namespace 'jusda-cdsd1-sitlxg44/harborid' in work queue no longer exists

I0106 09:07:07.298413 1 devopscredential_controller.go:219] namespace 'juslink-widgetv22mt/juslink-gitlab-token' in work queue no longer exists

I0106 09:07:07.298427 1 devopscredential_controller.go:219] namespace 'jusda-cdsd1-sitlxg44/jusda-dce-cdsd2' in work queue no longer exists

I0106 09:07:07.298443 1 devopscredential_controller.go:219] namespace 'juslink-basicservicelqs89/harborid' in work queue no longer exists

I0106 09:07:07.298525 1 devopscredential_controller.go:219] namespace 'juslink-waybillp9k6t/juslink-gitlab-token' in work queue no longer exists

I0106 09:07:07.298568 1 devopscredential_controller.go:219] namespace 'jusda-lng-sitswszs/jusda-dcs-kylle' in work queue no longer exists

I0106 09:07:07.298586 1 devopscredential_controller.go:219] namespace 'jusda-lng-sitswszs/harborid' in work queue no longer exists

I0106 09:07:07.298597 1 devopscredential_controller.go:219] namespace 'juslink-basicservicelqs89/juslink-gitlab-token' in work queue no longer exists

I0106 09:07:07.299157 1 devopscredential_controller.go:219] namespace 'julink-toolkitsqnhmt/juslink-gitlab-token' in work queue no longer exists

I0106 09:07:07.301862 1 devopscredential_controller.go:219] namespace 'juslink-waybillp9k6t/kubeconfig' in work queue no longer exists

I0106 09:07:07.301961 1 devopscredential_controller.go:219] namespace 'juslink-widgetv22mt/harborid' in work queue no longer exists

I0106 09:07:07.306142 1 devopscredential_controller.go:219] namespace 'juslink-waybillp9k6t/harborid' in work queue no longer exists

I0106 09:07:07.307101 1 devopscredential_controller.go:219] namespace 'jusda-srm-sitn9sxc/harborid' in work queue no longer exists

I0106 09:07:07.309533 1 devopscredential_controller.go:219] namespace 'jusda-srm-sitn9sxc/jusda-dcs-kylle' in work queue no longer exists

I0106 09:07:07.322037 1 devopscredential_controller.go:219] namespace 'jusda-srm-sitn9sxc/kubeconfig' in work queue no longer exists

I0106 09:07:07.331028 1 devopscredential_controller.go:219] namespace 'id-generatorvq46p/juslink-gitlab-token' in work queue no longer exists

I0106 09:07:07.331774 1 devopscredential_controller.go:219] namespace 'id-generatorvq46p/harborid' in work queue no longer exists

I0106 09:07:07.332360 1 devopscredential_controller.go:219] namespace 'julink-toolkitsqnhmt/kubeconfig' in work queue no longer exists

I0106 09:07:07.334679 1 devopscredential_controller.go:219] namespace 'id-generatorvq46p/kubeconfig' in work queue no longer exists

I0106 09:07:07.353574 1 devopscredential_controller.go:219] namespace 'juslink-widgetv22mt/kubeconfig' in work queue no longer exists

I0106 09:07:07.353671 1 devopscredential_controller.go:219] namespace 'juslink-basicservicelqs89/kubeconfig' in work queue no longer exists

E0106 09:07:07.384464 1 runtime.go:78] Observed a panic: "invalid memory address or nil pointer dereference" (runtime error: invalid memory address or nil pointer dereference)

goroutine 448 [running]:

k8s.io/apimachinery/pkg/util/runtime.logPanic(0x1abd840, 0x2c15950)

/go/pkg/mod/k8s.io/[email protected]/pkg/util/runtime/runtime.go:74 +0xa6

k8s.io/apimachinery/pkg/util/runtime.HandleCrash(0x0, 0x0, 0x0)

/go/pkg/mod/k8s.io/[email protected]/pkg/util/runtime/runtime.go:48 +0x86

panic(0x1abd840, 0x2c15950)

/usr/local/go/src/runtime/panic.go:965 +0x1b9

github.com/beevik/etree.(*Element).Text(0x0, 0x1d2229f, 0x7)

/go/pkg/mod/github.com/beevik/[email protected]/etree.go:426 +0x26

kubesphere.io/devops/pkg/client/devops/jenkins/internal.GetGitlabSourceFromEtree(0xc000aaf2c0, 0x1d785d3)

/workspace/pkg/client/devops/jenkins/internal/gitlab.go:126 +0x5da

kubesphere.io/devops/pkg/client/devops/jenkins.parseMultiBranchPipelineConfigXml(0xc003eda000, 0x13d9, 0x13d9, 0x0, 0x0)

/workspace/pkg/client/devops/jenkins/pipeline_internal.go:453 +0x71e

kubesphere.io/devops/pkg/client/devops/jenkins.(*Jenkins).GetProjectPipelineConfig(0xc000756b40, 0xc00256e4b0, 0xe, 0xc000c68f94, 0x9, 0x1, 0x0, 0x0)

/workspace/pkg/client/devops/jenkins/project_pipeline.go:172 +0x3b7

kubesphere.io/devops/controllers/pipeline.(*Controller).syncHandler(0xc000880c80, 0xc00256e4b0, 0x18, 0xda466f, 0xc00045d558)

/workspace/controllers/pipeline/pipeline_controller.go:265 +0x7b2

kubesphere.io/devops/controllers/pipeline.(*Controller).processNextWorkItem.func1(0xc000880c80, 0x1a202a0, 0xc002575a50, 0x0, 0x0)

/workspace/controllers/pipeline/pipeline_controller.go:157 +0xe7

kubesphere.io/devops/controllers/pipeline.(*Controller).processNextWorkItem(0xc000880c80, 0x203001)

/workspace/controllers/pipeline/pipeline_controller.go:164 +0x4d

kubesphere.io/devops/controllers/pipeline.(*Controller).worker(...)

/workspace/controllers/pipeline/pipeline_controller.go:175

k8s.io/apimachinery/pkg/util/wait.BackoffUntil.func1(0xc00175e220)

/go/pkg/mod/k8s.io/[email protected]/pkg/util/wait/wait.go:155 +0x5f

k8s.io/apimachinery/pkg/util/wait.BackoffUntil(0xc00175e220, 0x200e280, 0xc001a86360, 0x1, 0xc000ad2180)

/go/pkg/mod/k8s.io/[email protected]/pkg/util/wait/wait.go:156 +0x9b

k8s.io/apimachinery/pkg/util/wait.JitterUntil(0xc00175e220, 0x3b9aca00, 0x0, 0x1, 0xc000ad2180)

/go/pkg/mod/k8s.io/[email protected]/pkg/util/wait/wait.go:133 +0x98

k8s.io/apimachinery/pkg/util/wait.Until(0xc00175e220, 0x3b9aca00, 0xc000ad2180)

/go/pkg/mod/k8s.io/[email protected]/pkg/util/wait/wait.go:90 +0x4d

created by kubesphere.io/devops/controllers/pipeline.(*Controller).Run

/workspace/controllers/pipeline/pipeline_controller.go:195 +0x1f0

panic: runtime error: invalid memory address or nil pointer dereference [recovered]

panic: runtime error: invalid memory address or nil pointer dereference

[signal SIGSEGV: segmentation violation code=0x1 addr=0x40 pc=0xc8f506]

goroutine 448 [running]:

k8s.io/apimachinery/pkg/util/runtime.HandleCrash(0x0, 0x0, 0x0)

/go/pkg/mod/k8s.io/[email protected]/pkg/util/runtime/runtime.go:55 +0x109

panic(0x1abd840, 0x2c15950)

/usr/local/go/src/runtime/panic.go:965 +0x1b9

github.com/beevik/etree.(*Element).Text(0x0, 0x1d2229f, 0x7)

/go/pkg/mod/github.com/beevik/[email protected]/etree.go:426 +0x26

kubesphere.io/devops/pkg/client/devops/jenkins/internal.GetGitlabSourceFromEtree(0xc000aaf2c0, 0x1d785d3)

/workspace/pkg/client/devops/jenkins/internal/gitlab.go:126 +0x5da

kubesphere.io/devops/pkg/client/devops/jenkins.parseMultiBranchPipelineConfigXml(0xc003eda000, 0x13d9, 0x13d9, 0x0, 0x0)

/workspace/pkg/client/devops/jenkins/pipeline_internal.go:453 +0x71e

kubesphere.io/devops/pkg/client/devops/jenkins.(*Jenkins).GetProjectPipelineConfig(0xc000756b40, 0xc00256e4b0, 0xe, 0xc000c68f94, 0x9, 0x1, 0x0, 0x0)

/workspace/pkg/client/devops/jenkins/project_pipeline.go:172 +0x3b7

kubesphere.io/devops/controllers/pipeline.(*Controller).syncHandler(0xc000880c80, 0xc00256e4b0, 0x18, 0xda466f, 0xc00045d558)

/workspace/controllers/pipeline/pipeline_controller.go:265 +0x7b2

kubesphere.io/devops/controllers/pipeline.(*Controller).processNextWorkItem.func1(0xc000880c80, 0x1a202a0, 0xc002575a50, 0x0, 0x0)

/workspace/controllers/pipeline/pipeline_controller.go:157 +0xe7

kubesphere.io/devops/controllers/pipeline.(*Controller).processNextWorkItem(0xc000880c80, 0x203001)

/workspace/controllers/pipeline/pipeline_controller.go:164 +0x4d

kubesphere.io/devops/controllers/pipeline.(*Controller).worker(...)

/workspace/controllers/pipeline/pipeline_controller.go:175

k8s.io/apimachinery/pkg/util/wait.BackoffUntil.func1(0xc00175e220)

/go/pkg/mod/k8s.io/[email protected]/pkg/util/wait/wait.go:155 +0x5f

k8s.io/apimachinery/pkg/util/wait.BackoffUntil(0xc00175e220, 0x200e280, 0xc001a86360, 0x1, 0xc000ad2180)

/go/pkg/mod/k8s.io/[email protected]/pkg/util/wait/wait.go:156 +0x9b

k8s.io/apimachinery/pkg/util/wait.JitterUntil(0xc00175e220, 0x3b9aca00, 0x0, 0x1, 0xc000ad2180)

/go/pkg/mod/k8s.io/[email protected]/pkg/util/wait/wait.go:133 +0x98

k8s.io/apimachinery/pkg/util/wait.Until(0xc00175e220, 0x3b9aca00, 0xc000ad2180)

/go/pkg/mod/k8s.io/[email protected]/pkg/util/wait/wait.go:90 +0x4d

created by kubesphere.io/devops/controllers/pipeline.(*Controller).Run

/workspace/controllers/pipeline/pipeline_controller.go:195 +0x1f0

Relevant log output

No response

Additional information

No response

What is version of KubeSphere DevOps has the issue?

v3.3.1

How did you install the Kubernetes? Or what is the Kubernetes distribution?

kubekey

What happened?

Users can not understand the parameters when create continuous deployment, they should open the doc together: https://kubesphere.io/zh/docs/v3.3/devops-user-guide/how-to-use/continuous-deployments/use-gitops-for-continous-deployment/#%E5%88%9B%E5%BB%BA%E6%8C%81%E7%BB%AD%E9%83%A8%E7%BD%B2

Suggest to add some info around the parameters, then users can use the create page only

Relevant log output

No response

Additional information

No response

What is version of KubeSphere DevOps has the issue?

v3.3.1

How did you install the Kubernetes? Or what is the Kubernetes distribution?

kubekey

What happened?

degrade， 建议改成 被降级， 这里表示 某些资源未达到 健康状态。（healthy 是 100% 所有资源都是健康的， 所以其实 degrade 也算 部分健康 ） missing， 建议改成 缺失， 这里就是表明 没找到资源， 丢失感觉有点主观概念。 suspended，建议改成 已暂停，比如一个 cronjob，暂停，会处于这种状态，翻译成已下架 不太合适。

Relevant log output

No response

Additional information

No response

What is version of KubeSphere DevOps has the issue?

v3.3.1

How did you install the Kubernetes? Or what is the Kubernetes distribution?

kubekey

Describe this feature

User need scan the repo first, then show the branch, and is able to run.

Now there is a run on console just after create the multi branch pipeline, user will click the run, and it will show an error.

Additional information

No response

What is version of KubeSphere DevOps has the issue?

v3.3.1

How did you install the Kubernetes? Or what is the Kubernetes distribution?

kubekey

What happened?

Jenkinsfile:

pipeline {
  agent {
    node {
      label 'java'
    }

  }
  stages {
    stage('stage-pk518') {
      agent none
      steps {
        input(message: 'release image with tag?', submitter: 'stark2')
        checkout([$class: 'GitSCM', 
        doGenerateSubmoduleConfigurations: false,
        submoduleCfg: [],
        extensions: [[$class: 'CloneOption', depth: 1, noTags: false, reference: '', shallow: true]],
        userRemoteConfigs: [[
          url: 'https://github.com/chilianyi/jenkins-test.git'
          ]]
])
      }
    }

  }
}

Max build record set to 2.

Run some pipelineruns, the pipelinerun need to review, When cancel the pipelinerun, the build will be deleted by jenkins, then it will change to not running status

Relevant log output

No response

Additional information

No response

What is version of KubeSphere DevOps has the issue?

v3.3.1

How did you install the Kubernetes? Or what is the Kubernetes distribution?

kubekey

Describe this feature

# kubectl get pipelinerun -n starkxhqxb | grep stark-
stark-4z2zh    Pending     48m
stark-59zll    Pending     48m
stark-846zm    Running     127m
stark-8scb7    Running     127m
stark-l4kkf    Running     127m
stark-n7ckp    Failed      48m
stark-ngddd    Pending     36m
stark-p7kxm    Running     127m
stark-q9j9p    Running     128m

It is hard to match pipelinerun cr with run records in console.

Backend feature:

1. Add run id in pipeline cr.
2. Keep the same status between pipeline cr with run records in console.

Frontend feature:

1. Able to show run id for not running pipelinerun, if it has run id in pipelinerun cr

# kubectl get pipelinerun stark-q9j9p -n starkxhqxb -o yaml
apiVersion: devops.kubesphere.io/v1alpha3
kind: PipelineRun
metadata:
  annotations:
    devops.kubesphere.io/creator: admin
    devops.kubesphere.io/jenkins-pipelinerun-id: "14"
    devops.kubesphere.io/jenkins-pipelinerun-stages-status: "null"
    devops.kubesphere.io/jenkins-pipelinerun-status: "null"
  creationTimestamp: "2022-12-07T04:54:03Z"

Additional information

No response