You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@openwhisk.apache.org by GitBox <gi...@apache.org> on 2020/01/06 21:58:38 UTC

[GitHub] [openwhisk-deploy-kube] dgrove-oss opened a new issue #569: Convert to Helm3 to leverage new features

dgrove-oss opened a new issue #569: Convert to Helm3 to leverage new features
URL: https://github.com/apache/openwhisk-deploy-kube/issues/569
 
 
   In particular, we can get some useful validation of values.yaml by using the new json schema support.  I'm prototyping this on a branch (https://github.com/dgrove-oss/openwhisk-deploy-kube/tree/helm3).
   
   

----------------------------------------------------------------
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.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services

[GitHub] [openwhisk-deploy-kube] dgrove-oss commented on issue #569: Convert to Helm3 to leverage new features

Posted by GitBox <gi...@apache.org>.
dgrove-oss commented on issue #569: Convert to Helm3 to leverage new features
URL: https://github.com/apache/openwhisk-deploy-kube/issues/569#issuecomment-611270960
 
 
   Migration to Helm 3 was completed a while ago; forgot to close the issue.

----------------------------------------------------------------
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.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services

[GitHub] [openwhisk-deploy-kube] dgrove-oss commented on issue #569: Convert to Helm3 to leverage new features

Posted by GitBox <gi...@apache.org>.
dgrove-oss commented on issue #569: Convert to Helm3 to leverage new features
URL: https://github.com/apache/openwhisk-deploy-kube/issues/569#issuecomment-571578861
 
 
   Sure.   Will do that relatively soon.
   
   BTW, we merged #567 yesterday which actually switched the travisci setup to used helm 3.0.1 for our testing.  Helm v3 can deploy a Helm v2 chart.  So you could start using Helm3 today to avoid requiring tiller.

----------------------------------------------------------------
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.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services

[GitHub] [openwhisk-deploy-kube] dgrove-oss closed issue #569: Convert to Helm3 to leverage new features

Posted by GitBox <gi...@apache.org>.
dgrove-oss closed issue #569: Convert to Helm3 to leverage new features
URL: https://github.com/apache/openwhisk-deploy-kube/issues/569
 
 
   

----------------------------------------------------------------
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.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services

[GitHub] [openwhisk-deploy-kube] chetanmeh commented on issue #569: Convert to Helm3 to leverage new features

Posted by GitBox <gi...@apache.org>.
chetanmeh commented on issue #569: Convert to Helm3 to leverage new features
URL: https://github.com/apache/openwhisk-deploy-kube/issues/569#issuecomment-571525685
 
 
   This would be useful specially getting rid of Tiller which was causing issue on some setups we had having RBAC enabled.
   
   @dgrove-oss Can you create a draft pr based on your current branch. Would be helpful to understand the changes needed as you progress

----------------------------------------------------------------
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.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services