Such as kubectl expose deployment nginx --port=80 --target-port=8000 , kurise plugin support this cmd for CloneSet, AdvancedStatefulSet.

Reference kubectl docs: https://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#expose

See:
openkruise/kruise#967

We should also allow users to install Kruise using Homebrew.
brew install kruise

openkruise/kruise#857

According kubectl reference , kubectl support create pdb. So that kubectl kruise can support create pub, like
kubectl kruise create podunavailablebudget my-pub --selector=app=rails --min-available=1

Reference openkruise/kruise#964

I get an auth error

$ kubectl-kruise rollout history cloneset plat-demo-28aebeb-20220119030940-test
error: no Auth Provider found for name "oidc"

kubectl kruise set image cloneset/words-app words-app-image='registry-vpc.cn-shanghai.aliyuncs.com/xxx-backend/words-service:2022-04-07_76' -n kube-eyododo --record
error: failed to patch image update to pod template: admission webhook "vcloneset.kb.io" denied the request: spec: Forbidden: only allowed to update images in spec for InPlaceOnly, but found remove /containers/0/env

Add cmd to support selective Pod deletion.

now kruise-tools only implement restarting ReCreate type cloneset, like deployment.
InPlaceOnly/InPlaceIfPossible is needed too.

What would you like to be added:
Support kubectl-kruise top cloneset [cloneset name] so that we can see the resource usage of each cloneset.

Why is this needed:
We often want to have an idea of the resource usage of each cloneset, not only individual pods or nodes.

The metrics server might not allow a direct query of this info, but kubectl performing a local summation of the resource usage of all pods in a cloneset may be worthy.

The 'kruise rollout undo' subcommand cannot roll back multiple batches that are currently being executed.
Get an error: you cannot rollback a paused deployment.

Reference openkruise/kruise#943

kruise rollout undo子命令不能回滚正在执行的多批次rollout，error: you cannot rollback a paused deployment
kruise-rollout-0.5.0
kruise-tools v1.1.0

kubectl kruise create ContainerRecreateRequest --pod my-pod --containers app,sidecar -n pod-namespace

we can leverage this ->https://github.com/sonatype-nexus-community/nancy as an github workflow to scan vulnerability.

Support transform native k8s workload in helm charts to kruise workload, such as kubectl kruise trans -f -t cloneset

当我通过set image替换镜像时不会触发原地升级，diff 一下更换镜像前后两个controllerrevision 对象中的 data 结构发现，执行了set image之后的版本丢失resource、port等配置，从而触发重建升级

kubectl-kruise rollout approve rollout/rollouts-demo -n default

error: no kind "Rollout" is registered for version "rollouts.kruise.io/v1beta1" in scheme "pkg/runtime/scheme.go:100"

kruise-rollout-0.5.0
kruise-tools v1.1.0

The cloneset has finished updating, but kubectl-kruise rollout status can't exit

kubectl-kruise  version
Client Version: version.Info{Major:"1", Minor:"0", GitVersion:"v1.0.4", GitCommit:"e1b55f7d11d906edf31a80ba695bc8857b881b75", GitTreeState:"clean", BuildDate:"2022-07-22T11:51:37Z", GoVersion:"go1.16.15", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"22+", GitVersion:"v1.22.3-aliyun.1", GitCommit:"937757761d3c1db7080f179102b437c26c521ecd", GitTreeState:"clean", BuildDate:"2022-05-26T12:38:52Z", GoVersion:"go1.16.9", Compiler:"gc", Platform:"linux/amd64"}
WARNING: version difference between client (1.0) and server (1.22) exceeds the supported minor version skew of +/-1



kubectl-kruise rollout status cloneset/app-web
Waiting for partitioned roll out to finish: 2 out of 2 new pods have been updated...   // Waiting 

kubectl get po 
app-web-8zqxn       1/1     Running   2 (60m ago)       4d
app-web-wrxhx       1/1     Running   0                 60m

Run: kubectl krew install kruise

Installing plugin: kruise
W0810 10:46:13.929533 5127 install.go:164] failed to install plugin "kruise": install failed: failed to unpack into staging dir: failed to unpack the plugin archive: failed to obtain plugin archive: failed to download "https://github.com/openkruise/kruise-tools/releases/download/v1.0.5/kubectl-kruise-linux-amd64.tar.gz": Get "https://github.com/openkruise/kruise-tools/releases/download/v1.0.5/kubectl-kruise-linux-amd64.tar.gz": unexpected EOF
failed to install some plugins: [kruise]: install failed: failed to unpack into staging dir: failed to unpack the plugin archive: failed to obtain plugin archive: failed to download "https://github.com/openkruise/kruise-tools/releases/download/v1.0.5/kubectl-kruise-linux-amd64.tar.gz": Get "https://github.com/openkruise/kruise-tools/releases/download/v1.0.5/kubectl-kruise-linux-amd64.tar.gz": unexpected EOF

In order to improve the experience, we suggest that expose the service like kubectl expose -h

[root@k8s-1 cloneset]# kubectl get cloneset 
NAME       DESIRED   UPDATED   UPDATED_READY   READY   TOTAL   AGE
cloneset   4         4         4               4       4       12m
[root@k8s-1 cloneset]# kubectl expose cloneset cloneset --port=80 --target-port=8000
error: no kind "CloneSet" is registered for version "apps.kruise.io/v1alpha1" in scheme "k8s.io/kubectl/pkg/scheme/scheme.go:28"
[root@k8s-1 cloneset]# kubectl expose cloneset cloneset --port=80 --target-port=8000
error: no kind "CloneSet" is registered for version "apps.kruise.io/v1alpha1" in scheme "k8s.io/kubectl/pkg/scheme/scheme.go:28"
[root@k8s-1 cloneset]# kubectl expose -h | grep cloneset 
[root@k8s-1 cloneset]# 

Currently kubectl get rollout only display exposed rollout status as columns, however it is vital to display the status of all involved objects as well, e.g. pods, traffic routings objects. So kruise-tools can provide a deep inspection command, in the form of kubectl kruise describe rollout ns/name, and provide the following information:

1. basic rollout spec information and status
2. status of involved pods, e.g. batch number, revision number, pod ready status
3. [optional] gateway status, e.g. important conditions and current listener

In addition, the new describe command should support a watch option, to dynamically update the output during the rollout.

One can use the Argo kubectl plugin as a reference