-
Notifications
You must be signed in to change notification settings - Fork 6.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix ciliums hubble relay configuration #9876
Fix ciliums hubble relay configuration #9876
Conversation
|
Welcome @prashantchitta! |
Hi @prashantchitta. Thanks for your PR. I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
02ed5e3
to
4c32d50
Compare
/easycla |
/check-cla |
4c32d50
to
8cf7260
Compare
Thanks for fixing the issue! /ok-to-test |
tls-client-cert-file: /var/lib/hubble-relay/tls/client.crt | ||
tls-client-key-file: /var/lib/hubble-relay/tls/client.key | ||
tls-hubble-server-ca-files: /var/lib/hubble-relay/tls/hubble-server-ca.crt | ||
disable-server-tls: {% if cilium_hubble_tls_generate %}false{% else %}true{% endif %} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why do you remove TLS feature?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It is generated by CronJob, right?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I created the PR to fix that
#9880
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@prashantchitta Could you take a look at #9880 of @utam0k ?
If that is good, we can keep a swtich of disable-server-tls
based on the pull request.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: oomichi, prashantchitta, utam0k The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
apiVersion: v1 | ||
kind: ConfigMap | ||
metadata: | ||
name: hubble-relay-config | ||
namespace: kube-system | ||
data: | ||
config.yaml: | | ||
peer-service: unix:///var/run/cilium/hubble.sock | ||
peer-service: "hubble-peer.kube-system.svc.cluster.local:443" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
peer-service: "hubble-peer.kube-system.svc.cluster.local:443" | |
peer-service: "hubble-peer.kube-system.svc.{{ dns_domain }}:443" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@MrFreezeex addressed the comment
Thanks @prashantchitta :D /lgtm |
* Fix ciliums hubble relay configuration * Fixed the tls from code review * Updated to dna_domain instead of hardcoding
This fixes the ContainerCreating status that appears because hubble relay has changed upstream. These changes are based on upstream cilium helm.
Hubble relay now uses k8s service to discover peers rather than unix socket. A new k8s service for peers and metrics are introduced
What type of PR is this?
What this PR does / why we need it:
Which issue(s) this PR fixes:
Fixes #
#9870 and #9613 (comment)
Special notes for your reviewer:
Does this PR introduce a user-facing change?: