You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: addons/grafana/10/README.md
+17-17Lines changed: 17 additions & 17 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,12 +1,12 @@
1
1
<!--- app-name: Grafana -->
2
2
3
-
# Grafana packaged by Bitnami
3
+
# Grafana packaged by Drycc
4
4
5
5
Grafana is an open source metric analytics and visualization suite for visualizing time series data that supports various types of data sources.
6
6
7
7
[Overview of Grafana](https://grafana.com/)
8
8
9
-
Trademarks: This software listing is packaged by Bitnami. The respective trademarks mentioned in the offering are owned by the respective companies, and use of them does not imply any affiliation or endorsement.
9
+
Trademarks: This software listing is packaged by Drycc. The respective trademarks mentioned in the offering are owned by the respective companies, and use of them does not imply any affiliation or endorsement.
This chart bootstraps a [grafana](https://github.com/drycc/containers/tree/main/drycc/grafana) deployment on a [Kubernetes](https://kubernetes.io) cluster using the [Helm](https://helm.sh) package manager.
21
21
22
-
Bitnami charts can be used with [Kubeapps](https://kubeapps.dev/) for deployment and management of Helm Charts in clusters.
22
+
Drycc charts can be used with [Kubeapps](https://kubeapps.dev/) for deployment and management of Helm Charts in clusters.
23
23
24
24
## Prerequisites
25
25
@@ -51,9 +51,9 @@ $ helm delete my-release
51
51
52
52
The command removes all the Kubernetes components associated with the chart and deletes the release. Use the option `--purge` to delete all persistent volumes too.
53
53
54
-
## Differences between the Bitnami Grafana chart and the Bitnami Grafana Operator chart
54
+
## Differences between the Drycc Grafana chart and the Drycc Grafana Operator chart
55
55
56
-
In the Bitnami catalog we offer both the drycc/grafana and drycc/grafana-operator charts. Each solution covers different needs and use cases.
56
+
In the Drycc catalog we offer both the drycc/grafana and drycc/grafana-operator charts. Each solution covers different needs and use cases.
57
57
58
58
The *drycc/grafana* chart deploys a single Grafana installation (with grafana-image-renderer) using a Kubernetes Deployment object (together with Services, PVCs, ConfigMaps, etc.). The figure below shows the deployed objects in the cluster after executing *helm install*:
59
59
@@ -441,12 +441,12 @@ This solution allows to easily deploy multiple Grafana instances compared to the
It is strongly recommended to use immutable tags in a production environment. This ensures your deployment does not change automatically if the same tag is updated with a different image.
488
488
489
-
Bitnami will release a new chart updating its containers if a new version of the main container, significant changes, or critical vulnerabilities exist.
489
+
Drycc will release a new chart updating its containers if a new version of the main container, significant changes, or critical vulnerabilities exist.
490
490
491
491
### Using custom configuration
492
492
@@ -614,14 +614,14 @@ As an alternative, you can use of the preset configurations for pod affinity, po
614
614
615
615
## Persistence
616
616
617
-
The [Bitnami Grafana](https://github.com/drycc/containers/tree/main/drycc/grafana) image stores the Grafana data and configurations at the `/opt/drycc/grafana/data` path of the container.
617
+
The [Drycc Grafana](https://github.com/drycc/containers/tree/main/drycc/grafana) image stores the Grafana data and configurations at the `/opt/drycc/grafana/data` path of the container.
618
618
619
619
Persistent Volume Claims are used to keep the data across deployments. This is known to work in GCE, AWS, and minikube.
620
620
See the [Parameters](#parameters) section to configure the PVC or to disable persistence.
621
621
622
622
## Troubleshooting
623
623
624
-
Find more information about how to deal with common errors related to Bitnami's Helm charts in [this troubleshooting guide](https://docs.drycc.com/general/how-to/troubleshoot-helm-chart-issues).
624
+
Find more information about how to deal with common errors related to Drycc's Helm charts in [this troubleshooting guide](https://docs.drycc.com/general/how-to/troubleshoot-helm-chart-issues).
625
625
626
626
## Upgrading
627
627
@@ -631,7 +631,7 @@ This major release only bumps the Grafana version to 9.x. No major issues are ex
631
631
632
632
### To 7.0.0
633
633
634
-
This major release renames several values in this chart and adds missing features, in order to be inline with the rest of assets in the Bitnami charts repository.
634
+
This major release renames several values in this chart and adds missing features, in order to be inline with the rest of assets in the Drycc charts repository.
635
635
636
636
Since the volume access mode when persistence is enabled is `ReadWriteOnce` in order to upgrade the deployment you will need to either use the `Recreate` strategy or delete the old deployment.
637
637
@@ -651,7 +651,7 @@ This version also introduces `drycc/common`, a [library chart](https://helm.sh/d
651
651
**What changes were introduced in this major version?**
652
652
653
653
- Previous versions of this Helm Chart use `apiVersion: v1` (installable by both Helm 2 and 3), this Helm Chart was updated to `apiVersion: v2` (installable by Helm 3 only). [Here](https://helm.sh/docs/topics/charts/#the-apiversion-field) you can find more information about the `apiVersion` field.
654
-
- The different fields present in the *Chart.yaml* file has been ordered alphabetically in a homogeneous way for all the Bitnami Helm Charts
654
+
- The different fields present in the *Chart.yaml* file has been ordered alphabetically in a homogeneous way for all the Drycc Helm Charts
655
655
656
656
**Considerations when upgrading to this version**
657
657
@@ -677,7 +677,7 @@ This major version signifies this change.
Copy file name to clipboardExpand all lines: addons/index.yaml
+4-1Lines changed: 4 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -74,4 +74,7 @@ entries:
74
74
description: "YugabyteDB is a high-performance distributed SQL database for powering global, internet-scale applications. "
75
75
nessie:
76
76
- version: "0.103"
77
-
description: "Transactional Catalog for Data Lakes with Git-like semantics . "
77
+
description: "Transactional Catalog for Data Lakes with Git-like semantics . "
78
+
lakefs:
79
+
- version: "1.52"
80
+
description: "LakeFS provides version control over the data lake, and uses Git-like semantics to create and access those versions. If you know git, you’ll be right at home with lakeFS. "
0 commit comments