Skip to content

Release/space1.16docs#1093

Open
tr0njavolta wants to merge 24 commits intomainfrom
release/space1.16docs
Open

Release/space1.16docs#1093
tr0njavolta wants to merge 24 commits intomainfrom
release/space1.16docs

Conversation

@tr0njavolta
Copy link
Member

@tr0njavolta tr0njavolta commented Feb 27, 2026

Description

Type of change

  • Bug fix (typo, broken link, incorrect info)
  • Content update (new info, clarification, reorganization)
  • New content (new page, section, or guide)

Checklist

  • I ran make vale-file FILE=docs/path/to/file.md locally for files changed (or will fix Vale suggestions in review)
  • Links work and point to the right places
  • If this adds new content, I tested the examples/instructions

Additional notes

@vercel
Copy link

vercel bot commented Feb 27, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
docs Ready Ready Preview, Comment Mar 5, 2026 4:10pm

Request Review

@cbuto cbuto force-pushed the release/space1.16docs branch from 2854e0e to 3b93008 Compare March 2, 2026 21:51
@cbuto cbuto force-pushed the release/space1.16docs branch from 4210fcf to 162ffdb Compare March 3, 2026 17:55
@cbuto cbuto force-pushed the release/space1.16docs branch from 162ffdb to 5284f6a Compare March 3, 2026 19:05
@cbuto cbuto force-pushed the release/space1.16docs branch from 5284f6a to 621f5e8 Compare March 3, 2026 19:42
@cbuto cbuto force-pushed the release/space1.16docs branch from 621f5e8 to 48be365 Compare March 3, 2026 19:45
@cbuto cbuto force-pushed the release/space1.16docs branch from 48be365 to ab324d0 Compare March 3, 2026 20:22
@cbuto cbuto force-pushed the release/space1.16docs branch from ab324d0 to e37dc7c Compare March 3, 2026 20:23
@cbuto cbuto force-pushed the release/space1.16docs branch from 657579d to 04446d8 Compare March 3, 2026 20:47
tr0njavolta and others added 2 commits March 4, 2026 16:22
Copy link
Member

@markandersontrocme markandersontrocme left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Small nits on being more explicit about Configuration values, and cloud selection

Comment on lines +32 to +40
```yaml
externalTLS:
host: proxy.example.com # Externally routable hostname for TLS certificates

router:
proxy:
service:
type: LoadBalancer
annotations:
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we specify this is the Spaces helm values?

Comment on lines +41 to +47
# AWS NLB (see Cloud-Specific Annotations for other clouds)
service.beta.kubernetes.io/aws-load-balancer-type: external
service.beta.kubernetes.io/aws-load-balancer-scheme: internet-facing
service.beta.kubernetes.io/aws-load-balancer-nlb-target-type: ip
```

See [Cloud-Specific Annotations](#cloud-specific-annotations) for GCP and Azure.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should this me a be more explicit this is for AWS and or provide tabs for AWS, GCP, Azure?

Comment on lines +77 to +88
```yaml
ingress:
provision: true
host: proxy.example.com
ingressClassName: "<your-ingress-class>"
# Annotations to add to the Ingress resource
annotations: {}
# Pod labels of the Ingress controller - used for network policy
podLabels: {}
# Namespace labels of the Ingress controller - used for network policy
namespaceLabels: {}
```
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we specify this is the Spaces helm values?

Comment on lines +244 to +246
### Install AWS Load Balancer Controller

The AWS Load Balancer Controller provisions a Network Load Balancer when you expose the spaces-router Service with the annotations in the next step.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: this only applies to an AWS Space install

- **Ingress is no longer provisioned by default.** The Ingress resource is now
controller-agnostic. All ingress-nginx specific annotations, labels, and the
hardcoded `ingressClassName: nginx` have been removed. To keep existing
ingress-nginx working, add the following to your Helm values:
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
ingress-nginx working, add the following to your Helm values:
ingress-nginx working, add the following to your spaces Helm values:

**2. Create EnvoyProxy and GatewayClass**

Create an `EnvoyProxy` resource that the GatewayClass references. See the [Envoy
Gateway EnvoyProxy docs][envoy-proxy] for the full API and more examples.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[envoy-proxy]: couldn't see the link definition for this reference.


| Spaces Version | Tested Kubernetes Versions |
|----------------|----------------------------|
| 1.15 | 1.32, 1.33, 1.34 |
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we add a line for 1.16?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants