Skip to content

separate deployment #614

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

Open
wants to merge 4 commits into
base: main
Choose a base branch
from

Conversation

hank95179
Copy link
Contributor

@hank95179 hank95179 commented Apr 26, 2025

This PR defines the state_validation spec function for a Deployment object.
Rules include the following fields. The fields selector, template, and replicas are omitted below since they are identical to - - ReplicaSet and Statefulset

  • minReadySeconds (int32): Optional. Should be >= 0

  • progressDeadlineSeconds: Optional , If exists should be greater than minReadySeconds

  • Strategy (StatefulSetUpdateStrategy): Optional

    • Strategy.type (string): Optional. Should be either "RollingUpdate" or "Recreate"

    • Strategy.rollingUpdate (RollingUpdateStatefulSetStrategy): Optional. Should only be present when type is "RollingUpdate"

    • Strategy.rollingUpdate.maxUnavailable (IntOrString): Optional. Assumes unmarshalled to a number for now, must be >= 0

    • Strategy.rollingUpdate.maxSurge (IntOrString): Optional. Assumes unmarshalled to a number for now, must be >= 0

    • maxSurge and maxUnvailable should not both be zero.

  • revisionHistoryLimit (int32): Optional. can be < 0

@hank95179
Copy link
Contributor Author

Init deployment spec for validation

@hank95179
Copy link
Contributor Author

Init deployment spec for validation

  1. strategy
  2. progressDeadlineSeconds

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

Successfully merging this pull request may close these issues.

1 participant