[GitHub] [cloudstack-kubernetes-provider] onitake commented on issue #19: Fix License headers to files

onitake commented on issue #19: URL: https://github.com/apache/cloudstack-kubernetes-provider/issues/19#issuecomment-702593380 I'll take care of it. A few question with respect to [the policy](https://www.apache.org/legal/src-headers.html): - Should I add a license header to Make

[GitHub] [cloudstack-kubernetes-provider] onitake commented on issue #16: [DISCUSS] Work on next release

onitake commented on issue #16: URL: https://github.com/apache/cloudstack-kubernetes-provider/issues/16#issuecomment-702596507 @rhtyd I think we are ready to cut a release when CI is set up and the outstanding issues are fixed (i.e. #19 , #18 , #17 ) The version we're running in pro

[GitHub] [cloudstack-kubernetes-provider] onitake opened a new issue #20: Update the Kubernetes frameworks

onitake opened a new issue #20: URL: https://github.com/apache/cloudstack-kubernetes-provider/issues/20 We're currently building against a very old Kubernetes framework version: 1.15.2 The project is already at 1.19, with 1.20 in alpha. Update all frameworks to the latest stable v

[GitHub] [cloudstack-kubernetes-provider] onitake commented on issue #16: [DISCUSS] Work on next release

onitake commented on issue #16: URL: https://github.com/apache/cloudstack-kubernetes-provider/issues/16#issuecomment-702603951 Going through all the issues, there is another thing we might want to consider, but I'm not sure if it should be done for 1.0: We're building against an old

[GitHub] [cloudstack-www] DaanHoogland merged pull request #77: Update security page

DaanHoogland merged pull request #77: URL: https://github.com/apache/cloudstack-www/pull/77 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 t

[GitHub] [cloudstack-www] DaanHoogland commented on pull request #77: Update security page

DaanHoogland commented on pull request #77: URL: https://github.com/apache/cloudstack-www/pull/77#issuecomment-702613653 @svenvogel (cc @PaulAngus ) is a publication action in order now? This is an automated message from the

RE: Dev Environment

Hi Gregor, thanks for your answer. You're right, solved my problem too. :) Thanks for your help Regards Dirk Dirk Klahre Cloud Stack Developer - Cloud Management Platform GMS Cloud Infrastructure Services We Transform. Trust into Value itelligence Global Managed Services GmbH ▪ Breitscheids

[GitHub] [cloudstack-kubernetes-provider] onitake opened a new pull request #21: Add missing license headers

onitake opened a new pull request #21: URL: https://github.com/apache/cloudstack-kubernetes-provider/pull/21 Fixes: #19 This is an automated message from the Apache Git Service. To respond to the message, please log on to Gi

[GitHub] [cloudstack-primate] DaanHoogland opened a new issue #785: [BUG] boot into setup dissapeared

DaanHoogland opened a new issue #785: URL: https://github.com/apache/cloudstack-primate/issues/785 **Describe the bug** A boot into setup check is expected in the instance action start and reboot as are shown in the vm wizard: https://user-images.githubusercontent.com/2486961/9493

[GitHub] [cloudstack-primate] DaanHoogland commented on issue #785: [BUG] boot into setup dissapeared

DaanHoogland commented on issue #785: URL: https://github.com/apache/cloudstack-primate/issues/785#issuecomment-702746207 @davidjumani @shwstppr looks like a regression since the initial merge. I noticed during taking screenshots for an intro doc. do you have a quick assesment? cc @rhtyd

[GitHub] [cloudstack-cloudmonkey] soreana opened a new pull request #70: Added new option to change default cmk config file.

soreana opened a new pull request #70: URL: https://github.com/apache/cloudstack-cloudmonkey/pull/70 Cloudmonkey command lets us use a different config file rather than the default one. This pull request added the same functionality to the `cmk` command. ``` cmk -c ./my-config