What should be cleaned up or changed:

https://github.com/kubernetes-sigs/kind/blob/master/hack/verify/generated.sh already verifies that generated code is up to date and the repo is gofmted

we should also ensure that go mod tidy has run over the modules, t

我刚看了一下其他人都好像有这个问题，不过还是看见有人数可以用renew的办法，我也尝试了一下
kubeadm alpha phase all
初步看好像是续期了一年的样子，但由于我是vmware的1master 3node的。。没有环境测试高可用情况下这样renew证书的话，其他master要怎么操作。

另外贴一下下面的help信息
[root@t0 etcd]# kubeadm alpha phase --help
This command is not meant to be run on its own. See list of available subcommands.

[root@t0 etcd]# kubeadm alpha certs renew --help
This command is not meant to be run on its ow

I started everything as per the instructions in the readme.md file.
After starting metrics server it doesnt show any metrics.

Should I try to start with any change in config of kubeadm ?

https://medium.com/free-code-camp/how-to-set-up-a-serious-kubernetes-terminal-dd07cab51cd4

I changed the Kubernetes version from 1.14.0 to 1.16.0 after I ran the playbook for the first time and then re-run it. It ran trough and updated the packages like this:

TASK [commons/pre-install : Install kubernetes packages (RHEL/CentOS)] ********************************************************************************************************************************************************

Version v0.8.0 of https://github.com/containernetworking/plugins removes code responsible for creating network namespaces: containernetworking/plugins@a0eac8d#diff-d3d859d29b12afe98694dc54a7ced6d9

Rather than using outdated version of dependency, we should probably update and find a way to manage namespaces on our own.

The latest implementation does bot force IP to be defined.
See: https://github.com/containernetworking/cni/blob/master/pkg/types/current/types.go#L107
while the code under local "vendor", has this check:
https://github.com/Huawei-PaaS/CNI-Genie/blob/master/vendor/github.com/containernetworking/cni/pkg/types/current/types.go#L108

This prevents using Genie to add an L2 network to a pod, using

OS running on Ansible host:

NAME="Ubuntu"
VERSION="16.04.5 LTS (Xenial Xerus)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 16.04.5 LTS"
VERSION_ID="16.04"
HOME_URL="http://www.ubuntu.com/"
SUPPORT_URL="http://help.ubuntu.com/"
BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/"
VERSION_CODENAME=xenial
UBUNTU_CODENAME=xenial

Ansible Version (ansible --version):

As per our discussion, after having curled the latest version of kn and run kn apply in an already existing working directory (hence previously initialized with an older version of kn), I am getting this error:

/opt/KubeNow/bin/ssh-agent-wrapper: line 7: kn-apply: command not found

By running ls bin in the working folder I noticed that the command kn-apply does not exist. This is becau

When attempting to run a kurl installer on a node that already has a later k8s version installed, the displayed error message is missing separators between sentences.

actual:
The currently installed kubernetes version is 1.16.4The requested version to upgrade to is 1.15.3Since the currently installed version is newer than the requested version, no action will be taken

expected:

Getting an error on terraform init

Error: Unsupported Terraform Core version

This configuration does not support Terraform version 0.12.1. To proceed,
either choose another supported Terraform version or update the root module's
version constraint. Version constraints are normally set for good reason, so
updating the constraint may lead to other errors or unexpected behavior.

I use this role pretty regularly in a continuous integration pipeline that I have. For some reason, I get this error intermittently. I don't know of an exact way to reproduce it. It just seems to happen randomly:

It honestl

CentOS Linux release 7.6.1810
docker 18.09
kubeadm 1.13

kubeadm init --kubernetes-version=v1.13.0 --pod-network-cidr=10.10.0.0/16 --apiserver-advertise-address=192.168.55.31
wget https://github.com/contiv/install/releases/download/1.2.0/contiv-1.2.0.tgz
tar zxvf contiv-1.2.0.tgz
cd contiv-1.2.0/
./install/k8s/install.sh -n 192.168.55.31
......
contiv netmaster is not ready !!

kubec

All calls to zypper should pass a --userdata value.

SUSE/doc-caasp#644 (comment) raised the question of "how can support detect that a customer did this [call zypper on the node manually] "wrong"?"

zypper has an option to pass a transaction id:

> zypper -h
  ...
    --userdata <STRING>     User defined transaction id used in history an

many people would like to see this feature added, especially when we're talking for projects like openstack-helm and kolla-kubernetes.

i'd like to see CoreOS supported for the project, and this issue is just to track this and let the community know that this is the project's intention. i know we're

We should add some options in the resource "kubeadm" for configuring the cloud provider...

• config options for some cloud providers (ie, OpenStack) (#22)
• config options for other providers that require more configuration actions (ie, AWS)