If you want to learn more about the Pod IP based Load Balancing, please refer to the following link.
- Traffic Modes in Application load balancing on Amazon EKS
Kubernetes Ingress is a resource that manages external access to the services in a cluster, typically HTTP.
You can create the ingress using the following steps.
First, you need to purchase the service domain. (e.g. example.com
)
After that, create a public hosted zone in Route53 and delegate the nameserver from the provider to Route53.
The ALB Ingress Controller and External DNS are required to automatically create DNS records and ALB through the kubernetes ingress
.
You need to create a public certificate for the ALB to use HTTPS.
Request a public certificate and add the following FQDN.
console.example.com
*.api.example.com
*.grpc.example.com
(optional)webhook.example.com
(optional)
When creating a certificate, you need to copy the certificate ARN and use it when creating the ingress.
First, you need to download all the ingress files and replace the certificate-arn
and hostname
with your own.
- Console: console_ingress.yaml
- REST API: rest_api_ingress.yaml
- gRPC API: grpc_api_ingress.yaml
- Monitoring Webhook: monitoring_webhook_ingress.yaml
And then, apply the ingress files.
kubectl apply -f console_ingress.yaml -n spaceone
kubectl apply -f rest_api_ingress.yaml -n spaceone
kubectl apply -f grpc_api_ingress.yaml -n spaceone
kubectl apply -f monitoring_webhook_ingress.yaml -n spaceone
gRPC API
andMonitoring Webhook
are optional. If you don't need it, you don't need to apply it.
You can access the console using the following URL.