Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How DaemonSet portworx-api works? #403

Open
andy812 opened this issue Jul 19, 2022 · 0 comments
Open

How DaemonSet portworx-api works? #403

andy812 opened this issue Jul 19, 2022 · 0 comments

Comments

@andy812
Copy link

andy812 commented Jul 19, 2022

https://github.com/portworx/helm/blob/master/charts/portworx/templates/portworx-ds.yaml

apiVersion: apps/v1
kind: DaemonSet
metadata:
  name: portworx-api
  namespace: kube-system
  labels:
    name: portworx-api
spec:
  selector:
    matchLabels:
      name: portworx-api
  minReadySeconds: 0
  updateStrategy:
    type: RollingUpdate
    rollingUpdate:
      maxUnavailable: 100%
  template:
    metadata:
      labels:
        name: portworx-api
    spec:
      affinity:
        nodeAffinity:
          requiredDuringSchedulingIgnoredDuringExecution:
            nodeSelectorTerms:
              - matchExpressions:
                  - key: px/enabled
                    operator: {{ template "px.affinityPxEnabledOperator" . }}
                    values:
                      -  {{ template "px.affinityPxEnabledValue" . }}
                  - key: node-role.kubernetes.io/master
                    operator: DoesNotExist
      hostNetwork: true
      hostPID: false
      containers:
        - name: portworx-api
          image: "{{ template "px.getPauseImage" . }}/pause:3.1"
          imagePullPolicy: {{ $pullPolicy }}
          readinessProbe:
            periodSeconds: 10
            httpGet:
              host: 127.0.0.1
              path: /status
              port: 9001
      restartPolicy: Always
      serviceAccountName: px-account

I don't understand how it works. As i see there is the only one pause container what do nothing. It doesn't listen port 9001, so readinessProbe always fail.
Could you explain how it should work?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant