kops icon indicating copy to clipboard operation
kops copied to clipboard

Published 20 hours ago • verified publisher icon kubernetes

dnscontroller needs better docs

Open chrislovecnm opened this issue 8 years ago • 7 comments
trafficstars

We need to document if this is correct:

  • route53-kubernetes creates a CNAME for Service of type=LoadBalancer to point to the auto-generated hostname of the ELB.
  • dns-controller creates multiple A records, one for each node on which the given Service has a Pod running, which is useful for a Service of type=NodePort.

chrislovecnm avatar Dec 21 '16 19:12 chrislovecnm

I found myself struggling for some time to understand (and still do not fully):

  • how k8s knows that type=LoadBalancer means AWS ELB, and what to do, how it is configured
  • how I can get a useful name (eventually figured out it means "ExternalIP", which really is just the generated hostname)
  • what the best path is - or at least my options are - for exposing ports
  • how I would set up a classic AWS VPC private/public structure with nodes controlled by k8s. E.g. I might want all k8s worker nodes in private subnet, but the ELB should be in the public. It is not at all clear how k8s does all of this (and how kops plays into it)

I know, I know... we need to remain focused. But the "coming from the outside in" use of k8s and much around it left me hanging in a lot of places.

More than happy to help here however possible.

deitch avatar Dec 21 '16 19:12 deitch

@deitch

how k8s knows that type=LoadBalancer means AWS ELB, and what to do, how it is configured

From the AWS cloud provider

yissachar avatar Dec 21 '16 20:12 yissachar

Yep but go find in the docs what it is, how it works or interacts with your AWS account, what the options are and how to configure it.

deitch avatar Dec 21 '16 21:12 deitch

Linking https://github.com/kubernetes/kops/issues/972 which dupes this.

yissachar avatar Dec 21 '16 22:12 yissachar

Hey all. I opened an issue to document how to diagnosis problem such as these, please comment on #3888

chrislovecnm avatar Nov 17 '17 22:11 chrislovecnm

Issues go stale after 90d of inactivity. Mark the issue as fresh with /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta. /lifecycle stale

fejta-bot avatar Feb 15 '18 22:02 fejta-bot

/lifecycle frozen /remove-lifecycle stale

chrislovecnm avatar Feb 16 '18 01:02 chrislovecnm

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-triage-robot avatar Oct 31 '22 18:10 k8s-triage-robot

The Kubernetes project currently lacks enough active 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 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 rotten

k8s-triage-robot avatar Nov 30 '22 19:11 k8s-triage-robot

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

This bot triages 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:

  • Reopen this issue with /reopen
  • Mark this issue as fresh with /remove-lifecycle rotten
  • Offer to help out with Issue Triage

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

/close not-planned

k8s-triage-robot avatar Dec 30 '22 20:12 k8s-triage-robot

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to this:

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

This bot triages 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:

  • Reopen this issue with /reopen
  • Mark this issue as fresh with /remove-lifecycle rotten
  • Offer to help out with Issue Triage

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

/close not-planned

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.

k8s-ci-robot avatar Dec 30 '22 20:12 k8s-ci-robot