kyma-incubator / marketplaces Goto Github PK

Description

It was reported that the instruction for releasing Kyma on Marketplace is not up-to-date and precise - verify it, see if it can be simplified, and update the required steps.

Here are a few exemplary comments to consider:

• Point 1 does not specify if you start doing the release from your fork of the upstream master.
• In point 3 it is not clear against what you should create the pull request.
• Point 4 states Merge the PR to the release branch which is not clear.
• Point 5 states that you should checkout release-1.1 - why if you already checked it out?
• There is no information on how to change Kyma versions on the Marketplace.

In general, check f the instruction can be more clearly described so that you know what and against what you are doing and you do not have to figure it out from subsequent steps. It may be also possible to simplify the release to fewer steps - pls check that with @pPrecel and @michal-hudy .

Description

• Have a large text box where you can baste the configmap and secrets that override installation values

Reasons

Enable flexible installation of kyma with specific overrides of values.yamls of components

Attachments

Description

• prepare setup on official SAP account on Azure
• have proper scripts/tool a part of this repo and prepare release pipeline
• check out with @atakanyenel his PoC
• if possible, make release fully automated, so once Kyma is released, then automatically latest Kyma is added to Azure Marketplace
• clear docs how the whole publishing process works

Reasons

Like in case of GCP Marketplace, we also want to have easy Kyma installation for Azure users.

Description

Adjust initializer to new version of Kyma - 1.2.0

Reasons

Make Kyma 1.2.0 available at Google Cloud Marketplace

Description

Improve README.md documents in the whole repository - they were prepared for the 1.2 release in a quite limited form and size and may require improvement.
Consult @michal-hudy for input.

Description

Extend GCP Marketplace documentation with information on how to test it with manifest generated by CI.

Reasons

As we are generating manifest during the build process it would be great to mention how to use it. Also, thanks to that developer don't have to have installed envsubst

This is blocked for now by kyma-project/kyma#2942 and kyma-project/kyma#4340

Description

• Uninstallation of Kyma application should uninstall whole Kyma
• Trigger proper mode of installation operator

Reasons

At the moment uninstallation of Application only removes deployer. Kyma is installed by separate operator and marketplace deployer only installs the operator. We should not only enable installation but also enable clear installation of Kyma.

Description

Add gcloud marketplace self-signed certificate linux instruction.

Reasons

No gcloud marketplace self-signed certificate linux instruction

This is blocked for now as this is not fully supported by GC Marketplace. For now we managed to automate creation of image with deployer and licences generator

Description

• Have automation based on CI with typical approvals flows basen on Prow
• Make sure anyone can make a PR with changes that later will be reflected in marketplace

Reasons

For now publishing is possible if you have access to special GC project where there are more solutions. We do not want to give access there for to many users and we should make everything possible to modify through CIs and configuration/documentation files in repository

Description

• Have a list of components names where you can deselect a given module and install kyma without it
• Only allow to deselect modules that kyma can really run without

Reasons

Enable flexible installation of kyma with specific components only

Attachments

Description

When Kyma is deployed from GCP Marketplace it should be configurated with valid certificate instead of self-signed. Unfortunately, it is not possible to generate a valid cert for xip.io domain with Let's encrypt. We can consider a similar solution as proposed here: https://content.pivotal.io/blog/sslip-io-a-valid-ssl-certificate-for-every-ip-address

Also, it would be nice if the user will have an ability to configure his domain with a certificate.

Reasons

Have a better experience when Kyma is deployed from GCP Marketplace.

Attachments

https://content.pivotal.io/blog/sslip-io-a-valid-ssl-certificate-for-every-ip-address
https://letsencrypt.org
http://xip.io

Description

GCP Marketplace needs a deployer image that deploys the application. Unfortunately, it is not possible to test that image in Partner Portal before publication. In such case we need to create our own pipeline that will verify if the application is installed properly.

Reasons

Make the marketplace solution more resilient.