Skip to content
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

Add hubble-ui as an option for cilium when installing hubble #13025

Closed
allen-mun opened this issue Dec 23, 2021 · 6 comments
Closed

Add hubble-ui as an option for cilium when installing hubble #13025

allen-mun opened this issue Dec 23, 2021 · 6 comments
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@allen-mun
Copy link

/kind feature

1. Describe IN DETAIL the feature/behavior/change you would like to see.
With hubble-ui v0.8.0+, it seems like hubble-ui now supports TLS (from this PR, release link: here. It looks like the reason for not installing hubble-ui was for a fix in the v0.7.7 hubble-ui image (from this).

For us, hubble-ui would provide an easier and more visible solution than using hubble-cli to debug network issues.
2. Feel free to provide a design supporting your feature request.

@k8s-ci-robot k8s-ci-robot added the kind/feature Categorizes issue or PR as related to a new feature. label Dec 23, 2021
@olemarkus
Copy link
Member

The reason we don't support hubble-ui is because webapps are a bit tricky. They don't belong in kube-system, they tend to be exposed outside of the cluster and thus has a different security profile. They require external TLS, DNS, and they perhaps should use an Ingress. They perhaps need an authenticating/authorizing proxy.

Luckily it is now easy to install the hubble ui alone using the cilium helm chart.

@allen-mun
Copy link
Author

Alright, without adding hubble-ui to kops, is it possible to change hubble-relay to toggle TLS since hubble-ui now supports it?

Line referenced here:

@olemarkus
Copy link
Member

Yes. kOps 1.24 will probably switch this one to enable TLS.

@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue or PR as fresh with /remove-lifecycle stale
  • Mark this issue or PR as rotten with /lifecycle rotten
  • Close this issue or PR with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Mar 27, 2022
@olemarkus
Copy link
Member

I think it is quite safe to say we won't support this as an addon.
We have also added docs on how to install hubble on kops. See https://kops.sigs.k8s.io/networking/cilium/#hubble-ui

/close

@k8s-ci-robot
Copy link
Contributor

@olemarkus: Closing this issue.

In response to this:

I think it is quite safe to say we won't support this as an addon.
We have also added docs on how to install hubble on kops. See https://kops.sigs.k8s.io/networking/cilium/#hubble-ui

/close

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
Development

No branches or pull requests

4 participants