chinglin

## Events ``` default 7s Normal SuccessfulDataVolumeCreate virtualmachine/vm-centos8 Created DataVolume vm-centos8 default 7s Normal SnapshotForSmartCloneInProgress datavolume/vm-centos8 Creating snapshot for smart-clone is in progress (for pvc default/centos8) default 7s Normal SnapshotForSmartCloneInProgress...

Disable these two feature from kubevirt crd, it's working now. ``` - NonRootExperimental - NonRoot ```

@alicefr ``` kind: PersistentVolumeClaim apiVersion: v1 metadata: name: example-local-claim spec: accessModes: - ReadWriteMany volumeMode: Block resources: requests: storage: 5Gi --- apiVersion: v1 kind: Pod metadata: name: netshoot spec: containers: -...

@alicefr there's no relate pod exist. ``` [root@hcit3 ~]# kubectl get pods NAME READY STATUS RESTARTS AGE virt-launcher-vm-centos8-lijie-cwh7b 1/1 Running 0 6d virt-launcher-vm-centos8-lijie-zfs-pxwcl 1/1 Running 0 6d virt-launcher-vm-centos8-pk2vm 1/1 Running...

events ``` default 33s Normal SuccessfulDataVolumeCreate virtualmachine/vm-fedora-openebszfs-ext4-wait Created DataVolume vm-fedora-openebszfs-ext4-wait default 33s Normal SnapshotForSmartCloneInProgress datavolume/vm-fedora-openebszfs-ext4-wait Creating snapshot for smart-clone is in progress (for pvc default/fedora34-openebs-zfspvx-ext4-wait) default 33s Normal SnapshotForSmartCloneInProgress datavolume/vm-fedora-openebszfs-ext4-wait...

I'll stick with immediate binding mode for now, Since I'm using local provisioner. On Thu, Jun 16, 2022, 19:53 akalenyu ***@***.***> wrote: > Seems like a bug where we don't...

Relate kubernetes issue https://github.com/kubernetes/kubernetes/issues/19161. to help people find here.

I have found that the apiserver itself expose log api as http request. example: ``` http://172.28.46.201:8080/api/v1/namespaces/default/pods/fs-2665028343-9ttqm/log http://172.28.46.201:8080/api/v1/namespaces/qb-qa-10/pods/ops-fs-3957094301-csgxx/log ```

Doing this, seems ok, it seems not compatible with KubeVirt's DataVolume? https://github.com/kubevirt/kubevirt/issues/7754 kube-schedule config ``` [root@hcit3 ~]# cat /etc/kubernetes/scheduler-config.yaml apiVersion: kubescheduler.config.k8s.io/v1beta2 kind: KubeSchedulerConfiguration clientConnection: kubeconfig: /etc/kubernetes/scheduler.conf extenders: - urlPrefix: "http://open-local-scheduler-extender.openlocal:23000/scheduler"...

I'm also encounter the fixed IP allocation feature, if someone consider to implement it, please consider the following case too. I'm thinking about two cases: 1. KubeVirt machine also needs...