Separate Statefulset spec

[hank95179]

Hi Xudong, I am YuHan Huang here is my spec and hope to have your response does these make sense.
This PR defines the state_validation spec function for a StatefulSet object.
Rules include the following fields. The fields selector, template, and replicas are omitted below since they are identical to ReplicaSet and Deployment

You can use this

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

• serviceName (string): Optional. Can also be empty.
• updateStrategy (StatefulSetUpdateStrategy): Optional
  • updateStrategy.type (string): Optional. Should be either "RollingUpdate" or "OnDelete"
  • updateStrategy.rollingUpdate (RollingUpdateStatefulSetStrategy): Optional. Should only be present when type is "RollingUpdate"
    • updateStrategy.rollingUpdate.maxUnavailable (IntOrString): Optional. Assumes unmarshalled to a number for now, must be > 0
    • updateStrategy.rollingUpdate.partition (int32): Optional. Must be >= 0
• podManagementPolicy (string): Optional. Either "OrderedReady" or "Parallel"
• revisionHistoryLimit (int32): Optional. Somehow no restrictions
• volumeClaimTemplates ([]PersistentVolumeClaim): Optional. Assume state_validation is implemented for PersistentVolumeClaim for now.
• minReadySeconds (int32): Optional. Should be >= 0
• persistentVolumeClaimRetentionPolicy (StatefulSetPersistentVolumeClaimRetentionPolicy): Optional
  • whenDeleted, whenScaled (string): Both either "Retain" or "Delete"
• ordinals.start (int32): Optional. Should be >= 0

[fredred375]

@hank95179 I think we are still missing specs for:

DeploymentSet

• strategy (DeploymentStrategy)
• revisionHistoryLimit (int32)
• progressDeadlineSeconds (int32)

StatefulSet

• updateStrategy (StatefulSetUpdateStrategy)

[fredred375]

@agrama64 I think we should still check for rolling_update.is_Some() before using get_Some_0()

[marshtompsxd]

@hank95179 @fredred375 could you submit two PRs, one for stateful set and one for deployment set? You can keep this PR for stateful set. Also, could you change the first comment to describe what this PR does?

[marshtompsxd]

Why is the code commented out now?

[fredred375]

I commented out the new specs for both deployment and statefulset so that it doesnt mess up ci. Primarily for deployment, but also commented out statefulset just to be safe.
But yes, that probably isnt needed for statefulset and everything should still work

[hank95179]

@marshtompsxd I have create another PR for deployment and this one PR will only for statefulset.