@@cloudtechmasters9985 I have Prometheus operator installed in k8s I have a external application outside of k8s that neither have any pods nor service inside the k8s which is running on ec2 instances (all ec2 instances is end user based I mean they can spin them anytime.So every time endpoint ip changes ) I am able to monitor them by mentioning endpoint ip but these IPs are dynamic.It is creating so much manual work there. Is there any way we can do automation for those endpoint IP? Like auto discovery
@@sawan1720 Create a DNS name and use the name every where instead of hard coded ips or for ec2 use elastic ip so that ips wont change everytime u stop and start
![Kubernetes Crash Course for Absolute Beginners [NEW]](http://i.ytimg.com/vi/s_o8dwzRlu4/mqdefault.jpg)
cool explanation
sahi hai bidu
I like your explanation but one query I have .Can we target external instances outside of k8s with match labels.
Hi Sawan,
Can you pls give an example which ur looking for?
especially external instances?
@@cloudtechmasters9985
I have Prometheus operator installed in k8s
I have a external application outside of k8s that neither have any pods nor service inside the k8s which is running on ec2 instances (all ec2 instances is end user based I mean they can spin them anytime.So every time endpoint ip changes )
I am able to monitor them by mentioning endpoint ip but these IPs are dynamic.It is creating so much manual work there.
Is there any way we can do automation for those endpoint IP? Like auto discovery
@@sawan1720 Create a DNS name and use the name every where instead of hard coded ips or for ec2 use elastic ip so that ips wont change everytime u stop and start