Closed mangoGoForward closed 1 year ago
[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: mangoGoForward
To complete the pull request process, please assign linuxsuren after the PR has been reviewed.
You can assign the PR to them by writing /assign @linuxsuren
in a comment when ready.
The full list of commands accepted by this bot can be found here.
I have som problem with devops and servicemesh:
when use common.ExecCommand
to run kubectl patch **
,it throw Error from server: Invalid JSON Patch
, If you has free time, please help me to figure out the problem.
/hold
I have som problem with devops and servicemesh:
when use
common.ExecCommand
to runkubectl patch **
,it throwError from server: Invalid JSON Patch
, If you has free time, please help me to figure out the problem.
I'm wondering if is that possible to use the k8s client instead.
/unhold
I have som problem with devops and servicemesh: when use
common.ExecCommand
to runkubectl patch **
,it throwError from server: Invalid JSON Patch
, If you has free time, please help me to figure out the problem.I'm wondering if is that possible to use the k8s client instead.
Solved
I didn't get any tips when no flags were given. But the flag
--components
is required. How about printing some information to let users know that.[root@node1 ~]# ks uninstall [root@node1 ~]#
For the command
ks install xx
, its responsibility is to create k8s or kubesphere instead of any components. We already have a commandks com enable devops
to enable components. I'm wondering if we can have a command like this:ks com disable devops
orks com unintall devops
.com
meanscomponent
.Is that possible to know if a component exists? See my test case below. For me, this is not a block opinion. You can take it or not.
[root@node1 ~]# ks uninstall --components devops release "devops" uninstalled customresourcedefinition.apiextensions.k8s.io "devopsprojects.devops.kubesphere.io" deleted customresourcedefinition.apiextensions.k8s.io "fakes.devops.kubesphere.io" deleted customresourcedefinition.apiextensions.k8s.io "gitrepositories.devops.kubesphere.io" deleted customresourcedefinition.apiextensions.k8s.io "pipelineruns.devops.kubesphere.io" deleted customresourcedefinition.apiextensions.k8s.io "pipelines.devops.kubesphere.io" deleted customresourcedefinition.apiextensions.k8s.io "s2ibinaries.devops.kubesphere.io" deleted customresourcedefinition.apiextensions.k8s.io "s2ibuilders.devops.kubesphere.io" deleted customresourcedefinition.apiextensions.k8s.io "s2ibuildertemplates.devops.kubesphere.io" deleted customresourcedefinition.apiextensions.k8s.io "s2iruns.devops.kubesphere.io" deleted customresourcedefinition.apiextensions.k8s.io "webhooks.devops.kubesphere.io" deleted namespace "kubesphere-devops-system" deleted [root@node1 ~]# ks uninstall --components devops Error: uninstall: Release not loaded: devops: release: not found Usage: ks uninstall [flags] Examples: ks uninstall --components devops Flags: --components strings Which components will uninstall -h, --help help for uninstall Global Flags: --context string Sets a context entry in kubeconfig the server rejected our request due to an error in our request
Got it. And I noticed that the command of ks com enable
has a flag toggle
, if toggle
is true, it will change clusterconfiguration, but do not remove related resource firstly.
Now I want to use ks com unintall devops
to refactor
Notification is installed in KubeSphere 3.2.1 by default, do we need support enable and uninstall component operator? @LinuxSuRen https://github.com/kubesphere-sigs/ks/blob/e6ef407317595056acc75e429bd68c5bc47cdadf/kubectl-plugin/common/components.go#L4-L9
Notification is installed in KubeSphere 3.2.1 by default, do we need support enable and uninstall component operator?
I am not sure if it can be enable/disable. We can support it if it is true.
I am not sure if it can be enable/disable. We can support it if it is true.
As the uninstall component said, we not need support operation of install or uninstall, so i suggest to remove notification
in function GetPluginAbleComponents
so i suggest to remove notification in function GetPluginAbleComponents
Sure.
For another implement, we can use the tools like istioctl
to install/uninstall our helm charts. They use CRD related to the k8s resources, once we delete these installation CRD, the related k8s resources in the cluster will delete.
@mangoGoForward: PR needs rebase.
Which issue(s) this PR fixes:
246
How to test:
/cc @kubesphere-sigs/sig-devops