Kyma-CLI as part of the Kyma family

[a-thaler]

Motivation

With Kyma-CLI developers will have a convenient way to manage a Kyma installation, supporting multiple operating system in a tested and maintainable way.
In order to leverage all the advantages of the existing CLI we need to integrate it to the official Kyma project.

Goal

Integrate Kyma-CLI to the kyma-project organization and integrate it to the release process

Details

In order to use it as the default tool for installation (#3005), it should be an official tool for kyma. Otherwise users will be irritated.

So it needs to be moved from a technical perspective, it needs to be integrated into the community process and it needs to be integrated to the release process.

Action Items

• Implement last pieces in CLI which are provided by local installation scripts
  • Specify custom admin password (Support custom admin password for installation cli#36)
  • Support of custom installer CR (Support of configuration overrides cli#40)
  • Support of knative mode (Support for knative flag on kyma installation cli#38)
  • Support for minikube restart (Continue with the installation even if I choose No for deleteing previous minikube cli#47)
  • Support of latest minikube version (Support for minikube 1.0.x cli#76)
  • review of CLI command structure and options incl. help text (CLI inline help documentation review cli#39)
  • security issues (Make request for root rights more explicit cli#71, Apply proper shell output encoding cli#69, Suppress kyma password log in specific cases cli#68)
  • quality issues (Code quality for release cli#80)
• make it part of the family
  • move git repo to kyma-project organization (Move Kyma-CLI to kyma-project/cli #4044)
  • have all opens source/community requirements fullfilled, see template (Move Kyma-CLI to kyma-project/cli #4044)
  • have release requirements fullfilles (threat modelling, license scan, security scan) (Release requirements for CLI #4046)
  • have automated release process in place (Release process for CLI #4045)
  • Have it integrated to the kyma release process from an organization perspective (Release process for CLI #4045)
  • Have it installable via official homebrew tap (Add homebrew support to Kyma-CLI #4037)