티스토리 뷰

728x170

Aug 18 01:19:57 kubemaster journal: W0817 16:19:57.121256       8 queue.go:130] 

requeuing &ObjectMeta{Name:sync status,GenerateName:,Namespace:,SelfLink:,UID:,ResourceVersion:,Generation:0,CreationTimestamp:0001-01-01 00:00:00 +0000 UTC,DeletionTimestamp:,DeletionGracePeriodSeconds:

nil,Labels:map[string]string{},Annotations:map[string]string{},OwnerReferences:[],Finalizers:[],ClusterName:,Initializers:nil,}, err services "ingress-nginx" not found 발생 시 대응 방법

 

1) Kubernetes Pod 배포 후 서비스를 확인하기 위해 tail -f /var/log/messages를 걸어 놓은 상태로 대기 중에 다음과 같은 로그가 반복적으로 출력되는 현상

...
...
Aug 18 01:19:56 kubemaster journal: W0817 16:19:56.725598       8 queue.go:130] requeuing &ObjectMeta{Name:sync status,GenerateName:,Namespace:,SelfLink:,UID:,ResourceVersion:,Generation:0,CreationTimestamp:0001-01-01 00:00:00 +0000 UTC,DeletionTimestamp:<nil>,DeletionGracePeriodSeconds:nil,Labels:map[string]string{},Annotations:map[string]string{},OwnerReferences:[],Finalizers:[],ClusterName:,Initializers:nil,}, err services "ingress-nginx" not found
Aug 18 01:19:56 kubemaster journal: W0817 16:19:56.825879       8 queue.go:130] requeuing &ObjectMeta{Name:sync status,GenerateName:,Namespace:,SelfLink:,UID:,ResourceVersion:,Generation:0,CreationTimestamp:0001-01-01 00:00:00 +0000 UTC,DeletionTimestamp:<nil>,DeletionGracePeriodSeconds:nil,Labels:map[string]string{},Annotations:map[string]string{},OwnerReferences:[],Finalizers:[],ClusterName:,Initializers:nil,}, err services "ingress-nginx" not found
Aug 18 01:19:56 kubemaster journal: W0817 16:19:56.924098       8 queue.go:130] requeuing &ObjectMeta{Name:sync status,GenerateName:,Namespace:,SelfLink:,UID:,ResourceVersion:,Generation:0,CreationTimestamp:0001-01-01 00:00:00 +0000 UTC,DeletionTimestamp:<nil>,DeletionGracePeriodSeconds:nil,Labels:map[string]string{},Annotations:map[string]string{},OwnerReferences:[],Finalizers:[],ClusterName:,Initializers:nil,}, err services "ingress-nginx" not found
Aug 18 01:19:57 kubemaster journal: W0817 16:19:57.030574       8 queue.go:130] requeuing &ObjectMeta{Name:sync status,GenerateName:,Namespace:,SelfLink:,UID:,ResourceVersion:,Generation:0,CreationTimestamp:0001-01-01 00:00:00 +0000 UTC,DeletionTimestamp:<nil>,DeletionGracePeriodSeconds:nil,Labels:map[string]string{},Annotations:map[string]string{},OwnerReferences:[],Finalizers:[],ClusterName:,Initializers:nil,}, err services "ingress-nginx" not found
Aug 18 01:19:57 kubemaster journal: W0817 16:19:57.121256       8 queue.go:130] requeuing &ObjectMeta{Name:sync status,GenerateName:,Namespace:,SelfLink:,UID:,ResourceVersion:,Generation:0,CreationTimestamp:0001-01-01 00:00:00 +0000 UTC,DeletionTimestamp:<nil>,DeletionGracePeriodSeconds:nil,Labels:map[string]string{},Annotations:map[string]string{},OwnerReferences:[],Finalizers:[],ClusterName:,Initializers:nil,}, err services "ingress-nginx" not found
...
...

 

2) 진단

로그 메시지와 같이 ingress-nginx 서비스를 사용하는 ingress Controller에서 해당 service를 발견하지 못해 발생하는 오류

 

3) 대응

Service 명 중 ingress-nginx 서비스로 기동되는 서비스가 있는지 확인한다.

[root@kubemaster kubernetes_onestepboot]# kubectl get services --all-namespaces
NAMESPACE              NAME                        TYPE        CLUSTER-IP       EXTERNAL-IP                     PORT(S)                  AGE
default                apache-docker-service       ClusterIP   10.103.14.107    <none>                          80/TCP                   10m
default                kubernetes                  ClusterIP   10.96.0.1        <none>                          443/TCP                  11m
kube-system            kube-dns                    ClusterIP   10.96.0.10       <none>                          53/UDP,53/TCP,9153/TCP   11m
kubernetes-dashboard   dashboard-metrics-scraper   ClusterIP   10.103.160.52    <none>                          8000/TCP                 11m
kubernetes-dashboard   kubernetes-dashboard        ClusterIP   10.103.137.145   <none>                          443/TCP                  11m
[root@kubemaster kubernetes_onestepboot]#

위와 같이 ingress-nginx로 기동되어 있는 서비스가 없어 발생하는 문제로 서비스를 추가하는 yaml 파일 또는 service apply 시점의 로그를 확인한다.

본 문제의 경우 ingress service를 추가하는 yaml 파일에서 ip가 잘못 지정되어 Service를 추가하지 못해 발생한 오류로 해결하였다.

그리드형
댓글
댓글쓰기 폼