search

gravitational / gravity

Kubernetes application deployments for restricted, regulated, or remote environments
Apache License 2.0
1.08k stars 109 forks source link

--values and --set options are absent for install? #1011

Closed RAbraham closed 4 years ago

RAbraham commented 4 years ago

Hi, Environment:

The documentation mentions that I can use --values and --set during the install process

unpacked-image$ ./gravity install --values=custom-values.yaml --set=nginx.image=1.9.1 --set=postgres.registry=internal.registry.io

But it gives me an error to use it.

sudo ./gravity install --advertise-addr=10.128.0.5 --token=abcd --cloud-provider=generic --config=/home/rabraham/tmp/fr/fr-config.yaml --values=/home/rabraham/tmp/fr/custom-values.yaml
[ERROR]: unknown long flag '--values'

Look in the help for install, I don't see those options? Is there any other way to pass this info?

root@on-prem-host:~/fifteenrock# ./gravity install --help
usage: gravity install [<flags>] [<path>]

Install cluster image on this node.

Flags:
      --help                   Show context-sensitive help (also try --help-long and --help-man).
      --debug                  Enable debug mode.
  -q, --quiet                  Suppress any extra output to stdout.
      --insecure               Skip TLS verification.
      --state-dir=STATE-DIR    Gravity local state directory.
      --log-file="/var/log/gravity-install.log"
                               Path to the log file with diagnostic information.
      --advertise-addr=ADVERTISE-ADDR
                               IP address this node will advertise to other cluster nodes. Must be present on the node. Will be auto-selected if not specified.
      --token=TOKEN            Unique install token to authorize other nodes to join the cluster. Generated automatically if unspecified.
      --cloud-provider=CLOUD-PROVIDER
                               Cloud provider integration: [generic aws gce]. Auto-detected if not set.
      --cluster=CLUSTER        Cluster name. Will be auto-generated if not specified.
      --flavor=FLAVOR          Cluster image flavor to install.
      --role=ROLE              Role of this node.
      --config=CONFIG          Kubernetes configuration resources, will be injected at cluster creation time.
      --wizard                 Start installation using web wizard interface.
      --mount=MOUNT            One or several mount overrides in the following format: <mount-name>:<path>, e.g. data:/var/lib/data.
      --pod-network-cidr="10.244.0.0/16"
                               Subnet range for Kubernetes pods network. Must be a minimum of /16.
      --service-cidr="10.100.0.0/16"
                               Subnet range for Kubernetes service networ.
      --vxlan-port=8472        Custom overlay network port.
      --dns-listen-addr=127.0.0.2 ...
                               Custom listen address for in-cluster DNS.
      --dns-port=53            Custom listen port for in-cluster DNS.
      --storage-driver=STORAGE-DRIVER
                               Docker storage driver. Overrides the one specified in the cluster image manifest. Recognized are: devicemapper, overlay, overlay2.
      --docker-opt=DOCKER-OPT ...
                               Additional arguments to Docker. Can be specified multiple times.
      --service-uid="1000"     Service user ID for Planet container. "planet" user will created and used if none specified.
      --service-gid="1000"     Service group ID for Planet container. "planet" group will created and used if none specified.
      --gce-node-tag=GCE-NODE-TAG ...
                               Override node tag on the instance in GCE required for load balanacing. Defaults to the cluster name.
      --dns-zone=DNS-ZONE ...  Specify an upstream server for the given zone within the cluster. Accepts <zone>/<nameserver> format where <nameserver> can be either <ip> or
                               <ip>:<port>. Can be specified multiple times.
      --remote                 Do not use this node in the cluster.

Args:
  [<path>]  Path to the directory with the unpacked cluster image. Defaults to the current directory.
r0mant commented 4 years ago

Hi @RAbraham, yeah, this feature will be a part of the upcoming 7.0 release, sorry about the confusion. I'll add a note to the docs.

In 6.x versions what you could do is use the --config parameter to pass arbitrary Kubernetes resources which will be created in the cluster. So you could create, say, a ConfigMap with your custom values, pass it via --config parameter and have your install hook mount the ConfigMap and consume values from it.

Let me know if you have any questions.