zch93 opened a new pull request, #524:
URL: https://github.com/apache/flink-kubernetes-operator/pull/524

   ## What is the purpose of the change
   
   *I had to remove the JsonIgnore annotation above the ResourceLifecycleState 
getter in CommonStatus and also I had to expose this as a printer column 
instead of the reconciliation status that is used currently.*
   
   
   ## Brief change log
   
     - *Remove the `@JsonIgnore` annotation above the `ResourceLifecycleState` 
getter*
     - *Added a new private field to `CommonStatus` with `@PrinterColumn` 
annotation*
     - *Remove the `@PrinterColumn` annotation above the `state` field within 
the `ReconciliationStatus` class*
   
   ## Verifying this change
   
   1. Checkout this PR
   2. And go through the quick-start guide
   3. Finally use the `kubectl get flinkdeployments` command to check the 
results
   
   *(OR)*
   
   1. (After you checked out this PR) Build the flink-kubernetes-operator with 
`mvn clean install -Pgenerate-docs -DskipTests` command
   2. Upgrade the `flinkdeployments` and `flinksessionjobs` CRDs
   4. Build a new docker image
   5. Load that image into minikube
   6. Install the operator locally
   7. Submit the basic-example Flink job
   8. Finally use the `kubectl get flinkdeployments` command to check the 
results
   
   You should see something like this as result:
   <img width="319" alt="image" 
src="https://user-images.githubusercontent.com/73717102/216645617-9c92b058-54c2-4c0b-8148-440d9ca8f5fe.png";>
   
   ## Does this pull request potentially affect one of the following parts:
   
     - Dependencies (does it add or upgrade a dependency): no
     - The public API, i.e., is any changes to the `CustomResourceDescriptors`: 
no
     - Core observer or reconciler logic that is regularly executed: no
   
   ## Documentation
   
     - Does this pull request introduce a new feature? no
     - If yes, how is the feature documented? not applicable
   


-- 
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: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to