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.
Client version: 1.30.2 (git-v1.30.2)
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.
Client Version: v1.30.7
Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3
Server Version: v1.30.7
3. What cloud provider are you using?
AWS
4. What commands did you run? What is the simplest way to reproduce this issue?
Upgraded from kOps 1.30.1 to 1.30.2 or simply create a new kOps cluster with kOps 1.30.2.
5. What happened after the commands executed?
Cilium hubble broke.
6. What did you expect to happen?
Cilium hubble show be working.
7. Please provide your cluster manifest. Execute kops get --name my.example.com -o yaml to display your cluster manifest.
You may want to remove your cluster name and other sensitive information.
8. Please run the commands with most verbose logging by adding the -v 10 flag.
Paste the logs into this report, or in a gist and provide the gist link here.
hubble-relay time="2024-11-29T11:14:28Z" level=warning msg="Failed to create peer client for peers synchronization; will try again after the timeout has expired" error="context deadline exceeded" subsys=hubble-relay target="hubble-peer.kube-system.svc.cluster.local:443"
cilium status
/¯¯\
/¯¯\__/¯¯\ Cilium: 10 warnings
\__/¯¯\__/ Operator: OK
/¯¯\__/¯¯\ Envoy DaemonSet: disabled (using embedded mode)
\__/¯¯\__/ Hubble Relay: OK
\__/ ClusterMesh: disabled
DaemonSet cilium Desired: 10, Ready: 10/10, Available: 10/10
Deployment cilium-operator Desired: 2, Ready: 2/2, Available: 2/2
Deployment hubble-relay Desired: 2, Ready: 2/2, Available: 2/2
Deployment hubble-ui Desired: 1, Ready: 1/1, Available: 1/1
Containers: cilium Running: 10
cilium-operator Running: 2
hubble-relay Running: 2
hubble-ui Running: 1
Cluster Pods: 83/83 managed by Cilium
Helm chart version:
Image versions cilium quay.io/cilium/cilium:v1.15.6@sha256:6aa840986a3a9722cd967ef63248d675a87add7e1704740902d5d3162f0c0def: 10
cilium-operator quay.io/cilium/operator:v1.15.6@sha256:f3ebc5eac9c0b37aabdf120e120a704ccd77d8c34191adec120e9ee021b8a875: 2
hubble-relay quay.io/cilium/hubble-relay:v1.15.6@sha256:a0863dd70d081b273b87b9b7ce7e2d3f99171c2f5e202cd57bc6691e51283e0c: 2
hubble-ui quay.io/cilium/hubble-ui-backend:v0.13.0@sha256:1e7657d997c5a48253bb8dc91ecee75b63018d16ff5e5797e5af367336bc8803: 1
hubble-ui quay.io/cilium/hubble-ui:v0.13.0@sha256:7d663dc16538dd6e29061abd1047013a645e6e69c115e008bee9ea9fef9a6666: 1
Warnings: cilium cilium-5ttd6 Hubble: Server not initialized
cilium cilium-5vqz6 Hubble: Server not initialized
cilium cilium-6pgkc Hubble: Server not initialized
cilium cilium-jq96t Hubble: Server not initialized
cilium cilium-jrrcb Hubble: Server not initialized
cilium cilium-lnp7s Hubble: Server not initialized
cilium cilium-lzvb4 Hubble: Server not initialized
cilium cilium-ps7mq Hubble: Server not initialized
cilium cilium-q6tt9 Hubble: Server not initialized
cilium cilium-xq8h7 Hubble: Server not initialized
9. Anything else do we need to know?
After downgrading to kOps 1.30.1 cilium hubble works again.
/kind bug
1. What
kops
version are you running? The commandkops version
, will displaythis information.
Client version: 1.30.2 (git-v1.30.2)
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.3. What cloud provider are you using?
AWS
4. What commands did you run? What is the simplest way to reproduce this issue?
Upgraded from kOps 1.30.1 to 1.30.2 or simply create a new kOps cluster with kOps 1.30.2.
5. What happened after the commands executed?
Cilium hubble broke.
6. What did you expect to happen?
Cilium hubble show be working.
7. Please provide your cluster manifest. Execute
kops get --name my.example.com -o yaml
to display your cluster manifest.You may want to remove your cluster name and other sensitive information.
8. Please run the commands with most verbose logging by adding the
-v 10
flag.Paste the logs into this report, or in a gist and provide the gist link here.
9. Anything else do we need to know?
After downgrading to kOps 1.30.1 cilium hubble works again.
The text was updated successfully, but these errors were encountered: