Consul Enterprise

    Find the license file that you received in your welcome email. It should have a extension. You will use the contents of this file to create a Kubernetes secret before installing the Helm chart.

    You can use the following commands to create the secret with name consul-ent-license and key key:

    Note: If you cannot find your .hclic file, please contact your sales team or Technical Account Manager.

    In your config.yaml, change the value of global.image to one of the enterprise release tags.

    1. global:
    2.   image: 'hashicorp/consul-enterprise:1.10.0-ent'

    config.yaml

    2. server:
    3.   enterpriseLicense:
    4.     secretName: 'consul-ent-license'

    Consul Enterprise - 图2

    config.yaml

    If the version of Consul is < 1.10, use the following config with the name and key of the secret you just created.

    Note: The value of server.enterpriseLicense.enableLicenseAutoload must be set to false.

    config.yaml

    Once the cluster is up, you can verify the nodes are running Consul Enterprise by using the consul license get command.

    First, forward your local port 8500 to the Consul servers so you can run consul commands locally against the Consul servers in Kubernetes:

    1. $ kubectl port-forward service/hashicorp-consul-server 8500:8500

    In a separate tab, run the consul license get command (if using ACLs see below):

    If you get an error:

    1. Error getting license: invalid character 'r' looking for beginning of value

    Then you have likely enabled ACLs. You need to specify your ACL token when running the license get command. First, assign the ACL token to the CONSUL_HTTP_TOKEN environment variable:

      Now the token will be used when running Consul commands: