githubEdit

Provider Attributes and Pricing Adjustments

Attribute Adjustments

  • Conduct the steps in this section on the Kubernetes control plane from which the provider was configured in prior steps

  • Adjust the following key-values pairs as necessary within the provider-storage.yaml file created below:

    • Update the values of the capabilities/storage/2/class key to the correct class type (I.e. beta2). Reference the Storage Class Types doc section for additional details.

    • Update the region value from current us-west to an appropriate value such as us-east OR eu-west

  • Ensure that necessary environment variables are in place prior to issuing

Caveat on Attributes Updates in Active Leases

  • If your provider has active leases, attributes that were used during the creation of those leases cannot be updated

  • Example - if a lease was created and is active on your provider with key=region and value=us-east- it would not be possible to update the region attribute without closing those active leases prior

Helm Chart Update

cd ~

helm repo update

Capture and Edit provider.yaml File

  • In this section we will capture the current provider settings and add necessary persistent storage elements

  • NOTE - the bidpricestoragescale setting in the provider.yaml file will be ignored if the bid pricing scriptarrow-up-right is used.

Capture Current Provider Settings and Write to File

Update provider.yaml File With Persistent Storage Settings

  • Open the provider.yaml file with your favorite editor (I.e. vi or vim) and add the following

And add this attribute if you are not using the bid pricing script:

Finalized provider.yaml File

  • Post additions discussed above, your provider.yaml file should look something like this:

Upgrade the Helm Install

Expected/Example Output

Verify Provider Settings

  • Issue the following command to verify values applied by Helm

Example/Expected Output

Provider Status

  • Note - the Helm upgrade will spawn a new provider pod

  • Possible the prior provider pod may show with a status of deleting on initial view and then would eventually disappear from output

Expected/Example Output

Last updated