当 ReplicaSet=2 时在 Kubernetes 上发现+请求一个 Kafka Streams 实例

Discover+Request a Kafka Streams Instance on Kubernetes when ReplicaSet=2

如何向同一 Kubernetes 服务上的同一 Kafka Streams 应用程序实例的另一个实例发送 RPC 请求。

注意:当使用 application.server 属性

公开当前实例 ip:port 时,这以前在 Docker 上有效

例如ReplicaSet=2

StreamApp 实例 1 端点 = 1.2.3.4:7079

StreamApp 实例 2 端点 = 1.2.3.5:7079

我想从实例 1 发送休息请求以访问实例 2 上的远程交互式查询

我已经试过了

我从实例 1 -> 实例 2 发送了一个 CURL 请求:但收到 404 错误

curl -X GET "http://1.2.3.5:7079/user/1" -H "accept: application/json"

但是如果我从 K8 主机 -> 实例 2 发送 CURL 请求:我得到 200 ok

curl -X GET "http://1.2.3.5:7079/user/1" -H "accept: application/json"



 #values.yml
replicaCount: 1

 image:
  repository: "docker.hosted/steam-app"
  tag: "0.1.0"
  pullPolicy: Always
  pullSecret: "a_secret"

service:
 name: http
 type: NodePort
 externalPort: 7079
 internalPort: 7079

kafka:
 host: "kafka.default"
 port: "9092"

ingress:
 enabled: false

deployment.yml

apiVersion: extensions/v1beta1
kind: Deployment
metadata:
  name: {{ template "stream-app.fullname" . }}
  labels:
    app: {{ template "stream-app.name" . }}
    chart: {{ .Chart.Name }}-{{ .Chart.Version | replace "+" "_" }}
    release: {{ .Release.Name }}
    heritage: {{ .Release.Service }}
spec:
  replicas: {{ .Values.replicaCount }}
  template:
    metadata:
      labels:
        app: {{ template "stream-app.name" . }}
        release: {{ .Release.Name }}
    spec:
      containers:
        - name: {{ .Chart.Name }}
          image: "{{ .Values.image.repository }}:{{ .Values.image.tag }}"
          imagePullPolicy: {{ .Values.image.pullPolicy }}
          env:
            - name: KAFKA_HOST
              value: "{{ tpl .Values.kafka.host . }}"
            - name: KAFKA_PORT
              value: "{{ .Values.kafka.port }}"
            - name: MY_POD_IP
              valueFrom:
               fieldRef:
                fieldPath: status.podIP
            - name: MY_POD_PORT
              value: "{{ .Values.service.internalPort }}"
          ports:
            - containerPort: {{ .Values.service.internalPort }}
          livenessProbe:
            httpGet:
              path: /actuator/alive
              port: {{ .Values.service.internalPort }}
            initialDelaySeconds: 60
            periodSeconds: 10
            timeoutSeconds: 1
            successThreshold: 1
            failureThreshold: 3
          readinessProbe:
            httpGet:
              path: /actuator/ready
              port: {{ .Values.service.internalPort }}
          initialDelaySeconds: 60
          periodSeconds: 10
          timeoutSeconds: 1
          successThreshold: 1
          failureThreshold: 3
          resources:
{{ toYaml .Values.resources | indent 12 }}
    {{- if .Values.nodeSelector }}
      nodeSelector:
{{ toYaml .Values.nodeSelector | indent 8 }}
    {{- end }}
      imagePullSecrets:
        - name: {{ .Values.image.pullSecret }

service.yml

kind: Service
metadata:
  name: {{ template "stream-app.fullname" . }}
  labels:
    app: {{ template "stream-app.name" . }}
    chart: {{ .Chart.Name }}-{{ .Chart.Version | replace "+" "_" }}
    release: {{ .Release.Name }}
    heritage: {{ .Release.Service }}
spec:
  type: {{ .Values.service.type }}
  ports:
    - port: {{ .Values.service.externalPort }}
      targetPort: {{ .Values.service.internalPort }}
      protocol: TCP
      name: {{ .Values.service.name }}
  selector:
    app: {{ template "stream-app.name" . }}
    release: {{ .Release.Name }}

我在安装服务之前禁用了 Istio 注入,然后在安装服务后重新启用它,现在一切正常,所以对我有用的命令是: