Skip to main content

Chart Dependencies

Chart Dependencies allow you to add external charts to your project, following the same pattern as Helm Chart Dependencies . This feature enables you to integrate third-party services and components seamlessly into your SleakOps deployment.

NodePool Configuration Required

Since SleakOps uses NodePools to determine resource placement, you must configure the tolerations parameter to target an existing NodePool for all dependency resources.

Supported Chart Repositories​

Currently, SleakOps supports Bitnami Charts exclusively. You can browse available charts on ArtifactHub to find suitable dependencies for your project.

Adding Chart Dependencies​

To add a new Chart Dependency, click the Create button in the Chart Configuration section:

Chart dependencies create button

Configuration Steps​

  1. Search and Select: Use the first two fields to search for the chart name and select your desired version
  2. Configure Values: Modify the values section below to customize the deployment
  3. Set Tolerations: Critical - Update all tolerations fields in the chart values to target your NodePool
Chart dependencies configuration form
Important

Ensure every tolerations field in the chart values is properly configured to use a NodePool. Without this configuration, Kubernetes cannot determine where to schedule the pods, leading to deployment failures.

Frequently Asked Questions​

My deployment succeeded but pods aren't working. What's wrong?​

The most common cause is incorrect NodePool configuration. Verify that:

  • All tolerations fields are properly set to target existing NodePools
  • The NodePool has sufficient resources
  • The NodePool is in a healthy state

I can't find the chart I need. What are my options?​

Currently, only Bitnami repository charts are supported. If you need a chart not available in Bitnami's repository, please contact our support team to discuss alternatives or request additional repository support.

How do I troubleshoot dependency deployment issues?​

Common troubleshooting steps:

  1. Verify NodePool tolerations are correctly configured
  2. Check that the chart version is compatible
  3. Ensure required values are properly set
  4. Review pod logs for specific error messages

My resources won't mount EBS volumes correctly. What should I check?​

  1. Ensure that the EBS CSI Driver is installed and functioning in your cluster. You can refer to the Addon documentation for guidance on setting up EBS.
  2. Ensure you completed the values with the appropriate storageClass that is created with the EBS addon. For example a persistence value for a chart could look like this:
persistence:
  enabled: true
  storageClass: "ebs-csi-default-sc"
  accessModes:
    - ReadWriteOnce
  size: 5Gi
  1. In case you need another storageClass, you can define it as an extra template and use it. Remember to set the provisioner to ebs.csi.aws.com.
  2. In case the pods are not starting, check the logs of the EBS CSI Controller for errors

My resources won't mount EFS volumes correctly. What should I check?​

  1. Ensure that the EFS CSI Driver is installed and functioning in your cluster. Sleakops installs this addon when you create a volume for a project. You can create and then delete a volume to complete the installation.
  2. Ensure you completed the values with the appropriate storageClass that you prefer for this data. Sleakops creates two StorageClasses when installing the EFS addon: efs-sc-retain and efs-sc-delete. For example a persistence value for a chart could look like this:
persistence:
  enabled: true
  storageClass: "efs-sc-retain"
  accessModes:
    - ReadWriteMany
  size: 5Gi
  1. In case you need another storageClass, you can define it as an extra template and use it. Remember to set the provisioner to efs.csi.aws.com.
  2. In case the pods are not starting, check the logs of the EFS CSI Controller for errors

Pods won't start due to image pull errors. What should I check?​

  1. Verify that the image name and tag specified in the chart values are correct.
  2. Verify that the repository is bitnamilegacy instead of bitnami.
  3. Verify if there is a value allowInsecureImages: false and change it to allowInsecureImages: true.