This is an automated email from the ASF dual-hosted git repository.

jiwq pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/submarine.git


The following commit(s) were added to refs/heads/master by this push:
     new a6e9fea  SUBMARINE-529. Change apiVersion
a6e9fea is described below

commit a6e9fea1d11095c2970d2cf71150db19c6f5b8aa
Author: wang0630 <[email protected]>
AuthorDate: Fri Jun 19 00:57:07 2020 +0800

    SUBMARINE-529. Change apiVersion
    
    ### What is this PR for?
    k8s installed by kind 0.8.0 seems that it does not support apiVersion 
apps/v1beta1 anymore.
    
    Change to apps/v1 to build successfully.
    
    ### What type of PR is it?
    [Improvement]
    
    ### Todos
    * [ ] - Task
    
    ### What is the Jira issue?
    https://issues.apache.org/jira/browse/SUBMARINE-529
    
    ### How should this be tested?
    https://travis-ci.com/github/wang0630/submarine/builds/172083779
    
    ### Screenshots (if appropriate)
    
    ### Questions:
    * Does the licenses files need update? No
    * Is there breaking changes for older versions? No
    * Does this needs documentation? No
    
    Author: wang0630 <[email protected]>
    
    Closes #317 from wang0630/master and squashes the following commits:
    
    658ffa7 [wang0630] Change apiVersion
---
 helm-charts/submarine/templates/submarine-database.yaml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/helm-charts/submarine/templates/submarine-database.yaml 
b/helm-charts/submarine/templates/submarine-database.yaml
index b7b5d27..02803a8 100644
--- a/helm-charts/submarine/templates/submarine-database.yaml
+++ b/helm-charts/submarine/templates/submarine-database.yaml
@@ -15,7 +15,7 @@
 # limitations under the License.
 #
 
-apiVersion: apps/v1beta1
+apiVersion: apps/v1
 kind: Deployment
 metadata:
   name: "{{ .Values.submarine.database.name }}"


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to