1. What kops version are you running? The command kops version, will display
this information.$ kops version Version 1.13.0 (git-be5fb9019)2. What Kubernetes version are you running? kubectl version will print the
version if a cluster is running or provide the Kubernetes version specified as
a kops flag.kubectl version Client Version: version.Info{Major:"1", Minor:"13", GitVersion:"v1.13.10", GitCommit:"37d169313237cb4ceb2cc4bef300f2ae3053c1a2", GitTreeState:"clean", BuildDate:"2019-08-19T10:52:43Z", GoVersion:"go1.11.13", Compiler:"gc", Platform:"darwin/amd64"} Server Version: version.Info{Major:"1", Minor:"13", GitVersion:"v1.13.10", GitCommit:"37d169313237cb4ceb2cc4bef300f2ae3053c1a2", GitTreeState:"clean", BuildDate:"2019-08-19T10:44:49Z", GoVersion:"go1.11.13", Compiler:"gc", Platform:"linux/amd64"}3. What AWS region are you using(Beijing or Ningxia)?Ningxia4. What commands did you run? What is the simplest way to reproduce this issue?
NONE
5. What happened after the commands executed?
NONE
6. What did you expect to happen?
NONE
7. Please provide the content of your Makefile and how did you run the make command
You may want to remove your cluster name and other sensitive information.
NONE
8. Anything else do we need to know?
Could we directly upgrade cluster from current version v1.13.10 to version 1.16.1 without considering applications. Actually we need version v.1.16.1 in kops-cn Ningxia.
1. What
kopsversion are you running? The commandkops version, will display this information.$ kops version Version 1.13.0 (git-be5fb9019)2. What Kubernetes version are you running?kubectl versionwill print the version if a cluster is running or provide the Kubernetes version specified as akopsflag.kubectl version Client Version: version.Info{Major:"1", Minor:"13", GitVersion:"v1.13.10", GitCommit:"37d169313237cb4ceb2cc4bef300f2ae3053c1a2", GitTreeState:"clean", BuildDate:"2019-08-19T10:52:43Z", GoVersion:"go1.11.13", Compiler:"gc", Platform:"darwin/amd64"} Server Version: version.Info{Major:"1", Minor:"13", GitVersion:"v1.13.10", GitCommit:"37d169313237cb4ceb2cc4bef300f2ae3053c1a2", GitTreeState:"clean", BuildDate:"2019-08-19T10:44:49Z", GoVersion:"go1.11.13", Compiler:"gc", Platform:"linux/amd64"}3. What AWS region are you using(Beijing or Ningxia)?Ningxia4. What commands did you run? What is the simplest way to reproduce this issue? NONE 5. What happened after the commands executed? NONE 6. What did you expect to happen? NONE 7. Please provide the content of yourMakefileand how did you run themakecommand You may want to remove your cluster name and other sensitive information. NONE 8. Anything else do we need to know? Could we directly upgrade cluster from current version v1.13.10 to version 1.16.1 without considering applications. Actually we need version v.1.16.1 in kops-cn Ningxia.