Request to add restriction about the DevOps CD feature

LinuxSuRen commented 2 years ago

Provide a restriction statement for the DevOps CD feature.

Background

Since v3.0.0, in the DevOps component, the version of Jenkins plugin kubernets-cd is 2.3.1. You will find out it is out of maintenance if you try to see the commit history of it. The last release commit was in the last year.

As we mentioned in https://github.com/kubesphere/ks-devops/issues/137, we don't have any strong reason to keep using this solution anymore. Please keep reading the following content if you want to know more details.

kubernetes-cd-plugin relies on the Kubernetes Java client. For this version, it can keep compatible from Kubernetes 1.9 to 1.15. Make it be short, please notice the version of your Kubernetes cluster before using it.

Conclusion

Put a known issue. Please make sure your Kubernetes cluster version is in the range from 1.9 to 1.15 before using the following CD feature.
Provide an alternative solution.

Alternative

You can use kubectl to deploy your desired application into a cluster. For instance, you can learn from the following snippet:

    stage('deploy') {
      steps {
        container ('base') {
          sh '''
          kubectl apply -f your-crd-file.yaml
          '''
        }
      }

[x] #2693

FAQ

Is that possible to use a GitOps framework to deploy my applications?
- Yes, totally. You can definitely adapt it, such as Argo CD. But you might need to deploy Argo CD by yourself before we support it out-of-box.

/area devops

LinuxSuRen commented 2 years ago

/priority high

LinuxSuRen commented 2 years ago

/assign

Felixnoo commented 2 years ago

I think we can track all the PRs that update DevOps documents in order to respond, directly or indirectly, to the request in this issue.

JohnNiang commented 2 years ago

I think this issue has been resolved, please refer to

I'm going to close this issue. /close

ks-ci-bot commented 2 years ago

@JohnNiang: Closing this issue.

In response to [this](https://github.com/kubesphere/website/issues/2096#issuecomment-996462248): >I think this issue has been resolved, please refer to >- https://github.com/kubesphere/console/issues/2612 >- https://github.com/kubesphere/website/pull/2098 >- https://github.com/kubesphere/website/pull/2187 >- https://github.com/kubesphere/devops-maven-sample/issues/4 > >I'm going to close this issue. >/close Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.

kubesphere / website