[
https://issues.apache.org/jira/browse/IGNITE-17780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeremy McMillan updated IGNITE-17780:
-------------------------------------
Description:
StatefulSet has been supported since IGNITE-6241. Experience supporting Ignite
in the field has led best practice recommendations to stop recommending the use
of Kubernetes Deployment objects because of the benefits, in practice, which
persistent volumes bring to common operations like restarting pods.
Persistent topology and node identity makes re-joining a cluster much cheaper
than always creating new Ignite nodes as pods are started.
This should be simple for the cloud provider specific examples: just change the
"Creating a Pod Configuration" sections to provide a valid StatefulSet example.
*
[https://ignite.apache.org/docs/2.11.1/installation/kubernetes/amazon-eks-deployment#creating-pod-configuration]
*
[https://ignite.apache.org/docs/2.11.1/installation/kubernetes/azure-deployment#creating-pod-configuration]
*
[https://ignite.apache.org/docs/2.11.1/installation/kubernetes/gke-deployment#creating-pod-configuration]
*
was:
StatefulSet has been supported since IGNITE-6241. Experience supporting Ignite
in the field has led best practice recommendations to stop recommending the use
of Kubernetes Deployment objects because of the benefits, in practice, which
persistent volumes bring to common operations like restarting pods.
Persistent topology and node identity makes re-joining a cluster much cheaper
than always creating new Ignite nodes as pods are started.
> Update Kubernetes Deployment examples to StatefulSet
> ----------------------------------------------------
>
> Key: IGNITE-17780
> URL: https://issues.apache.org/jira/browse/IGNITE-17780
> Project: Ignite
> Issue Type: Bug
> Components: documentation
> Reporter: Jeremy McMillan
> Priority: Minor
>
> StatefulSet has been supported since IGNITE-6241. Experience supporting
> Ignite in the field has led best practice recommendations to stop
> recommending the use of Kubernetes Deployment objects because of the
> benefits, in practice, which persistent volumes bring to common operations
> like restarting pods.
> Persistent topology and node identity makes re-joining a cluster much cheaper
> than always creating new Ignite nodes as pods are started.
> This should be simple for the cloud provider specific examples: just change
> the "Creating a Pod Configuration" sections to provide a valid StatefulSet
> example.
> *
> [https://ignite.apache.org/docs/2.11.1/installation/kubernetes/amazon-eks-deployment#creating-pod-configuration]
> *
> [https://ignite.apache.org/docs/2.11.1/installation/kubernetes/azure-deployment#creating-pod-configuration]
> *
> [https://ignite.apache.org/docs/2.11.1/installation/kubernetes/gke-deployment#creating-pod-configuration]
> *
--
This message was sent by Atlassian Jira
(v8.20.10#820010)