Git-Mirrors/constellation
1
0
Fork 0
mirror of https://github.com/edgelesssys/constellation.git synced 2025-01-02 11:26:25 -05:00
Code Issues Packages Projects Releases Wiki Activity
66faa5493f
constellation/dev-docs/workflows/marketplace-images.md
Moritz Sanft e691e26bd3
cli: support for GCP marketplace images (#2792) 
* cli: support GCP marketplace images

* ci: support GCP marketplace images

* docs: support GCP marketplace images

* bazel: generate

* ci: allow GCP for mpi e2e test

* Update docs/docs/overview/license.md

Co-authored-by: Thomas Tendyck <51411342+thomasten@users.noreply.github.com>

* terraform-provider: allow GCP MPIs

* terraform-provider: fix error message

---------

Co-authored-by: Thomas Tendyck <51411342+thomasten@users.noreply.github.com>
2024-01-08 15:51:39 +01:00

1.4 KiB
Raw Blame History

Using Marketplace Images in Constellation

This document explains the steps a user needs to take to run Constellation with dynamic billing via the cloud marketplaces.

AWS

Marketplace Images on AWS are not available yet.

Azure

On Azure, to use a marketplace image, ensure that the subscription has accepted the agreement to use marketplace images:

az vm image terms accept --publisher edgelesssystems --offer constellation --plan constellation

Then, set the VMs to use the marketplace image in the constellation-conf.yaml file:

yq eval -i ".provider.azure.useMarketplaceImage = true" constellation-conf.yaml

And ensure that the cluster uses a release image (i.e. .image=vX.Y.Z in the constellation-conf.yaml file). Afterwards, proceed with the cluster creation as usual.

GCP

On GCP, to use a marketplace image, ensure that the account is entitled to use marketplace images by Edgeless Systems by accepting the terms through the web portal.

Then, set the VMs to use the marketplace image in the constellation-conf.yaml file:

yq eval -i ".provider.gcp.useMarketplaceImage = true" constellation-conf.yaml

And ensure that the cluster uses a release image (i.e. .image=vX.Y.Z in the constellation-conf.yaml file). Afterwards, proceed with the cluster creation as usual.