[BUG] Cannot setup openyurt with `yurtctl convert --provider kind` #484

Congrool · 2021-09-21T12:18:21Z

What happened:
Hello, I'd like to deploy the openyurt cluster with yurtctl and kind. It seems that yurtctl supports kind with option --provider kind. However, when I used the following command, it resulted in error.

yurtctl convert -t --provider kind --cloud-nodes ${cloudnodes}

F0921 08:08:07.173618   12871 convert.go:98] fail to complete the convert option: failed to read file /etc/systemd/system/kubelet.service.d/10-kubeadm.conf, open /etc/systemd/system/kubelet.service.d/10-kubeadm.conf: no such file or directory

I read the code and found that when yurtctl starts, it will read the 10-kubeadm.conf (at /etc/systemd/system/kubelet.service.d/10-kubeadm.conf in default) to get pod manifest path. However, the file and directory does not exsit when using kind. Maybe we should come out a better way to solve it.

What you expected to happen:
We can use yurtctl to deploy openyurt with kind.

How to reproduce it (as minimally and precisely as possible):
Use yurtctl convert -t --provider kind --cloud-nodes ${cloudnodes} to deploy openyurt with kind.

Environment:

OpenYurt version: commit: 797c43d
Kubernetes version (use kubectl version): 1.20

The text was updated successfully, but these errors were encountered:

rambohe-ch · 2021-09-21T13:23:29Z

@Peeknut Would you be able to help fix this problem?

adamzhoul · 2021-09-22T01:07:53Z

what about using --kubeadm-conf-path for now?

Congrool · 2021-09-22T01:28:49Z

@adamzhoul , Hello, I find some 10-kubeadm.conf in my local file system.

locate 10-kubeadm.conf
${GOPATH}/pkg/mod/sigs.k8s.io/kind@v0.11.1/images/base/files/etc/systemd/system/kubelet.service.d/10-kubeadm.conf
${GOPATH}/src/github.com/kubernetes/build/debs/10-kubeadm.conf
${GOPATH}/src/github.com/kubernetes/build/rpms/10-kubeadm.conf

However, none of them looks like the right file.

I tried the first one, and new error occurred. Maybe it's not a right way.

get kubeadm-conf-path: ${GOPATH}/pkg/mod/sigs.k8s.io/kind@v0.11.1/images/base/files/etc/systemd/system/kubelet.service.d/10-kubeadm.conffailed to get pod manifest path
F0922 09:44:40.800540   64458 convert.go:98] fail to complete the convert option: failed to read file /var/lib/kubelet/config.yaml, open /var/lib/kubelet/config.yaml: no such file or directory

adamzhoul · 2021-09-22T01:58:21Z

try run yurtctl in kind node

adamzhoul · 2021-09-22T03:02:26Z

Now we read the podManifests path from kubeadm file.

pass podManifests path to the disable-node job. (this requires kubeadm exists at local, so this is a problem)
pass kubeadm path to the revert edgenode job. (this doesn’t require kubeadm to exist at local, so this is not a problem)

in all: this leads to a problem when yurtctl is not in the cluster node.

Solutions:

add —podManifests back, which is not recommended personally.
use default podManifest value when kubeadm is not exists. this may lead the disable-node job to fail when podManifest dir is not right.
pass —kubeadm to disable-node job, which may lead to more complicated implementation.

    config_path=`grep -o -E '\-\-config=.*.yaml' {{.kubeadm_conf_path}} |awk -F'=' '{print  $2}’`
    pod_manifest_path=`grep -o -E 'staticPodPath:\ .*' $config_path|awk '{print $2}'`
    nsenter -t 1 -m -u -n -i -- sed -i 's/--controllers=/--controllers=-nodelifecycle,/g' $pod_manifest_path/kube-controller-manager.yaml

others.

@rambohe-ch @Congrool @Peeknut what do you think?

Peeknut · 2021-09-22T03:07:50Z

@adamzhoul , Hello, I find some 10-kubeadm.conf in my local file system.

locate 10-kubeadm.conf
${GOPATH}/pkg/mod/sigs.k8s.io/kind@v0.11.1/images/base/files/etc/systemd/system/kubelet.service.d/10-kubeadm.conf
${GOPATH}/src/github.com/kubernetes/build/debs/10-kubeadm.conf
${GOPATH}/src/github.com/kubernetes/build/rpms/10-kubeadm.conf

However, none of them looks like the right file.

I tried the first one, and new error occurred. Maybe it's not a right way.

get kubeadm-conf-path: ${GOPATH}/pkg/mod/sigs.k8s.io/kind@v0.11.1/images/base/files/etc/systemd/system/kubelet.service.d/10-kubeadm.conffailed to get pod manifest path
F0922 09:44:40.800540   64458 convert.go:98] fail to complete the convert option: failed to read file /var/lib/kubelet/config.yaml, open /var/lib/kubelet/config.yaml: no such file or directory

Does 10-kubeadm.conf in dir /usr/lib/systemd/system/kubelet.service.d/ ?

Congrool · 2021-09-22T03:12:19Z

@Peeknut There's no /usr/lib/systemd/system/kubelet.service.d/ as well in my local file system.

ls /usr/lib/systemd/system/kubelet.service.d/
ls: cannot access '/usr/lib/systemd/system/kubelet.service.d/': No such file or directory

Peeknut · 2021-09-22T03:25:30Z

@Peeknut There's no /usr/lib/systemd/system/kubelet.service.d/ as well in my local file system.
ls /usr/lib/systemd/system/kubelet.service.d/
ls: cannot access '/usr/lib/systemd/system/kubelet.service.d/': No such file or directory

Could you show the file 10-kubeadm.conf content?

Congrool · 2021-09-22T03:48:05Z

@Peeknut
Well, the content of the file is as following:

cat ${GOPATH}/pkg/mod/sigs.k8s.io/kind@v0.11.1/images/base/files/etc/systemd/system/kubelet.service.d/10-kubeadm.conf
# https://github.com/kubernetes/kubernetes/blob/ba8fcafaf8c502a454acd86b728c857932555315/build/debs/10-kubeadm.conf
# Note: This dropin only works with kubeadm and kubelet v1.11+
[Service]
Environment="KUBELET_KUBECONFIG_ARGS=--bootstrap-kubeconfig=/etc/kubernetes/bootstrap-kubelet.conf --kubeconfig=/etc/kubernetes/kubelet.conf"
Environment="KUBELET_CONFIG_ARGS=--config=/var/lib/kubelet/config.yaml"
# This is a file that "kubeadm init" and "kubeadm join" generates at runtime, populating the KUBELET_KUBEADM_ARGS variable dynamically
EnvironmentFile=-/var/lib/kubelet/kubeadm-flags.env
# This is a file that the user can use for overrides of the kubelet args as a last resort. Preferably, the user should use
# the .NodeRegistration.KubeletExtraArgs object in the configuration files instead. KUBELET_EXTRA_ARGS should be sourced from this file.
EnvironmentFile=-/etc/default/kubelet
# On cgroup v1, the /kubelet cgroup is created in the entrypoint script before running systemd.
# On cgroup v2, the /kubelet cgroup is created here. (See the comments in the entrypoint script for the reason.)
ExecStartPre=/bin/sh -euc "if [ -f /sys/fs/cgroup/cgroup.controllers ]; then create-kubelet-cgroup-v2; fi"
ExecStart=
ExecStart=/usr/bin/kubelet $KUBELET_KUBECONFIG_ARGS $KUBELET_CONFIG_ARGS $KUBELET_KUBEADM_ARGS $KUBELET_EXTRA_ARGS --cgroup-root=/kubelet

It's the same as the file in the kind repo.

@adamzhoul
I tried to run yurtctl in the kind node.

yurtctl convert --cloud-nodes openyurt-e2e-test-control-plane -t --provider kubeadm

It works.

root@openyurt-e2e-test-control-plane:~/openyurt# ./yurtctl convert --cloud-nodes openyurt-e2e-test-control-plane -t --provider kubeadm
get kubeadm-conf-path: /etc/systemd/system/kubelet.service.d/10-kubeadm.confget PodManifestPath: /etc/kubernetes/manifestsI0922 03:38:39.504680    2808 convert.go:318] mark openyurt-e2e-test-control-plane as the cloud-node
I0922 03:40:00.021463    2808 util.go:492] servant job(yurtctl-disable-node-controller-openyurt-e2e-test-control-plane) has succeeded
I0922 03:40:00.021570    2808 convert.go:343] complete disabling node-controller
I0922 03:40:00.489607    2808 convert.go:354] yurt-tunnel-server is deployed
I0922 03:40:00.525977    2808 convert.go:362] yurt-tunnel-agent is deployed
I0922 03:40:00.600863    2808 convert.go:433] kube-public/cluster-info configmap already exists, skip to prepare it
I0922 03:40:00.682505    2808 convert.go:390] deploying the yurt-hub and resetting the kubelet service...
E0922 03:42:00.797153    2808 util.go:489] fail to run servant job(yurtctl-servant-convert-openyurt-e2e-test-worker): wait for job to be complete timeout
I0922 03:42:00.797216    2808 convert.go:413] complete deploying yurt-hub

I think it's better to enable users to run yurtctl locally without exec into kind node when --provider kind is set.

Peeknut · 2021-09-22T05:27:28Z

@Peeknut
Well, the content of the file is as following:

cat ${GOPATH}/pkg/mod/sigs.k8s.io/kind@v0.11.1/images/base/files/etc/systemd/system/kubelet.service.d/10-kubeadm.conf
# https://github.com/kubernetes/kubernetes/blob/ba8fcafaf8c502a454acd86b728c857932555315/build/debs/10-kubeadm.conf
# Note: This dropin only works with kubeadm and kubelet v1.11+
[Service]
Environment="KUBELET_KUBECONFIG_ARGS=--bootstrap-kubeconfig=/etc/kubernetes/bootstrap-kubelet.conf --kubeconfig=/etc/kubernetes/kubelet.conf"
Environment="KUBELET_CONFIG_ARGS=--config=/var/lib/kubelet/config.yaml"
# This is a file that "kubeadm init" and "kubeadm join" generates at runtime, populating the KUBELET_KUBEADM_ARGS variable dynamically
EnvironmentFile=-/var/lib/kubelet/kubeadm-flags.env
# This is a file that the user can use for overrides of the kubelet args as a last resort. Preferably, the user should use
# the .NodeRegistration.KubeletExtraArgs object in the configuration files instead. KUBELET_EXTRA_ARGS should be sourced from this file.
EnvironmentFile=-/etc/default/kubelet
# On cgroup v1, the /kubelet cgroup is created in the entrypoint script before running systemd.
# On cgroup v2, the /kubelet cgroup is created here. (See the comments in the entrypoint script for the reason.)
ExecStartPre=/bin/sh -euc "if [ -f /sys/fs/cgroup/cgroup.controllers ]; then create-kubelet-cgroup-v2; fi"
ExecStart=
ExecStart=/usr/bin/kubelet $KUBELET_KUBECONFIG_ARGS $KUBELET_CONFIG_ARGS $KUBELET_KUBEADM_ARGS $KUBELET_EXTRA_ARGS --cgroup-root=/kubelet

It's the same as the file in the kind repo.

@adamzhoul
I tried to run yurtctl in the kind node.

yurtctl convert --cloud-nodes openyurt-e2e-test-control-plane -t --provider kubeadm

It works.

root@openyurt-e2e-test-control-plane:~/openyurt# ./yurtctl convert --cloud-nodes openyurt-e2e-test-control-plane -t --provider kubeadm
get kubeadm-conf-path: /etc/systemd/system/kubelet.service.d/10-kubeadm.confget PodManifestPath: /etc/kubernetes/manifestsI0922 03:38:39.504680    2808 convert.go:318] mark openyurt-e2e-test-control-plane as the cloud-node
I0922 03:40:00.021463    2808 util.go:492] servant job(yurtctl-disable-node-controller-openyurt-e2e-test-control-plane) has succeeded
I0922 03:40:00.021570    2808 convert.go:343] complete disabling node-controller
I0922 03:40:00.489607    2808 convert.go:354] yurt-tunnel-server is deployed
I0922 03:40:00.525977    2808 convert.go:362] yurt-tunnel-agent is deployed
I0922 03:40:00.600863    2808 convert.go:433] kube-public/cluster-info configmap already exists, skip to prepare it
I0922 03:40:00.682505    2808 convert.go:390] deploying the yurt-hub and resetting the kubelet service...
E0922 03:42:00.797153    2808 util.go:489] fail to run servant job(yurtctl-servant-convert-openyurt-e2e-test-worker): wait for job to be complete timeout
I0922 03:42:00.797216    2808 convert.go:413] complete deploying yurt-hub

I think it's better to enable users to run yurtctl locally without exec into kind node when --provider kind is set.

Currently the value of parameter --provider (kind or kubeadm ) has no effect. So if the command yurtctl convert --cloud-nodes openyurt-e2e-test-control-plane -t --provider kubeadm can work, so can command yurtctl convert -t --provider kind --cloud-nodes ${cloudnodes}.

Peeknut · 2021-09-22T05:29:19Z

@adamzhoul , Hello, I find some 10-kubeadm.conf in my local file system.

locate 10-kubeadm.conf
${GOPATH}/pkg/mod/sigs.k8s.io/kind@v0.11.1/images/base/files/etc/systemd/system/kubelet.service.d/10-kubeadm.conf
${GOPATH}/src/github.com/kubernetes/build/debs/10-kubeadm.conf
${GOPATH}/src/github.com/kubernetes/build/rpms/10-kubeadm.conf

However, none of them looks like the right file.

I tried the first one, and new error occurred. Maybe it's not a right way.

get kubeadm-conf-path: ${GOPATH}/pkg/mod/sigs.k8s.io/kind@v0.11.1/images/base/files/etc/systemd/system/kubelet.service.d/10-kubeadm.conffailed to get pod manifest path
F0922 09:44:40.800540   64458 convert.go:98] fail to complete the convert option: failed to read file /var/lib/kubelet/config.yaml, open /var/lib/kubelet/config.yaml: no such file or directory

The err msg show open /var/lib/kubelet/config.yaml: no such file or directory, but 10-kubeadm.conf is configured with Environment="KUBELET_CONFIG_ARGS=--config=/var/lib/kubelet/config.yaml", please check whether /var/lib/kubelet/config.yaml really exists.

adamzhoul · 2021-09-22T05:34:16Z

@Peeknut
I think his core poblem is: yurtctl run in local pc not in cluster node.
kubeadm.conf config.yaml may not exists, and it’s ok they are not.

Congrool · 2021-09-22T05:39:00Z

Currently the value of parameter --provider (kind or kubeadm ) has no effect. So if the command yurtctl convert --cloud-nodes openyurt-e2e-test-control-plane -t --provider kubeadm can work, so can command yurtctl convert -t --provider kind --cloud-nodes ${cloudnodes}.

@Peeknut Yes. Both --provider kubeadm and --provider kind can work in the kind node (through docker exec -it openyurt-e2e-test-control-plane bash) while cannot work in the local host (where the kind cluster is running on).

I mean if we can support deploying openyurt without exec into the docker container when we set --provider kind.

Peeknut · 2021-09-22T05:50:31Z

Oo, I got it.
Yes, we can consider supporting this feature.

Peeknut · 2021-09-22T06:04:11Z

Now we read the podManifests path from kubeadm file.

pass podManifests path to the disable-node job. (this requires kubeadm exists at local, so this is a problem)

pass kubeadm path to the revert edgenode job. (this doesn’t require kubeadm to exist at local, so this is not a problem)

in all: this leads to a problem when yurtctl is not in the cluster node.

Solutions:

add —podManifests back, which is not recommended personally.

use default podManifest value when kubeadm is not exists. this may lead the disable-node job to fail when podManifest dir is not right.

pass —kubeadm to disable-node job, which may lead to more complicated implementation.
    config_path=`grep -o -E '\-\-config=.*.yaml' {{.kubeadm_conf_path}} |awk -F'=' '{print  $2}’`
    pod_manifest_path=`grep -o -E 'staticPodPath:\ .*' $config_path|awk '{print $2}'`
    nsenter -t 1 -m -u -n -i -- sed -i 's/--controllers=/--controllers=-nodelifecycle,/g' $pod_manifest_path/kube-controller-manager.yaml
others.

@rambohe-ch @Congrool @Peeknut what do you think?

For disable node-controller job，consider passing in "kubeadm_conf_path" instead of "pod_manifest_path". Because:
1)It can support the situation yurtctl is not in the cluster node.
2)It is indeed better to obtain the pod-manifest-path according to the actual situation of the node instead of uniformly passing in the parameter pod-manifest-path in the cloud.

Solution 2 (Using the default value) has the same effect as the parameters passed in now.(that is, we assume that the pod-manifest-path on the node is the same by default).
Solution 3 is really complicated. How about considers adding a yurctl subcommand to close the node controller?

adamzhoul · 2021-09-22T06:19:17Z

what do you mean by adding a subcommand？

Peeknut · 2021-09-22T06:37:57Z

what do you mean by adding a subcommand？

Maybe just like yurtctl convert controller-plane, and the disable node-controller job can ues it?

adamzhoul · 2021-09-22T08:39:46Z

Is this means?

remove disable node-controller from yurtctl convert
run yurtctl disable node-controller

I think this may lead to :

large size of code update
the user has to run two commands to do one convert job.

Peeknut · 2021-09-22T11:02:36Z

Is this means?

remove disable node-controller from yurtctl convert

run yurtctl disable node-controller

I think this may lead to :

large size of code update

the user has to run two commands to do one convert job.

yes, maybe should compare solutions or find other solutions.

adamzhoul · 2021-09-26T03:10:39Z

for now, solution 3 can be the quickest way and has a small size code updated.

pass —kubeadm to disable-node job, which may lead to more complicated implementation.

config_path=`grep -o -E '\-\-config=.*.yaml' {{.kubeadm_conf_path}} |awk -F'=' '{print  $2}’`
pod_manifest_path=`grep -o -E 'staticPodPath:\ .*' $config_path|awk '{print $2}'`
nsenter -t 1 -m -u -n -i -- sed -i 's/--controllers=/--controllers=-nodelifecycle,/g' $pod_manifest_path/kube-controller-manager.yaml

after all, run yurtctl outside of the cluster is really convenient and attractive.
especially when debugging code.

what do you think? @Peeknut @Congrool @rambohe-ch

Peeknut · 2021-09-26T12:05:26Z

Yes, this can solve the problem, but maybe using the code form is more elegant than using the linux command.
What do you think？@rambohe-ch

rambohe-ch · 2021-09-27T03:27:24Z

for now, solution 3 can be the quickest way and has a small size code updated.

pass —kubeadm to disable-node job, which may lead to more complicated implementation.
config_path=`grep -o -E '\-\-config=.*.yaml' {{.kubeadm_conf_path}} |awk -F'=' '{print  $2}’`
pod_manifest_path=`grep -o -E 'staticPodPath:\ .*' $config_path|awk '{print $2}'`
nsenter -t 1 -m -u -n -i -- sed -i 's/--controllers=/--controllers=-nodelifecycle,/g' $pod_manifest_path/kube-controller-manager.yaml
after all, run yurtctl outside of the cluster is really convenient and attractive.
especially when debugging code.

what do you think? @Peeknut @Congrool @rambohe-ch

@adamzhoul @Peeknut how about define staticPodPath as /etc/kubernetes/manifests?
the reasons as following:

all tools(kubeadm/minikube/kind) use /etc/kubernetes/manifests as staticPodPath, and users rarely modify these setting.
the code will more readable and simpler. we don't need to consider how to get staticPodPath from config.yaml or pass staticPodPath from cloud to edge.
we can add some before you begin introductions in tutorials like make sure that kubelet use /etc/kubernetes/manifests as staticPodPath.

if staticPodPath is not /etc/kubernetes/manifests, users are advised to install OpenYurt manually.

adamzhoul · 2021-09-27T09:20:04Z

Do you mean hard code? Something like：

   const staticPodPath = "/etc/kubernetes/manifests"

I agree with that.

we can add some before you begin introductions in tutorials like make sure that kubelet use /etc/kubernetes/manifests as staticPodPath.

Only put this into before you begin looks a little strange.

if staticPodPath is not /etc/kubernetes/manifests, users are advised to install OpenYurt manually.

what about creating a link？ manually install is really difficult.

ln -s realPath /etc/kubernetes/manifests

rambohe-ch · 2021-09-27T11:33:05Z

@adamzhoul Thank you for your feedback.

Do you mean hard code? Something like：
   const staticPodPath = "/etc/kubernetes/manifests"

yes, use hard code to define staticPodPath.

what about creating a link？ manually install is really difficult.
ln -s realPath /etc/kubernetes/manifests

It's a good idea, we can also add soft link for staticPodPath in before you begin of tutorial docs.

rambohe-ch · 2021-09-27T11:33:35Z

@adamzhoul Would you like to take over and fix this bug?

adamzhoul · 2021-09-27T14:27:20Z

sure

rambohe-ch · 2021-09-28T01:59:25Z

/assign @adamzhoul

adamzhoul · 2021-09-28T07:41:21Z

still, I don't think we need to put something in Before you begin

this dir is hardly changed
we only support the cluster installed by minikube, kubeadm, kind. we are only following their config.
put this in Before you begin looks like we have some special design while we are not
less in Before you begin less pressure for beginners.

@rambohe-ch

rambohe-ch · 2021-09-29T06:08:13Z

still, I don't think we need to put something in Before you begin

this dir is hardly changed

we only support the cluster installed by minikube, kubeadm, kind. we are only following their config.

put this in Before you begin looks like we have some special design while we are not

less in Before you begin less pressure for beginners.

@rambohe-ch

@adamzhoul how about add some introduction in troubleshooting tutorial? https://github.com/openyurtio/openyurt/blob/master/docs/tutorial/yurtctl.md#troubleshooting

adamzhoul · 2021-09-29T09:13:01Z

good idea

Congrool added the kind/bug kind/bug label Sep 21, 2021

Congrool mentioned this issue Sep 21, 2021

[Question] Develop Guide Help #467

Closed

Congrool changed the title ~~[BUG] Cannot setup openyurt wich yurtctl convert --provider kind~~ [BUG] Cannot setup openyurt with yurtctl convert --provider kind Sep 22, 2021

openyurt-bot assigned adamzhoul Sep 28, 2021

adamzhoul mentioned this issue Sep 28, 2021

use default staticPath #506

Merged

openyurt-bot closed this as completed in #506 Oct 10, 2021

Congrool mentioned this issue Oct 13, 2021

[REQUEST Membership]: New membership for Congrool openyurtio/community#30

Closed

6 tasks

