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
Comments
/priority high |
/assign |
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. |
I think this issue has been resolved, please refer to
I'm going to close this issue. |
@JohnNiang: Closing this issue. In response to this:
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. |
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
Alternative
You can use kubectl to deploy your desired application into a cluster. For instance, you can learn from the following snippet:
FAQ
/area devops
The text was updated successfully, but these errors were encountered: