Deploy Consul on Kubernetes

Install Consul to your Kubernetes cluster with the Consul K8S CLI. Confirm the run by entering y.

$ consul-k8s install -config-file=helm/values-v1.yaml## ...    Proceed with installation? (y/N) y==> Installing Consul## ...✓ Consul installed in namespace "consul".

Notice that the Consul K8s CLI installs Consul into the consul namespace.

Refer to the Consul K8S CLI documentation to learn more about additional settings.

Add the HashiCorp Helm Chart repository.

$ helm repo add hashicorp https://helm.releases.hashicorp.com"hashicorp" has been added to your repositories

Install Consul to your Kubernetes cluster with the Helm chart. Notice that this command installs Consul into the consul namespace.

$ helm install --values helm/values-v1.yaml consul hashicorp/consul --create-namespace --namespace consul --version "1.2.0"

Install Consul to your Kubernetes cluster with the Consul K8S CLI. Confirm the run by entering y.

$ consul-k8s install -config-file=helm/values-v1.yaml## ...    Proceed with installation? (y/N) y==> Installing Consul## ...✓ Consul installed in namespace "consul".

Notice that the Consul K8s CLI installs Consul into the consul namespace.

Refer to the Consul K8S CLI documentation to learn more about additional settings.

Add the HashiCorp Helm Chart repository.

$ helm repo add hashicorp https://helm.releases.hashicorp.com"hashicorp" has been added to your repositories

Install Consul to your Kubernetes cluster with the Helm chart. Notice that this command installs Consul into the consul namespace.

$ helm install --values helm/values-v1.yaml consul hashicorp/consul --create-namespace --namespace consul --version "1.2.0"

Install Consul to your Kubernetes cluster with the Consul K8S CLI. Confirm the run by entering y.

$ consul-k8s install -config-file=helm/values-v1.yaml## ...    Proceed with installation? (y/N) y==> Installing Consul## ...✓ Consul installed in namespace "consul".

Notice that the Consul K8s CLI installs Consul into the consul namespace.

Refer to the Consul K8S CLI documentation to learn more about additional settings.

Add the HashiCorp Helm Chart repository.

$ helm repo add hashicorp https://helm.releases.hashicorp.com"hashicorp" has been added to your repositories

Install Consul to your Kubernetes cluster with the Helm chart. Notice that this command installs Consul into the consul namespace.

$ helm install --values helm/values-v1.yaml consul hashicorp/consul --create-namespace --namespace consul --version "1.2.0"

In your terminal, run the CLI command consul catalog services to return the list of services registered in Consul. Notice this returns only the consul service since it is the only running service in your Consul datacenter.

$ consul catalog servicesconsul

Agents run in either server or client mode. Server agents store all state information, including service and node IP addresses, health checks, and configuration. Client agents are lightweight processes that make up the majority of the datacenter. They report service health status to the server agents. Clients must run on every pod where services are running.

Run the CLI command consul members to return the list of Consul agents in your environment.

$ consul membersNode             Address           Status  Type    Build   Protocol  DC   Partition  Segmentconsul-server-0  10.0.4.13:8301    alive   server  1.16.0  2         dc1  default    <all>consul-server-1  10.0.6.43:8301    alive   server  1.16.0  2         dc1  default    <all>consul-server-2  10.0.5.64:8301    alive   server  1.16.0  2         dc1  default    <all>

Output the HCP Consul Dedicated URL value to your terminal and paste it in your browser to find the Consul UI. Since this environment uses a self-signed TLS certificate for its resources, click to proceed through the certificate warnings.

$ echo $CONSUL_HTTP_ADDRhttps://a55925452f7214a1cad0a0d564ae1872-646141274.us-west-2.elb.amazonaws.com

Output the token value to your terminal and copy the value to your clipboard. You will use this ACL token to authenticate in the Consul UI.

$ echo $CONSUL_HTTP_TOKENfe0dd5c3-f2e1-81e8-cde8-49d26cee5efc

On the left navigation pane, click Services to review your deployed services. At this time, you will only find the consul service.

By default, the anonymous ACL policy allows you to view the contents of Consul services, nodes, and intentions. To make changes and see more details within the Consul UI, click Log In in the top right and insert your bootstrap ACL token.

After successfully authenticating with your ACL token, you are now able to view additional Consul components and make changes in the UI. Notice you can view and manage more options under the Access Controls section on the left navigation pane.

On the left navigation pane, click on Nodes.

Agents run in either server or client mode. Server agents store all state information, including service and node IP addresses, health checks, and configuration. Client agents are lightweight processes that make up the majority of the datacenter. They report service health status to the server agents. Clients must run on every pod where services are running.

In your terminal, view the list of services registered in Consul.

$ curl -k \    --header "X-Consul-Token: $CONSUL_HTTP_TOKEN" \    $CONSUL_HTTP_ADDR/v1/catalog/services

Sample output:

{"consul":[]}

Agents run in either server or client mode. Server agents store all state information, including service and node IP addresses, health checks, and configuration. Client agents are lightweight processes that make up the majority of the datacenter. They report service health status to the server agents. Clients must run on every pod where services are running.

View the list of server and client Consul agents in your environment.

$ curl -k \    --header "X-Consul-Token: $CONSUL_HTTP_TOKEN" \    $CONSUL_HTTP_ADDR/v1/agent/members

Sample output:

[{"Name":"consul-server-0","Addr":"10.244.0.24","Port":8301,"Tags":{"acls":"1","bootstrap":"1","build":"1.16.0:c6d0f9ec","dc":"dc1","ft_fs":"1","ft_si":"1","grpc_port":"8503","id":"9da2304b-3829-4af8-7256-bc240d57d42b","port":"8300","raft_vsn":"3","role":"consul","segment":"","use_tls":"1","vsn":"2","vsn_max":"3","vsn_min":"2","wan_join_port":"8302"},"Status":1,"ProtocolMin":1,"ProtocolMax":5,"ProtocolCur":2,"DelegateMin":2,"DelegateMax":5,"DelegateCur":4}]

In your terminal, run the CLI command consul catalog services to return the list of services registered in Consul. Notice this returns only the consul service since it is the only running service in your Consul datacenter.

$ consul catalog servicesconsul

Agents run in either server or client mode. Server agents store all state information, including service and node IP addresses, health checks, and configuration. Client agents are lightweight processes that make up the majority of the datacenter. They report service health status to the server agents. Clients must run on every pod where services are running.

Run the CLI command consul members to return the list of Consul agents in your environment.

$ consul membersNode             Address           Status  Type    Build   Protocol  DC   Partition  Segmentconsul-server-0  10.0.4.13:8301    alive   server  1.16.0  2         dc1  default    <all>consul-server-1  10.0.6.43:8301    alive   server  1.16.0  2         dc1  default    <all>consul-server-2  10.0.5.64:8301    alive   server  1.16.0  2         dc1  default    <all>

Output the HCP Consul Dedicated URL value to your terminal and paste it in your browser to find the Consul UI. Since this environment uses a self-signed TLS certificate for its resources, click to proceed through the certificate warnings.

$ echo $CONSUL_HTTP_ADDRhttps://a55925452f7214a1cad0a0d564ae1872-646141274.us-west.azure.com

Output the token value to your terminal and copy the value to your clipboard. You will use this ACL token to authenticate in the Consul UI.

$ echo $CONSUL_HTTP_TOKENfe0dd5c3-f2e1-81e8-cde8-49d26cee5efc

On the left navigation pane, click Services to review your deployed services. At this time, you will only find the consul service.

By default, the anonymous ACL policy allows you to view the contents of Consul services, nodes, and intentions. To make changes and see more details within the Consul UI, click Log In in the top right and insert your bootstrap ACL token.

After successfully authenticating with your ACL token, you are now able to view additional Consul components and make changes in the UI. Notice you can view and manage more options under the Access Controls section on the left navigation pane.

On the left navigation pane, click on Nodes.

Agents run in either server or client mode. Server agents store all state information, including service and node IP addresses, health checks, and configuration. Client agents are lightweight processes that make up the majority of the datacenter. They report service health status to the server agents. Clients must run on every pod where services are running.

In your terminal, view the list of services registered in Consul.

$ curl -k \    --header "X-Consul-Token: $CONSUL_HTTP_TOKEN" \    $CONSUL_HTTP_ADDR/v1/catalog/services

Sample output:

{"consul":[]}

Agents run in either server or client mode. Server agents store all state information, including service and node IP addresses, health checks, and configuration. Client agents are lightweight processes that make up the majority of the datacenter. They report service health status to the server agents. Clients must run on every pod where services are running.

View the list of server and client Consul agents in your environment.

$ curl -k \    --header "X-Consul-Token: $CONSUL_HTTP_TOKEN" \    $CONSUL_HTTP_ADDR/v1/agent/members

