Question: Hi! what happen if I point the ingress to an headless service?

Asked By
Asked At
2018-05-04 18:58:53

Found 15 possible answers.

User Answered At Possible Answer
omarjatoi 2018-05-04 19:13:11 you’d want some form of service discovery in front of the headless service and then point the ingress to that service discovery point
dan.wendorf 2018-05-04 20:02:17 Is it possible to use kops to set annotations on nodes? I’m interested in applying so spot instances (which can get terminated at any time) aren’t attached to a load balancer. Adding an annotation to an InstanceGroup’s metadata.annotations key does nothing.
slupers 2018-05-04 20:26:12 Hi! When creating a cluster with kops, is there any way to override aspects of kube-system pods or point to custom manifests for certain components? Let's say I wanted specify a memory limit for kube-controller-manager when creating a cluster, what would be the best way to do that?
dagviggo 2018-05-04 20:38:46 .. info for both setting k8s labels and AWS tags both hm.. that doesn't cover annotations though so if it has to be an annotation i'm not sure
faheem 2018-05-05 12:30:39 Usually all the configurable parameters for k8s components supported by kops are available in go docs. See something like KubeControllerManagerConfig in
lukeab 2018-05-05 14:20:10 Hey folks, i've spun up a new private topology cluster, internal elb is getting tcp(443) healthcheck fails on the master for the api, I dont know why Slight mis-step, I didn't add a bastion to the network, is there a neat way to add one so i can ssh in and debug the api endpoint?
chrislovecnm 2018-05-05 15:49:43 @lukeab did you masters start? How about etcd?
lukeab 2018-05-05 15:51:33 i'm re-building it again on the same vpc/domain, to see if it jutst works this time. anyway, added --bastion=true this time, and explicitly setting --dns-zone to see what happsn. I'm wondering if there is a dns resolver issue.
chrislovecnm 2018-05-05 16:24:11 @lukeab bastion has zero to deal with the masters not starting properly. Dns could be an issue
lukeab 2018-05-05 17:31:20 wasn't suggesting they were related, just didn't have bastionto ssh in to master so i could actually debug why the api elb healthcheck failed. --utility-subnets=subnet-xxxxxxx
  --subnets=subnet-xxxxxxxx \
  --node-count=3 \
  --node-size=m5.2xlarge \
  --master-size=m5.large \
  --master-zones=eu-west-1a \
  --zones=eu-west-1a \
  --networking=calico \
  --network-cidr=w.x.y.z/21 \
  --vpc=vpc-xxxxxxxx \
  --ssh-public-key=/home/luke/.ssh/ \
  --topology=private \
  --cloud=aws \  \  \
so here's my full kops create cluster command
kops create cluster \ but ss -nlput on the master, shows no port 443 listening? so i created a fresh cluster, private topology, internal elb, bastion and seems the elb pointing to the bastionworks fine, i can ssh to the bastion and then the master ok, i can't get a working instanice. hmm, turns out my vpc already has that. ok, so i just found out about this enableDnsHostnames requirement dont know why. now since i updated my settings (bash script around kops create cluster ...options..) i'm getting auth failure on the s3 bucket :disappointed:
adam_p 2018-05-05 21:35:16 What os are you using for your masters?
lukeab 2018-05-05 21:35:45 default for kops
adam_p 2018-05-05 21:35:59 m5s wont work with the default debian
lukeab 2018-05-05 21:36:05 ahhhhhh is there documentation on instance type support? well gosh darn and rats! i guess i just tear down and start again back on m4? Or hmm, maybe c5?
adam_p 2018-05-05 21:36:52 c5 has the same problem

Related Questions