Closed zuoinlv closed 5 years ago
I fixed the issue by upgrading the dns to core-dns, not the kube-dns
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
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten
.
Rotten issues close after an additional 30d of inactivity.
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 rotten
Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen
.
Mark the issue as fresh with /remove-lifecycle rotten
.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta. /close
@fejta-bot: Closing this issue.
I would like to expose the kafka service for external access using NodePort, but service could not be accessed from the pod, logs from one of kafka pods:
Service object in kafka.yaml :
apiVersion: v1 kind: Service metadata: name: kafka labels: app: kafka spec: type: NodePort ports:
port: 9093 name: server selector: app: kafka