Skip to content

Commit b7c8eed

Browse files
authored
Remove link to helm repo (#3805)
1 parent 154fa30 commit b7c8eed

File tree

1 file changed

+2
-42
lines changed

1 file changed

+2
-42
lines changed

docs/kubernetes/ingress-controller.md

Lines changed: 2 additions & 42 deletions
Original file line numberDiff line numberDiff line change
@@ -490,48 +490,8 @@ instance to be cluster-wide, watching all `Ingress` objects across all namespace
490490

491491
## Helm-based deployment
492492

493-
[Helm](https://helm.sh/) calls itself the package manager for Kubernetes and therefore take cares of the deployment of whole applications including resources like services, configurations and so on.
494-
495-
Skipper is also available as community contributed Helm chart in the public [quay.io](https://quay.io/repository/) registry.
496-
The latest packaged release can be found [here](https://quay.io/application/baez/skipper).
497-
The source code is available at [GitHub](https://github.com/baez90/skipper-helm).
498-
499-
The chart includes resource definitions for the following use cases:
500-
501-
- RBAC
502-
- [Prometheus-Operator](https://github.com/prometheus-operator/prometheus-operator)
503-
504-
As this chart is not maintained by the Skipper developers and is still under development only the basic deployment workflow is covered here.
505-
Check the GitHub repository for all details.
506-
507-
To be able to deploy the chart you will need the following components:
508-
509-
- `helm` CLI (Install guide [here](https://github.com/kubernetes/helm))
510-
- Helm registry plugin (available [here](https://github.com/app-registry/appr-helm-plugin))
511-
512-
If your environment is setup correctly you should be able to run `helm version --client` and `helm registry version quay.io` and get some information about your tooling without any error.
513-
514-
It is possible to deploy the chart without any further configuration like this:
515-
516-
helm registry upgrade quay.io/baez/skipper -- \
517-
--install \
518-
--wait \
519-
"your release name e.g. skipper"
520-
521-
The `--wait` switch can be omitted as it only takes care that Helm is waiting until the chart is completely deployed (meaning all resources are created).
522-
523-
To update the deployment to a newer version the same command can be used.
524-
525-
If you have RBAC enabled in your Kubernetes instance you don't have to create all the previously described resources on your own but you can let Helm create them by simply adding one more switch:
526-
527-
helm registry upgrade quay.io/baez/skipper -- \
528-
--install \
529-
--wait \
530-
--set rbac.create=true \
531-
"your release name e.g. skipper"
532-
533-
There are some more options available for customization of the chart.
534-
Check the repository if you need more configuration possibilities.
493+
Skipper is not available as a Helm chart.
494+
There is a [ticket asking for a helm chart](https://github.com/zalando/skipper/issues/3355).
535495

536496
## Run as API Gateway with East-West setup
537497

0 commit comments

Comments
 (0)