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
A hubble-metrics service is created and the cilium pods expose the hubble-metrics port. Unfortunately, the port of the service and the port of the pod are not the same. The service uses the port9965 (which is the port cilium uses). The pod uses the port9091 (which cilium used a long time ago, now they use port 9965). Since the service is a headless services it must use the same port as the port exposed by the pod. For more explanation see this: kubernetes/kubernetes#20488 (comment)
1. What kops version are you running? The command kops version, will display
this information.
kops version
Client version: 1.30.3 (git-v1.30.3
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: v1.30.8
3. What cloud provider are you using?
AWS
4. What commands did you run? What is the simplest way to reproduce this issue?
5. What happened after the commands executed?
6. What did you expect to happen?
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.
n/a
9. Anything else do we need to know?
I'm happy to provide a PR to fix it. Just let me know.
The text was updated successfully, but these errors were encountered:
/kind bug
When setting up hubble-metrics via cluster.yaml:
A
hubble-metrics
service is created and the cilium pods expose thehubble-metrics
port. Unfortunately, the port of the service and the port of the pod are not the same. The service uses the port9965
(which is the port cilium uses). The pod uses the port9091
(which cilium used a long time ago, now they use port9965
). Since the service is a headless services it must use the same port as the port exposed by the pod. For more explanation see this: kubernetes/kubernetes#20488 (comment)1. What
kops
version are you running? The commandkops version
, will displaythis information.
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?
5. What happened after the commands executed?
6. What did you expect to happen?
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.
n/a
9. Anything else do we need to know?
I'm happy to provide a PR to fix it. Just let me know.
The text was updated successfully, but these errors were encountered: