You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What happened:
kubeadm supports for generating manifest for all components except workload-contorller-manager What you expected to happen:
kubeadm should support to generate manifest for workload-controller-manager How to reproduce it (as minimally and precisely as possible):
this PR use hardcoded manifest: https://github.com/futurewei-cloud/arktos/pull/211 Anything else we need to know?: https://github.com/futurewei-cloud/arktos/pull/211
per this issue, kube-up and start-kubemark using different way for only workload-controller-manager. after this issue fixed, there is another following issue need be fixed: https://github.com/futurewei-cloud/arktos/issues/218 Environment:
Arktos version (use kubectl version):
Cloud provider or hardware configuration:
OS (e.g: cat /etc/os-release):
Kernel (e.g. uname -a):
Install tools:
Network plugin and version (if this is a network-related bug):
Others:
The text was updated successfully, but these errors were encountered:
What happened:
kubeadm supports for generating manifest for all components except workload-contorller-manager
What you expected to happen:
kubeadm should support to generate manifest for workload-controller-manager
How to reproduce it (as minimally and precisely as possible):
this PR use hardcoded manifest: https://github.com/futurewei-cloud/arktos/pull/211
Anything else we need to know?:
https://github.com/futurewei-cloud/arktos/pull/211
per this issue, kube-up and start-kubemark using different way for only workload-controller-manager. after this issue fixed, there is another following issue need be fixed: https://github.com/futurewei-cloud/arktos/issues/218
Environment:
kubectl version
):cat /etc/os-release
):uname -a
):The text was updated successfully, but these errors were encountered: