These customizations can range from ingress configurations, cloud storage and backup settings, custom password implementations, to minor alterations to suit our platform needs. Let’s delve into the specifics of each customized upstream chart.

ArgoCD

To enhance our interaction with ArgoCD, we have integrated an ingress that allows us to access ArgoCD publicly. While port-forwarding can be sufficient for local testing, a direct and steady connection will augment our operations in a production setting. ArgoCD can now be accessed at the following URL: argocd.eu-north-1.training.dx-book.com .

Let’s check it out:

kubectl get ingresses/argocd-ingress -n argocd

Chart Museum

With the goal of fine-tuning the chart management process, we made several improvements to the default Chart Museum configurations. These include enabling the overwrite of packages for flexibility and incorporating cloud storage with AWS S3 to ensure scalability and reliability of our chart storage.

values: |
  fullnameOverride: chartmuseum
  service:
    servicename: chartmuseum
  env:
    open:
      DISABLE_API: false
      ALLOW_OVERWRITE: true
      STORAGE: amazon
      STORAGE_AMAZON_BUCKET: training-dx-book-charts
      STORAGE_AMAZON_PREFIX:
      STORAGE_AMAZON_REGION: us-east-1
    secret:
      AWS_ACCESS_KEY_ID: AKIAUICYRSPXZSMCPWAXJ
      AWS_SECRET_ACCESS_KEY: XPWSBLCklsTpAZaZ0KYJRo21i60L6g5sk93kSrwrf  

Grafana

We understand the need for convenient access to our monitoring dashboards. Hence, we have added an ingress for Grafana, providing public access to our Grafana instance. It can be accessed via grafana.eu-north-1.training.dx-book.com.

Longhorn

TODO: Where does the aws-secret come from?

We customized longhorn to add a backup mechanism in AWS S3. It uses the aws-secret.

values: |
  defaultSettings:
    backupTarget: s3://training-dx-book-dev-backup@us-east-1/
    backupTargetCredentialSecret: aws-secret  

Prometheus

In an effort to streamline the authentication process, we pre-defined a password for the admin user. The pre-set password is: bPWxQ2HD3wN6fWWQ. It is recommended to change this password post-installation to maintain security.

Redis

Consistent with the Prometheus setup, we’ve also hard-coded a password for Redis to facilitate an initial smooth login. The pre-set password for Redis is: nfp7kzf8NTH!cga0keknfp7kzf8NTH!cga0keknfp7kzf8NTH!cga0kek.

Verdaccio

To ensure that Verdaccio runs efficiently, we have set up a persistent storage system using the longhorn storage class, allocating 4GB of space for it. Additionally, we’ve customized Verdaccio’s config.yaml file to suit our platform’s needs. For convenience during initial setup, both the username and password for Verdaccio have been set to verdaccio. These credentials should be updated post-installation for security reasons.