Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Request to add restriction about the DevOps CD feature #2096

Closed
1 task done
LinuxSuRen opened this issue Nov 10, 2021 · 5 comments
Closed
1 task done

Request to add restriction about the DevOps CD feature #2096

LinuxSuRen opened this issue Nov 10, 2021 · 5 comments

Comments

@LinuxSuRen
Copy link
Member

LinuxSuRen commented Nov 10, 2021

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 kubesphere/ks-devops#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.

image

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
          '''
        }
      }

FAQ

  • Is that possible to use a GitOps framework to deploy my applications?

/area devops

@LinuxSuRen
Copy link
Member Author

/priority high

@LinuxSuRen
Copy link
Member Author

/assign

@Felixnoo
Copy link
Contributor

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.

@ks-ci-bot
Copy link
Collaborator

@JohnNiang: Closing this issue.

In response to this:

I think this issue has been resolved, please refer to

I'm going to close this issue.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants