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
1. What kops version are you running? The command kops version, will display
this information.
Version 1.20.0 (git-8ea83c6d233a15dacfcc769d4d82bea3f530cf72)
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.
v1.19.9
3. What cloud provider are you using?
AWS
4. What commands did you run? What is the simplest way to reproduce this issue?
Use cilium networking
Enable hubble
$ yq -y .spec.networking.cilium.hubble cluster.yaml
enabled: true
metrics:
- dns
Try to update the cluster:
$ kops --state=s3://mybucket/testcluster.k8s.local replace -f cluster.yaml
$ kops --state=s3://mybucket/testcluster.k8s.local update cluster testcluster.k8s.local
I0420 17:34:15.024753 216616 apply_cluster.go:479] Gossip DNS: skipping DNS validation
error building tasks: error reading manifest addons/networking.cilium.io/k8s-1.12-v1.9.yaml: error opening resource: error executing resource template "addons/networking.cilium.io/k8s-1.12-v1.9.yaml": error executing template "addons/networking.cilium.io/k8s-1.12-v1.9.yaml": template: addons/networking.cilium.io/k8s-1.12-v1.9.yaml:931:62: executing "addons/networking.cilium.io/k8s-1.12-v1.9.yaml" at <.Networking.Cilium.Version>: can't evaluate field Networking in type *kops.CiliumNetworkingSpec
5. What happened after the commands executed?
The template cannot be rendered
6. What did you expect to happen?
The cluster will update properly
As a workaround I disabled Hubble
The text was updated successfully, but these errors were encountered:
javipolo
added a commit
to javipolo/kops
that referenced
this issue
Apr 20, 2021
1. What
kops
version are you running? The commandkops version
, will displaythis information.
Version 1.20.0 (git-8ea83c6d233a15dacfcc769d4d82bea3f530cf72)
2. What Kubernetes version are you running?
kubectl version
will print theversion if a cluster is running or provide the Kubernetes version specified as
a
kops
flag.v1.19.9
3. What cloud provider are you using?
AWS
4. What commands did you run? What is the simplest way to reproduce this issue?
Use cilium networking
Enable hubble
Try to update the cluster:
5. What happened after the commands executed?
The template cannot be rendered
6. What did you expect to happen?
The cluster will update properly
As a workaround I disabled Hubble
The text was updated successfully, but these errors were encountered: