From 5927be7d73da776e77faf146709ee4b2c2b17f0e Mon Sep 17 00:00:00 2001 From: Philippe Merle Date: Mon, 30 Dec 2024 23:10:05 +0100 Subject: [PATCH] Update links to KubeDiagrams configuration files --- README.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index 81580de..70ea2c5 100644 --- a/README.md +++ b/README.md @@ -104,9 +104,9 @@ Supported `kind`/`apiVersion` resource types are 32 ones: * StorageClass/storage.k8s.io/v1 * User/rbac.authorization.k8s.io/v1 -**Note**: The mapping between these supported Kubernetes resources and architecture diagrams is defined into [bin/kube-diagrams.yml](bin/kube-diagrams.yaml#L24). +**Note**: The mapping between these supported Kubernetes resources and architecture diagrams is defined into [bin/kube-diagrams.yml](bin/kube-diagrams.yaml#L31). -**Note**: The mapping for any Kubernetes custom resources can be also defined into **KubeDiagrams** configuration files as illustrated in [examples/k0s/KubeDiagrams.yml](examples/k0s/KubeDiagrams.yml#L10). +**Note**: The mapping for any Kubernetes custom resources can be also defined into **KubeDiagrams** configuration files as illustrated in [examples/k0s/KubeDiagrams.yml](examples/k0s/KubeDiagrams.yml#L10) and [free5gc-k8s/KubeDiagrams.yml](free5gc-k8s/KubeDiagrams.yml#L3). Currently, unsupported `kind`/`apiGroup` resource types are 27 ones: * Binding/ @@ -139,7 +139,7 @@ Currently, unsupported `kind`/`apiGroup` resource types are 27 ones: ## Kubernetes resources clustering -With **KubeDiagrams**, Kubernetes resources can be clustered within the architecture diagrams automatically. **KubeDiagrams** uses the `metadata.namespace` resource field as first clustering criteria. Then, the `metadata.labels` keys can be used to define subclusters. Following table lists the predefined mappings between label keys and cluster titles as defined in the [bin/kube-diagrams.yml](bin/kube-diagrams.yaml#L13) file (see the `clusters` list). +With **KubeDiagrams**, Kubernetes resources can be clustered within the architecture diagrams automatically. **KubeDiagrams** uses the `metadata.namespace` resource field as first clustering criteria. Then, the `metadata.labels` keys can be used to define subclusters. Following table lists the predefined mappings between label keys and cluster titles as defined in the [bin/kube-diagrams.yml](bin/kube-diagrams.yaml#L20) file (see the `clusters` list). | Label | Cluster Title | | :--------: | :-------: |