https://github.com/hops-ops/helm-linkerd
Crossplane configuration for linkerd Helm chart
https://github.com/hops-ops/helm-linkerd
crossplane crossplane-configuration crossplane-configurations crossplane-xrd helm kubernetes linkerd xrd
Last synced: 4 months ago
JSON representation
Crossplane configuration for linkerd Helm chart
- Host: GitHub
- URL: https://github.com/hops-ops/helm-linkerd
- Owner: hops-ops
- Created: 2026-01-13T07:44:40.000Z (5 months ago)
- Default Branch: main
- Last Pushed: 2026-01-28T17:43:28.000Z (4 months ago)
- Last Synced: 2026-01-29T08:33:32.298Z (4 months ago)
- Topics: crossplane, crossplane-configuration, crossplane-configurations, crossplane-xrd, helm, kubernetes, linkerd, xrd
- Language: KCL
- Size: 22.5 KB
- Stars: 0
- Watchers: 0
- Forks: 0
- Open Issues: 1
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# helm-linkerd
A Crossplane Configuration package that installs the linkerd-control-plane Helm chart with a minimal, stable interface.
## Overview
`helm-linkerd` renders a single Helm release for Linkerd. It exposes only the inputs needed
for chart values, namespace, and release name, keeping the interface stable while allowing full Helm overrides.
## Features
- **Minimal Helm interface**: values and overrideAllValues with stable defaults
- **Predictable naming**: defaults to `-linkerd` in the `linkerd` namespace
- **GitOps friendly**: ships a `.gitops/` deploy chart
## Prerequisites
- Crossplane installed in the cluster
- Crossplane providers:
- `provider-helm` (>=v1.0.2)
- Crossplane function:
- `function-auto-ready` (>=v0.6.0)
- Linkerd CRDs must be installed separately (use `linkerd-crds` chart or `linkerd install --crds-only`)
## Quick Start
```yaml
apiVersion: pkg.crossplane.io/v1
kind: Configuration
metadata:
name: helm-linkerd
spec:
package: ghcr.io/hops-ops/helm-linkerd:latest
```
```yaml
apiVersion: helm.hops.ops.com.ai/v1alpha1
kind: Linkerd
metadata:
name: linkerd
namespace: example-env
spec:
clusterName: example-cluster
values:
controllerReplicas: 2
```
## Identity and Certificates
Linkerd requires TLS certificates for its identity system. The default configuration uses
`identity.issuer.scheme: kubernetes.io/tls`. You must provide valid certificates either by:
1. Using cert-manager with a Linkerd Trust Anchor
2. Manually creating the required secrets
3. Using `overrideAllValues` to configure a different identity scheme
See [Linkerd Identity documentation](https://linkerd.io/2.14/tasks/automatically-rotating-control-plane-tls-credentials/) for details.
## Development
```bash
make render
make validate
make test
```
## License
Apache-2.0