Sample output:

[{"Name":"consul-server-0","Addr":"10.244.0.24","Port":8301,"Tags":{"acls":"1","bootstrap":"1","build":"1.16.0:c6d0f9ec","dc":"dc1","ft_fs":"1","ft_si":"1","grpc_port":"8503","id":"9da2304b-3829-4af8-7256-bc240d57d42b","port":"8300","raft_vsn":"3","role":"consul","segment":"","use_tls":"1","vsn":"2","vsn_max":"3","vsn_min":"2","wan_join_port":"8302"},"Status":1,"ProtocolMin":1,"ProtocolMax":5,"ProtocolCur":2,"DelegateMin":2,"DelegateMax":5,"DelegateCur":4}]

Open a separate terminal window and expose the Consul server with kubectl port-forward using the consul-ui service name as the target.

$ kubectl port-forward svc/consul-ui --namespace consul 8501:443

In your original terminal, run the CLI command consul catalog services to return the list of services registered in Consul. Notice this returns only the consul service since it is the only running service in your Consul datacenter.

$ consul catalog servicesconsul

Agents run in either server or client mode. Server agents store all state information, including service and node IP addresses, health checks, and configuration. Client agents are lightweight processes that make up the majority of the datacenter. They report service health status to the server agents. Clients must run on every pod where services are running.

Run the CLI command consul members to return the list of Consul agents in your environment.

$ consul membersNode             Address           Status  Type    Build   Protocol  DC   Partition  Segmentconsul-server-0  10.0.4.13:8301    alive   server  1.16.0  2         dc1  default    <all>

Output the token value to your terminal and copy the value to your clipboard. You will use this ACL token to authenticate in the Consul UI.

$ echo $CONSUL_HTTP_TOKENfe0dd5c3-f2e1-81e8-cde8-49d26cee5efc

Open a separate terminal window and expose the Consul UI with kubectl port-forward using the consul-ui service name as the target.

$ kubectl port-forward svc/consul-ui --namespace consul 8501:443

Open https://localhost:8501 in your browser to find the Consul UI. Since this environment uses a self-signed TLS certificate for its resources, click to proceed through the certificate warnings.

On the left navigation pane, click Services to review your deployed services. At this time, you will only find the consul service.

By default, the anonymous ACL policy allows you to view the contents of Consul services, nodes, and intentions. To make changes and see more details within the Consul UI, click Log In in the top right and insert your bootstrap ACL token.

After successfully authenticating with your ACL token, you are now able to view additional Consul components and make changes in the UI. Notice you can view and manage more options under the Access Controls section on the left navigation pane.

On the left navigation pane, click on Nodes.

Agents run in either server or client mode. Server agents store all state information, including service and node IP addresses, health checks, and configuration. Client agents are lightweight processes that make up the majority of the datacenter. They report service health status to the server agents. Clients must run on every pod where services are running.

Open a separate terminal window and expose the Consul server with kubectl port-forward using the consul-ui service name as the target.

$ kubectl port-forward svc/consul-ui --namespace consul 8501:443

In your original terminal, view the list of services registered in Consul.

$ curl -k \    --header "X-Consul-Token: $CONSUL_HTTP_TOKEN" \    $CONSUL_HTTP_ADDR/v1/catalog/services

Sample output:

{"consul":[]}

Agents run in either server or client mode. Server agents store all state information, including service and node IP addresses, health checks, and configuration. Client agents are lightweight processes that make up the majority of the datacenter. They report service health status to the server agents. Clients must run on every pod where services are running.

View the list of server and client Consul agents in your environment.

$ curl -k \    --header "X-Consul-Token: $CONSUL_HTTP_TOKEN" \    $CONSUL_HTTP_ADDR/v1/agent/members

Sample output:

[{"Name":"consul-server-0","Addr":"10.244.0.24","Port":8301,"Tags":{"acls":"1","bootstrap":"1","build":"1.16.0:c6d0f9ec","dc":"dc1","ft_fs":"1","ft_si":"1","grpc_port":"8503","id":"9da2304b-3829-4af8-7256-bc240d57d42b","port":"8300","raft_vsn":"3","role":"consul","segment":"","use_tls":"1","vsn":"2","vsn_max":"3","vsn_min":"2","wan_join_port":"8302"},"Status":1,"ProtocolMin":1,"ProtocolMax":5,"ProtocolCur":2,"DelegateMin":2,"DelegateMax":5,"DelegateCur":4}]