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
{{ message }}
This repository has been archived by the owner on Sep 8, 2022. It is now read-only.
As an immediate workaround, you can pass the --relay-version to cilium hubble enable:
$ cilium hubble enable --relay-version -service-mesh:v1.11.0-beta.1🔑 Found CA in secret cilium-ca✨ Patching ConfigMap cilium-config to enable Hubble...♻️ Restarted Cilium pods⌛ Waiting for Cilium to become ready before deploying other Hubble component(s)...🔑 Generating certificates for Relay...✨ Deploying Relay from quay.io/cilium/hubble-relay-service-mesh:v1.11.0-beta.1...⌛ Waiting for Hubble to be installed...✅ Hubble was successfully enabled!
Is there an existing issue for this?
What happened?
I ran the installation instruction for Cilium Service Mesh beta according to here and it does not attach the right image version for hubble-relay.
Specifically when I run this command:
cilium install --version -service-mesh:v1.11.0-beta.1 --config enable-envoy-config=true --kube-proxy-replacement=probe cilium hubble enable
The output indicates that it tags it incorrectly to
quay.io/cilium/hubble-relay:-service-mesh:v1.11.0-beta.1: 1
:Manually correcting it using
kubectl edit
solves the issue.Cilium Version
Kernel Version
Darwin 3c22fbbff4ba.ant.amazon.com 19.6.0 Darwin Kernel Version 19.6.0: Sun Nov 14 19:58:51 PST 2021; root:xnu-6153.141.50~1/RELEASE_X86_64 x86_64
Kubernetes Version
Sysdump
🔍 Collecting Kubernetes nodes
⚠️ Deployment "clustermesh-apiserver" not found in namespace "kube-system" - this is expected if 'clustermesh-apiserver' isn't enabled
⚠️ The following tasks failed, the sysdump may be incomplete:
⚠️ [10] Collecting Cilium egress NAT policies: failed to collect Cilium egress NAT policies: the server could not find the requested resource (get ciliumegressnatpolicies.cilium.io)
⚠️ [11] Collecting Cilium local redirect policies: failed to collect Cilium local redirect policies: the server could not find the requested resource (get ciliumlocalredirectpolicies.cilium.io)
⚠️ Please note that depending on your Cilium version and installation options, this may be expected
🔍 Collect Kubernetes nodes
🔍 Collecting Kubernetes events
🔍 Collecting Kubernetes pods
🔍 Collecting Kubernetes services
🔍 Collecting Cilium network policies
🔍 Collecting Cilium egress NAT policies
🔍 Collecting Cilium endpoints
🔍 Collecting Kubernetes network policies
🔍 Collecting Kubernetes pods summary
🔍 Collecting Cilium cluster-wide network policies
🔍 Collecting Kubernetes namespaces
🔍 Collect Kubernetes version
🔍 Collecting Cilium local redirect policies
🔍 Collecting Cilium identities
🔍 Collecting Cilium nodes
🔍 Collecting Cilium etcd secret
🔍 Collecting the Cilium configuration
🔍 Collecting the Cilium daemonset
🔍 Collecting the Hubble daemonset
🔍 Collecting the Hubble Relay configuration
🔍 Collecting the Hubble Relay deployment
🔍 Collecting the Hubble UI deployment
🔍 Collecting the Cilium operator deployment
🔍 Collecting the 'clustermesh-apiserver' deployment
🔍 Collecting gops stats from Cilium pods
🔍 Collecting gops stats from Hubble pods
🔍 Collecting 'cilium-bugtool' output from Cilium pods
🔍 Collecting gops stats from Hubble Relay pods
🔍 Collecting logs from Cilium pods
🔍 Collecting logs from Cilium operator pods
🔍 Collecting logs from 'clustermesh-apiserver' pods
🔍 Collecting logs from Hubble pods
🔍 Collecting logs from Hubble Relay pods
🔍 Collecting logs from Hubble UI pods
🔍 Collecting platform-specific data
🔍 Collecting Hubble flows from Cilium pods
🗳 Compiling sysdump
✅ The sysdump has been saved to /Users/yojeo/src/microservices-demo/cilium-sysdump-20220126-131409.zip
Relevant log output
No response
Anything else?
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: