Skip to content

updated startup probe and ingress documentation #39

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Nick-Andreano merged 1 commit into from
Jan 29, 2026
Merged

updated startup probe and ingress documentation #39

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion charts/iap/values.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -301,7 +301,7 @@ readinessProbe:
# probe has succeeded once, the liveness probe takes over.
startupProbe:
enabled: true
initialDelaySeconds: 90
initialDelaySeconds: 180
periodSeconds: 30
timeoutSeconds: 10
failureThreshold: 3
Expand Down
26 changes: 26 additions & 0 deletions docs/ingress.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -68,6 +68,32 @@ ingress:
alb.ingress.kubernetes.io/target-group-attributes: stickiness.enabled=true,stickiness.lb_cookie.duration_seconds=3600
```

**SSL/TLS Certificate Configuration:**

For SSL/TLS termination at the ALB level, specify an AWS Certificate Manager (ACM) certificate using the `certificate-arn` annotation:

```yaml
annotations:
alb.ingress.kubernetes.io/certificate-arn: "arn:aws:acm:region:account-id:certificate/certificate-id"
```

The `certificate-arn` annotation:
- Specifies the ARN (Amazon Resource Name) of an ACM certificate
- Enables SSL/TLS termination at the load balancer
- Supports multiple certificates by providing comma-separated ARNs
- The certificate must be in the same AWS region as the ALB
- Requires the ALB to have HTTPS listeners configured (via `listen-ports`)

**Example with certificate:**

```yaml
ingress:
annotations:
alb.ingress.kubernetes.io/certificate-arn: "arn:aws:acm:us-east-1:123456789012:certificate/12345678-1234-1234-1234-123456789012"
alb.ingress.kubernetes.io/listen-ports: '[{"HTTPS": 443}]'
alb.ingress.kubernetes.io/ssl-policy: "ELBSecurityPolicy-TLS-1-2-2017-01"
```

#### NGINX Ingress Controller - Alternative Option

For environments where ALB is not available or preferred, NGINX Ingress Controller can be used as an alternative.
Expand Down