It is a bit strange issue. I tried to reproduce it on my local mikube cluster but without any effects… So, during calling istioctl upgrade command, istioctl tries to compose GitHub release URL which is invalid. It is missing amd64 suffix. On the other hand, when I call istioctl manifest apply everything works fine.
$ istioctl --context istio-debug upgrade -f pawel-debug-istiooperator.yaml -f profiles/pawel-default.yaml --dry-run
2020-05-26T10:28:48.053041Z info proto: tag has too few fields: "-"
Control Plane - pilot pod - istiod-6fdfdb74cb-9kjgj - version: 1.6.0
Control Plane - pilot pod - istiod-6fdfdb74cb-cfrq8 - version: 1.6.0
Control Plane - pilot pod - istiod-6fdfdb74cb-wwm69 - version: 1.6.0
2020-05-26T10:28:56.049618Z warn found 4 CRD of unsupported v1alpha1 security policy: [clusterrbacconfigs.rbac.istio.io rbacconfigs.rbac.istio.io servicerolebindings.rbac.istio.io serviceroles.rbac.istio.io]. The v1alpha1 security policy is no longer supported starting 1.6. It's strongly recommended to delete the CRD of the v1alpha1 security policy to avoid applying any of the v1alpha1 security policy in the unsupported version
Upgrade version check passed: 1.6.0 -> 1.6.0.
2020-05-26T10:28:56.669814Z info Error: failed to generate Istio configs from file [pawel-debug-istiooperator.yaml profiles/pawel-default.yaml] for the current version: 1.6.0, error: failed to fetch URL https://github.com/istio/istio/releases/download/1.6.0/istio-1.6.0-linux.tar.gz : 404 Not Found
Error: failed to generate Istio configs from file [pawel-debug-istiooperator.yaml profiles/pawel-default.yaml] for the current version: 1.6.0, error: failed to fetch URL https://github.com/istio/istio/releases/download/1.6.0/istio-1.6.0-linux.tar.gz : 404 Not Found
Output from istioctl upgrade
$ istioctl --context istio-debug upgrade --dry-run
2020-05-26T10:45:00.680190Z info proto: tag has too few fields: "-"
Control Plane - pilot pod - istiod-6fdfdb74cb-9kjgj - version: 1.6.0
Control Plane - pilot pod - istiod-6fdfdb74cb-cfrq8 - version: 1.6.0
Control Plane - pilot pod - istiod-6fdfdb74cb-wwm69 - version: 1.6.0
2020-05-26T10:45:16.137258Z warn found 4 CRD of unsupported v1alpha1 security policy: [clusterrbacconfigs.rbac.istio.io rbacconfigs.rbac.istio.io servicerolebindings.rbac.istio.io serviceroles.rbac.istio.io]. The v1alpha1 security policy is no longer supported starting 1.6. It's strongly recommended to delete the CRD of the v1alpha1 security policy to avoid applying any of the v1alpha1 security policy in the unsupported version
Upgrade version check passed: 1.6.0 -> 1.6.0.
2020-05-26T10:45:16.968546Z info Error: failed to generate Istio configs from file [] for the current version: 1.6.0, error: failed to fetch URL https://github.com/istio/istio/releases/download/1.6.0/istio-1.6.0-linux.tar.gz : 404 Not Found
Error: failed to generate Istio configs from file [] for the current version: 1.6.0, error: failed to fetch URL https://github.com/istio/istio/releases/download/1.6.0/istio-1.6.0-linux.tar.gz : 404 Not Found
Could you tell me where can I set the URL in the IstioOperator manifest?
@Shubham thanks for pointing this. I removed those 4 CRDS, but still have the same problem with wrong URL to the istio release:
$ istioctl --context istio-debug upgrade -f pawel-debug-istiooperator.yaml -f profiles/pawel-default.yaml --dry-run
2020-05-27T09:28:41.813791Z info proto: tag has too few fields: "-"
Control Plane - pilot pod - istiod-6fdfdb74cb-9kjgj - version: 1.6.0
Control Plane - pilot pod - istiod-6fdfdb74cb-cfrq8 - version: 1.6.0
Control Plane - pilot pod - istiod-6fdfdb74cb-wwm69 - version: 1.6.0
Upgrade version check passed: 1.6.0 -> 1.6.0.
2020-05-27T09:28:45.671646Z info Error: failed to generate Istio configs from file [pawel-debug-istiooperator.yaml profiles/pawel-default.yaml] for the current version: 1.6.0, error: failed to fetch URL https://github.com/istio/istio/releases/download/1.6.0/istio-1.6.0-linux.tar.gz : 404 Not Found
Error: failed to generate Istio configs from file [pawel-debug-istiooperator.yaml profiles/pawel-default.yaml] for the current version: 1.6.0, error: failed to fetch URL https://github.com/istio/istio/releases/download/1.6.0/istio-1.6.0-linux.tar.gz : 404 Not Found
Yes. For example, I want to introduce changes in the control plane (for example enable Grafana). In this case should I use istioctl upgrade or istioctl manifest apply?
When I use --force flag the output is the same. Here is how to reproduce it on the minikube cluster
$ minikube start --kubernetes-version=1.14.7 --cpus=5 --memory=5500mb
😄 minikube v1.8.1 on Darwin 10.14.6
✨ Automatically selected the hyperkit driver. Other choices: docker, virtualbox
💿 Downloading VM boot image ...
🔥 Creating hyperkit VM (CPUs=5, Memory=5500MB, Disk=20000MB) ...
🐳 Preparing Kubernetes v1.14.7 on Docker 19.03.6 ...
🚀 Launching Kubernetes ...
🌟 Enabling addons: default-storageclass, storage-provisioner
⌛ Waiting for cluster to come online ...
🏄 Done! kubectl is now configured to use "minikube"
$ istioctl --context minikube install --set profile=default
Detected that your cluster does not support third party JWT authentication. Falling back to less secure first party JWT. See https://istio.io/docs/ops/best-practices/security/#configure-third-party-service-account-tokens for details.
✔ Istio core installed
✔ Istiod installed
✔ Addons installed
✔ Ingress gateways installed
✔ Installation complete
$ istioctl --context minikube upgrade --force --dry-run
2020-05-27T10:44:20.620944Z info proto: tag has too few fields: "-"
Control Plane - ingressgateway pod - istio-ingressgateway-64b6f7f96d-6lwqk - version: 1.6.0
Control Plane - pilot pod - istiod-694d645947-c8z9p - version: 1.6.0
2020-05-27T10:44:20.780122Z warn found 4 CRD of unsupported v1alpha1 security policy: [clusterrbacconfigs.rbac.istio.io rbacconfigs.rbac.istio.io servicerolebindings.rbac.istio.io serviceroles.rbac.istio.io]. The v1alpha1 security policy is no longer supported starting 1.6. It's strongly recommended to delete the CRD of the v1alpha1 security policy to avoid applying any of the v1alpha1 security policy in the unsupported version
Upgrade version check passed: 1.6.0 -> 1.6.0.
2020-05-27T10:44:21.144259Z info Error: failed to generate Istio configs from file [] for the current version: 1.6.0, error: failed to fetch URL https://github.com/istio/istio/releases/download/1.6.0/istio-1.6.0-linux.tar.gz : 404 Not Found
Error: failed to generate Istio configs from file [] for the current version: 1.6.0, error: failed to fetch URL https://github.com/istio/istio/releases/download/1.6.0/istio-1.6.0-linux.tar.gz : 404 Not Found
oh you install default version and you want to enable other components like grafana as you mention above.
then you would create overlays file like this for grafana
@Shubham, yes. It works with istioctl manifest apply but does not work with istioctl upgrade. So, I want to know what is the reason. And should I set somehow a link to the GitHub release?