chore: enable blobfuse-proxy by default in kubectl install

[andyzhangx]

What type of PR is this?
/kind cleanup

What this PR does / why we need it:
chore: enable blobfuse-proxy by default in kubectl install

Which issue(s) this PR fixes:

Fixes #

Requirements:

• uses conventional commit messages
• includes documentation
• adds unit tests
• tested upgrade from previous version

Special notes for your reviewer:

Release note:

none

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: andyzhangx

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [andyzhangx]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[andyzhangx]

/retest

[andyzhangx]

/retest

[andyzhangx]

/retest

[andyzhangx]

/cherrypick release-1.24

[andyzhangx]

/cherrypick release-1.23

[andyzhangx]

/cherrypick release-1.22

[k8s-infra-cherrypick-robot]

@andyzhangx: new pull request created: #1631

In response to this:

/cherrypick release-1.23

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-sigs/prow repository.

[k8s-infra-cherrypick-robot]

@andyzhangx: new pull request created: #1632

In response to this:

/cherrypick release-1.24

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-sigs/prow repository.

[k8s-infra-cherrypick-robot]

@andyzhangx: #1630 failed to apply on top of branch "release-1.22":

Applying: chore: enable blobfuse-proxy by default in kubectl install
Applying: doc: support example pod running on arm64 node
Using index info to reconstruct a base tree...
A	deploy/example/cloning/nginx-pod-restored-cloning.yaml
M	deploy/example/nginx-blobfuse-inline-volume.yaml
M	deploy/example/nginx-pod-blob.yaml
M	deploy/example/statefulset-nfs.yaml
M	deploy/example/statefulset.yaml
Falling back to patching base and 3-way merge...
Auto-merging deploy/example/statefulset.yaml
Auto-merging deploy/example/statefulset-nfs.yaml
Auto-merging deploy/example/nginx-pod-blob.yaml
Auto-merging deploy/example/nginx-blobfuse-inline-volume.yaml
CONFLICT (modify/delete): deploy/example/cloning/nginx-pod-restored-cloning.yaml deleted in HEAD and modified in doc: support example pod running on arm64 node. Version doc: support example pod running on arm64 node of deploy/example/cloning/nginx-pod-restored-cloning.yaml left in tree.
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config advice.mergeConflict false"
Patch failed at 0002 doc: support example pod running on arm64 node

In response to this:

/cherrypick release-1.22

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-sigs/prow repository.