Congrool mentioned this issue Jan 26, 2022

add Congrool as reviewer of OpenYurt #726

Merged

6 tasks

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

[BUG] Cannot setup openyurt with `yurtctl convert --provider kind` #484

[BUG] Cannot setup openyurt with `yurtctl convert --provider kind` #484

Congrool commented Sep 21, 2021

rambohe-ch commented Sep 21, 2021

adamzhoul commented Sep 22, 2021

Congrool commented Sep 22, 2021 •

edited

Loading

adamzhoul commented Sep 22, 2021

adamzhoul commented Sep 22, 2021

Peeknut commented Sep 22, 2021

Congrool commented Sep 22, 2021

Peeknut commented Sep 22, 2021

Congrool commented Sep 22, 2021

Peeknut commented Sep 22, 2021

Peeknut commented Sep 22, 2021

adamzhoul commented Sep 22, 2021 •

edited

Loading

Congrool commented Sep 22, 2021

Peeknut commented Sep 22, 2021

Peeknut commented Sep 22, 2021 •

edited

Loading

adamzhoul commented Sep 22, 2021

Peeknut commented Sep 22, 2021

adamzhoul commented Sep 22, 2021

Peeknut commented Sep 22, 2021

adamzhoul commented Sep 26, 2021

Peeknut commented Sep 26, 2021

rambohe-ch commented Sep 27, 2021 •

edited

Loading

adamzhoul commented Sep 27, 2021

rambohe-ch commented Sep 27, 2021 •

edited

Loading

rambohe-ch commented Sep 27, 2021

adamzhoul commented Sep 27, 2021

rambohe-ch commented Sep 28, 2021

adamzhoul commented Sep 28, 2021

rambohe-ch commented Sep 29, 2021

adamzhoul commented Sep 29, 2021

[BUG] Cannot setup openyurt with yurtctl convert --provider kind #484

[BUG] Cannot setup openyurt with yurtctl convert --provider kind #484

Comments

Congrool commented Sep 21, 2021

rambohe-ch commented Sep 21, 2021

adamzhoul commented Sep 22, 2021

Congrool commented Sep 22, 2021 • edited Loading

adamzhoul commented Sep 22, 2021

adamzhoul commented Sep 22, 2021

Peeknut commented Sep 22, 2021

Congrool commented Sep 22, 2021

Peeknut commented Sep 22, 2021

Congrool commented Sep 22, 2021

Peeknut commented Sep 22, 2021

Peeknut commented Sep 22, 2021

adamzhoul commented Sep 22, 2021 • edited Loading

Congrool commented Sep 22, 2021

Peeknut commented Sep 22, 2021

Peeknut commented Sep 22, 2021 • edited Loading

adamzhoul commented Sep 22, 2021

Peeknut commented Sep 22, 2021

adamzhoul commented Sep 22, 2021

Peeknut commented Sep 22, 2021

adamzhoul commented Sep 26, 2021

Peeknut commented Sep 26, 2021

rambohe-ch commented Sep 27, 2021 • edited Loading

adamzhoul commented Sep 27, 2021

rambohe-ch commented Sep 27, 2021 • edited Loading

rambohe-ch commented Sep 27, 2021

adamzhoul commented Sep 27, 2021

rambohe-ch commented Sep 28, 2021

adamzhoul commented Sep 28, 2021

rambohe-ch commented Sep 29, 2021

adamzhoul commented Sep 29, 2021

[BUG] Cannot setup openyurt with `yurtctl convert --provider kind` #484

[BUG] Cannot setup openyurt with `yurtctl convert --provider kind` #484

Congrool commented Sep 22, 2021 •

edited

Loading

adamzhoul commented Sep 22, 2021 •

edited

Loading

Peeknut commented Sep 22, 2021 •

edited

Loading

rambohe-ch commented Sep 27, 2021 •

edited

Loading

rambohe-ch commented Sep 27, 2021 •

edited

Loading