Skip to content

Flatcar Linux Azure billing / licensing confusion #703

Description

@dghubble

Raising some concerns about the Flatcar Linux Azure Marketplace image.

On Azure, CoreOS Container Linux has always been offered as a free image. It has no license accept step and no additional cost.

The Flatcar Linux offering is listed as BYOL ("bring your own license") and does not list additional charges (but also doesn't say free). The BYOL link doesn't go anywhere and Flatcar's Azure docs don't provide details about license acceptance or charges / pricing.

License

The slightly different Flatcar Linux offering requires users accept Kinvolks terms to use the Marketplace image.

$ terraform apply
Error message: 'Legal terms have not been accepted for this item on this subscription

Remedied by the following (suggested in Typhoon docs).

az vm image terms show --publish kinvolk --offer flatcar-container-linux --plan stable
az vm image terms accept --publish kinvolk --offer flatcar-container-linux --plan stable

My best attempts at investigating show you can use the az CLI to get a JSON blob that links to a personalized license that just contains a link to https://kinvolk.io/legal/open-source/.

Cost

Accepting the Marketplace terms enables a subscription (its shown deeply burried in the Azure Marketplace console if you click on juuust the right things) which may have costs associated with it. Since trialing of Flatcar Linux Azure began, a new separate Azure Marketplace invoice line item (separate from Azure Service) has appeared.

Azure's own detailed invoice is broken and the generic invoice PDF provides no details about even the name of the subscription, so its been difficult to confirm whether this is indeed coming from Flatcar Linux Azure. Its possible its something else.

Screenshot from 2020-04-11 21-13-58

Actions

There are several problems with this situation:

  • Is Flatcar Linux Azure Marketplace image cost free or not? This should be clear.
  • What really is the Flatcar Linux BYOL policy? Is this step needed vs CoreOS?
  • Azure's Dashboard's UX is becoming more of a liability

I've reached out to Kinvolk directly to gather some details.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions