Merge upstream/master-vnext into feature/add-network-policy
Resolve conflicts by combining NetworkPolicy feature with all features from master-vnext integration branch: - NetworkPolicy support (this branch) - HTTPRoute support - envFrom support - Startup probe - Cache persistence - IPv6 dual-stack - revisionHistoryLimit - initContainers deprecation Updated version to 3.0.0 and merged all changelog entries. Regenerated README.md from template. Co-Authored-By: Claude <noreply@anthropic.com> Signed-off-by: Aleksei Sviridkin <f@lex.la>
This commit is contained in:
14 files changed
+1351
-19
No files matched your search
@@ -59,6 +59,33 @@ helm install my-jellyfin jellyfin/jellyfin -f values.yaml
|
||||
|
||||
{{ template "helm-docs.versionFooter" . }}
|
||||
|
||||
## Gateway API HTTPRoute
|
||||
|
||||
This chart supports the Kubernetes Gateway API HTTPRoute resource as a modern alternative to Ingress.
|
||||
|
||||
To use HTTPRoute, you need to have Gateway API CRDs installed in your cluster and a Gateway resource configured.
|
||||
|
||||
Example configuration:
|
||||
|
||||
```yaml
|
||||
httpRoute:
|
||||
enabled: true
|
||||
annotations: {}
|
||||
parentRefs:
|
||||
- name: my-gateway
|
||||
namespace: gateway-system
|
||||
sectionName: https
|
||||
hostnames:
|
||||
- jellyfin.example.com
|
||||
rules:
|
||||
- matches:
|
||||
- path:
|
||||
type: PathPrefix
|
||||
value: /
|
||||
```
|
||||
|
||||
For more information about Gateway API, see: <https://gateway-api.sigs.k8s.io/>
|
||||
|
||||
## Hardware acceleration
|
||||
|
||||
Out of the box the pod does not have the necessary permissions to enable hardware acceleration (HWA) in Jellyfin.
|
||||
@@ -286,3 +313,32 @@ networkPolicy:
|
||||
- Either disable NetworkPolicy or disable host networking
|
||||
|
||||
For more configuration options, see the full values documentation in [values.yaml](values.yaml).
|
||||
|
||||
## IPv6 Configuration
|
||||
|
||||
This chart supports IPv6 and dual-stack networking configurations out of the box. Health probes use httpGet by default for compatibility with both IPv4 and IPv6.
|
||||
|
||||
### IPv6-only Configuration
|
||||
|
||||
For IPv6-only clusters:
|
||||
|
||||
```yaml
|
||||
service:
|
||||
ipFamilyPolicy: SingleStack
|
||||
ipFamilies:
|
||||
- IPv6
|
||||
```
|
||||
|
||||
### Dual-stack Configuration
|
||||
|
||||
For dual-stack clusters (both IPv4 and IPv6):
|
||||
|
||||
```yaml
|
||||
service:
|
||||
ipFamilyPolicy: PreferDualStack # or RequireDualStack
|
||||
ipFamilies:
|
||||
- IPv4
|
||||
- IPv6 # First family in the list is the primary
|
||||
```
|
||||
|
||||
For more information about Kubernetes dual-stack networking, see: <https://kubernetes.io/docs/concepts/services-networking/dual-stack/>
|
||||
Reference in new issue
Block a user