The Integration documentation section is organized linearly; each document representing the next step in the Service Proxy for Kubernetes (SPK) integration process. The SPK integration process relies heavily on the Helm package manager to install each of the SPK software components.
This document provides a brief description of each integration step, and the command line interface (CLI) tools required to perform the integration tasks. A careful review of this document ensures a positive experience.
Note: You can click Next at the bottom of each page, or scroll through the SPK PDF to follow the integration process.
Install the CLI tools listed below on your Linux based workstation:
- Helm CLI - Manages the SPK Pod and Custom Resource (CR) installations.
- OpenSSL toolkit - Creates SSL certificates that secure Pod-to-Pod communication.
- Podman - Tags and pushes software images to local registries.
Integrating the SPK software images involves six required steps, and four optional steps:
- SPK Software - Extract and install the SPK software images and Custom Resource Definitions (CRDs).
- SPK Cert Manager - Automatically Secure communication between the SPK Pods, and regularly rotate secure secrets.
- Fluentd Logging - Optional: Centralize logging data sent from each of the installed SPK Pods.
- OTEL Collectors - Optional: Collect and view statistics from the SPK Controller and TMM Pods.
- dSSM Database - Optional: Store session-state data for the Service Proxy TMM Pod.
- SPK CWC - Install the Cluster Wide Controller to enable gathering SPK software telemetry.
- SPK Licensing - License the cluster to enable flexible consumption software use.
- SPK Controller - Prepare the cluster to proxy and load balance application traffic.
- SPK CRs - Configure a Custom Resource (CR) to begin processing application traffic.
Continue to the SPK Software guide to extract and install the SPK software.
Provide feedback to improve this document by emailing email@example.com.