Closed chobostar closed 2 years ago
Name | Link |
---|---|
Latest commit | 794c35dbc0df342d94c06c4fe09788c2975ea5a0 |
Latest deploy log | https://app.netlify.com/sites/pedantic-goldberg-f76ec1/deploys/62f3b71f21bd8f00084ca5df |
Deploy Preview | https://deploy-preview-41--pedantic-goldberg-f76ec1.netlify.app |
Preview on mobile | Toggle QR Code...Use your smartphone camera to open QR code link. |
To edit notification comments on pull requests, go to your Netlify site settings.
Looks good. For the API reference changes, I believe the content is autogenerated. So we need to update the source as well.
@chobostar Could you check @JakeSCahill's comment and resolve conflicts?
@hasancelik yes, I have just checked again
Yaml files are included into adoc as is: https://github.com/hazelcast/hazelcast-platform-operator-docs/pull/7/files#diff-76bc1e26c86f00d6cc19714cd56c2364d216a8c049aee1a6380bcb52dde1f7c7R43
Files were added manually by hand. I don't see any automation there. Thus fix the yaml file means fix the rendered doc.
Here are fixed examples: https://deploy-preview-41--pedantic-goldberg-f76ec1.netlify.app/operator/latest-snapshot/scheduling-configuration.html#pod-affinity-and-pod-anti-affinity
As far as I see everything as expected.
corev1.DoNotSchedule
became DoNotSchedule
. Does this affect the API reference here? https://deploy-preview-41--pedantic-goldberg-f76ec1.netlify.app/operator/latest-snapshot/api-ref.html#schedulingconfiguration
corev1.DoNotSchedule
becameDoNotSchedule
. Does this affect the API reference here? https://deploy-preview-41--pedantic-goldberg-f76ec1.netlify.app/operator/latest-snapshot/api-ref.html#schedulingconfiguration
Thanks for clarifying!
That was just typo in example yaml.
Nothing changed in API, so we don't need to change API ref.
Here is CRD part connected with the PR: https://github.com/hazelcast/hazelcast-platform-operator/blob/main/bundle.yaml#L937-L1033 as I see the schema exactly the same as fixed version of our example yaml.
WhenUnsatisfiable indicates how to deal with a pod if it doesn't satisfy the spread constraint. - DoNotSchedule (default)
also everything is consistent
Looks good š
@chobostar Could you check @JakeSCahill's comment and resolve conflicts?
@hasancelik we are done here and ready to be merged.
@chobostar Thanks a lot š
fixed wrong indent in pod-antiffity
fixed topology spread to as docs: https://kubernetes.io/docs/concepts/workloads/pods/pod-topology-spread-constraints/
DoNotSchedule (default) tells the scheduler not to schedule it.
ScheduleAnyway tells the scheduler to still schedule it while prioritizing nodes that minimize the skew.