You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@flink.apache.org by GitBox <gi...@apache.org> on 2022/03/25 10:23:43 UTC

[GitHub] [flink-kubernetes-operator] bgeng777 opened a new pull request #111: [FLINK-26825] Document State Machine Graph for JM Deployment

bgeng777 opened a new pull request #111:
URL: https://github.com/apache/flink-kubernetes-operator/pull/111


   - Add State Machine Graph for JM Deployment and document the meaning of each possible transition.
   - The graph is attached here:
   ![JM_deployment_state_machine](https://user-images.githubusercontent.com/80749729/160102961-aac56574-a7d8-41ef-b1a3-8a044e885efa.svg)
   
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@flink.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



[GitHub] [flink-kubernetes-operator] mbalassi commented on a change in pull request #111: [FLINK-26825] Document State Machine Graph for JM Deployment

Posted by GitBox <gi...@apache.org>.
mbalassi commented on a change in pull request #111:
URL: https://github.com/apache/flink-kubernetes-operator/pull/111#discussion_r835231724



##########
File path: docs/content/docs/concepts/architecture.md
##########
@@ -45,6 +45,25 @@ The CR can be (re)applied on the cluster any time. The Operator makes continuous
 
 The Operator is built with the [Java Operator SDK](https://github.com/java-operator-sdk/java-operator-sdk) and uses the [Native Kubernetes Integration](https://nightlies.apache.org/flink/flink-docs-master/docs/deployment/resource-providers/native_kubernetes/) for launching Flink deployments and submitting jobs under the hood. The Java Operator SDK is a higher level framework and related tooling to support writing Kubernetes Operators in Java. Both the Java Operator SDK and Flink's native kubernetes integration itself is using the [Fabric8 Kubernetes Client](https://github.com/fabric8io/kubernetes-client) to interact with the Kubernetes API Server.
 
+## State Machine of JobManager Deployment
+The Operator will manage the lifecycle of JobManager Deployment. Its state machine is as follows:

Review comment:
       nit: The Operator _manages_ the lifecycle of _the_ JobManager Deployment

##########
File path: docs/content/docs/concepts/architecture.md
##########
@@ -45,6 +45,25 @@ The CR can be (re)applied on the cluster any time. The Operator makes continuous
 
 The Operator is built with the [Java Operator SDK](https://github.com/java-operator-sdk/java-operator-sdk) and uses the [Native Kubernetes Integration](https://nightlies.apache.org/flink/flink-docs-master/docs/deployment/resource-providers/native_kubernetes/) for launching Flink deployments and submitting jobs under the hood. The Java Operator SDK is a higher level framework and related tooling to support writing Kubernetes Operators in Java. Both the Java Operator SDK and Flink's native kubernetes integration itself is using the [Fabric8 Kubernetes Client](https://github.com/fabric8io/kubernetes-client) to interact with the Kubernetes API Server.
 
+## State Machine of JobManager Deployment
+The Operator will manage the lifecycle of JobManager Deployment. Its state machine is as follows:
+
+{{< img src="/img/concepts/JM_deployment_state_machine.svg" alt="State Machine of JobManager Deployment" >}}
+
+The possible transitions usually indicate that there are some underlying changes:
+
+1. `MISSING` -> `DEPLOYING`: A new JM deployment exists and is being created
+2. `DEPLOYING` -> `DEPLOYED_NOT_READY`: The JM deployment exists and pass checks of the availability of replicas and JM port connectivity. Now, it is waiting the REST service to be ready

Review comment:
       nit: ... and _passes the JM availability and connectivity checks_ 




-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@flink.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



[GitHub] [flink-kubernetes-operator] gyfora merged pull request #111: [FLINK-26825] Document State Machine Graph for JM Deployment

Posted by GitBox <gi...@apache.org>.
gyfora merged pull request #111:
URL: https://github.com/apache/flink-kubernetes-operator/pull/111


   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@flink.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org