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 fully qualified domain name inside Service Resource Information section #8707

Open
StevenWooding opened this issue Feb 20, 2024 · 1 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.

Comments

@StevenWooding
Copy link

What would you like to be added?

When clicking on a specific service and it displays all the information of the service. There is a section called "Resource Information" that prints out the Cluster IP, Type etc etc.

It would be nice to also have the fully qualified domain name (FQDN) there for the local cluster. So the 'xxx.yyy.svc.cluster.local' domain.

Why is this needed?

With our setup of Kubernetes we often have to connect across namespaces. And then working out what the FQDN is for the cross namespace connection can take time and introduce typo's. So simply having the FQDN printed out that can be copied and pasted would save a lot of time and make installations less error prone.

@StevenWooding StevenWooding added the kind/feature Categorizes issue or PR as related to a new feature. label Feb 20, 2024
@k8s-triage-robot
Copy link

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

This bot triages un-triaged issues 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 as fresh with /remove-lifecycle stale
  • Close this issue 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 May 20, 2024
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

3 participants