从部署配置中配置pod的重新启动策略

Question

kind: DeploymentConfig
metadata:
  generation: 19
  name: my-deployment-config
  namespace: my-deployment-config-namespace
  selfLink: >-
    ...
  uid: af918183-c780-11ea-8945-525400d3e4d9
spec:
  replicas: 1
  revisionHistoryLimit: 10
  selector:
    name: my-selector
  strategy:
    activeDeadlineSeconds: 21600
    resources: {}
    rollingParams:
      intervalSeconds: 1
      maxSurge: 25%
      maxUnavailable: 25%
      timeoutSeconds: 600
      updatePeriodSeconds: 1
    type: Rolling
template:
    metadata:
      ...
    spec:
      containers:
        - image: >-
            (image source)
          imagePullPolicy: Always
          name: my-container
          ports:
            - containerPort: 8080
              protocol: TCP
          resources: {}
          terminationMessagePath: /dev/termination-log
          terminationMessagePolicy: File
      restartPolicy: Always
      schedulerName: default-scheduler
      securityContext: {}
      terminationGracePeriodSeconds: 30

Kubernetes文档以及关于重新启动策略的Openshift文档显示，可以使用Always、Never或OnFailure配置POD。

那么我如何从部署配置中做到这一点呢？

Answer 1

部署仅允许始终使用RestartPolicy。请参阅本文档https://kubernetes.io/docs/concepts/workloads/controllers/deployment/#pod-template

也请参考有关此问题的长期报告。https://github.com/kubernetes/kubernetes/issues/24725

只允许使用等于Always的.spec.template.spec.RestartPolicy，如果未指定，则为默认值。