The kubernetes-master charm is a layered and reactive charm, so it needs to be built with
charm build. The rest of the Charm Writing docs will be helpful, as well.
One nice aspect of the charms being layered is that, if you want to build a customized version of kubernetes-master based on the upstream charm, instead of creating a fork of the charm and having to keep that in sync, you can create a charm layer which includes kubernetes-master as a base layer and can then extend or override it with only the pieces that need to be different. You would do this by checking out a copy of the kubernetes-master charm into your
$CHARM_LAYERS_PATH directory (as
kubernetes-master) and then having your
layer.yaml file look like this:
At a minimum, you would want to override the charm name in your
metadata.yaml, so that you don’t conflict with the upstream charm: