diff --git a/deploy/charts/backend/Chart.yaml b/deploy/charts/backend/Chart.yaml index 4cbde61ba..80657f8fa 100644 --- a/deploy/charts/backend/Chart.yaml +++ b/deploy/charts/backend/Chart.yaml @@ -21,4 +21,4 @@ version: 0.1.0 # incremented each time you make changes to the application. Versions are not expected to # follow Semantic Versioning. They should reflect the version the application is using. # It is recommended to use it with quotes. -appVersion: "v0.5.1" +appVersion: "v0.6.0" diff --git a/docs/content/setup/helm.md b/docs/content/setup/helm.md index e26ab2122..b91d36649 100644 --- a/docs/content/setup/helm.md +++ b/docs/content/setup/helm.md @@ -64,8 +64,7 @@ helm upgrade \ --set 'gatewayApi.route.hostnames[0]=kube-bind.example.com' \ --set gatewayApi.route.path=/ \ --set gatewayApi.route.pathType=PathPrefix \ - --set image.tag=${VERSION} \ - kube-bind \ + --set image.tag=v${VERSION} \ kube-bind oci://ghcr.io/kube-bind/charts/backend --version ${VERSION} ``` diff --git a/docs/content/usage/.pages b/docs/content/usage/.pages index 0432813a3..60fed3eb5 100644 --- a/docs/content/usage/.pages +++ b/docs/content/usage/.pages @@ -2,3 +2,4 @@ nav: - index.md - api-concepts.md - synchronization.md + - integrations \ No newline at end of file diff --git a/docs/content/usage/index.md b/docs/content/usage/index.md index 067456399..822627891 100644 --- a/docs/content/usage/index.md +++ b/docs/content/usage/index.md @@ -88,8 +88,7 @@ If you're new to kube-bind: 1. **Start with the [Quickstart Guide](../setup/quickstart.md)** for a hands-on introduction 2. **Review [API Concepts](api-concepts.md)** to understand the fundamental types -3. **Explore [Template References](template-references.md)** for advanced use cases -4. **Check the [Reference Documentation](../reference/)** for complete API specifications +3. **Check the [Reference Documentation](../reference/)** for complete API specifications The konnector agents establish a secure, authenticated connection that allows: diff --git a/docs/content/usage/integrations/.pages b/docs/content/usage/integrations/.pages new file mode 100644 index 000000000..c695c2b86 --- /dev/null +++ b/docs/content/usage/integrations/.pages @@ -0,0 +1,2 @@ +nav: + - cert-manager.md \ No newline at end of file diff --git a/docs/content/usage/integrations/cert-manager.md b/docs/content/usage/integrations/cert-manager.md new file mode 100644 index 000000000..0f59e84a0 --- /dev/null +++ b/docs/content/usage/integrations/cert-manager.md @@ -0,0 +1,103 @@ +--- +title: Cert-Manager +description: | + Guide on integrating kube-bind with cert-manager for automated TLS certificate management. +weight: 10 +--- + +# Cert-Manager Integration + +1. **Install cert-manager** in your Kubernetes cluster, where kube-bind backend is running, if you haven't already. You can follow the official installation guide [here](https://cert-manager.io/docs/installation/kubernetes/). + + +2. **Create a `kube-bind` template for `Certificate` resources** to allow service consumers to request TLS certificates. Below is an example template: + +```yaml +kubectl apply -f - <