Test Endpoint Setup - Part Three
The final step in test endpoint setup is to deploy the Hopr Sidecar to your Kubernetes pod and test its connection to the Hopr test endpoint.
Test Deployment
Finally, the deployment section is shown. This YAML deploys three (3) containers into the namespace.
- curl-test: This container simulates a client. On an interval, it contacts the xtra-router container which should encrypt and proxy the communication out to the XTRA test endpoint on the Internet. The URL environment variable may need to be changed if the Envoy listener configuration is modified.
- xtra-router: This container proxies network communication inside the Pod. It can be configured in many ways to accomplish a desired result via the ConfigMap shown previously. This ConfigMap is mounted as the /etc/envoy/envoy.yaml file in the container, which is loaded and used as the running configuration by Envoy.
- xtra-keyserver: This container is used by plugin within the xtra-router container. It provides a rotating key to the router on demand, which will be used to encrypt/decrypt network communication. The license secret is used by this container as environment variable. The CHIPS algorithm shown is the default for the public XTRA test endpoint, but can be changed for scenarios where the remote endpoint uses a different one.
Installation
1. Test access to your Kubernetes cluster:
2. Deploy the hopr-test.yaml resources:
Output from the command:
3. Check that the pod has all containers running
Output from the command:
4. Check the logs for the curl-test container, which is attempting to contact the XTRA test endpoint via encrypted communication. Use the pod name from the command output above.
Output from the command:
Removal
1. Remove the hopr-test.yaml resources: