Comprehensive Enhancements to Dependency-Track Helm Chart w/o 3rd party dependencies

[JuryA]

🛠 Helm Chart Enhancement

• Ingress Template Rewrite: Overhauled the Dependency Track Ingress Template to align with the Bitnami common format, enabling detailed customization and expanded base service definitions. Reimplemented without 3rd party dependencies.
• New Template Introductions: Added new templates (dependencytrack.tpl.render, dependencytrack.namespace, dependencytrack.secrets.lookup, dependencytrack.ingress.certManagerRequest) to encapsulate common operations and boost chart maintainability.
• Custom Resource Deployment: Implemented a method for deploying additional Kubernetes resources through a custom Helm chart, offering users more flexibility to extend the chart with personal specifications.

🔐 TLS Support

• TLS Secrets Management: Introduced a new template for managing TLS Secrets, streamlining certificate handling and enhancing security.
• Enhanced Certificate Logic: Updated certificate management to differentiate between auto-generated certificates and those provided by the user, improving flexibility.
• TLS Configuration Fields: Enhanced values.yaml with new fields related to TLS configuration, providing clear options for setup.

📖 Documentation

• Detailed Annotations: Annotated Ingress and TLS related values in values.yaml extensively, adhering to Helm-docs standards to aid user comprehension.
• Updated README: Revised the README document to reflect the recent changes and additions to the chart.

📁 Repository and Codebase Maintenance

• Repository Clean-up: Updated .gitignore with new patterns to exclude system generated files and specific IDE/system files.
• Helm Packaging: Introduced a .helmignore file to limit contents packaged into the Helm chart.
• Extra Deployment Options: Added extraDeploy.yaml to allow specification of extra Kubernetes resources, enhancing the chart's customization and extension capabilities.

🧪 How to Test

1. Deploy and Validate: Deploy the updated chart in a controlled environment. Validate all new functionalities and custom configurations.
2. TLS and Certificates: Test the TLS configurations extensively to ensure certificates are handled correctly, whether auto-generated or user-provided.
3. Documentation Review: Verify that the documentation accurately reflects the chart's capabilities and setup instructions.
4. Extended Customization: Test the deployment of additional resources via extraDeploy.yaml to confirm functionality and integration without impacting core components.

📅 Impact

As a result of these updates, the Dependency-Track Helm chart is not only more extensible and customizable but also aligns with industry standards and best practices. These improvements significantly enhance usability and potential use cases, ensuring that the chart remains relevant and robust in diverse environments.

Please review the extensive changes and provide feedback. Due to the broad scope of updates, extensive testing is recommended to ensure there are no unforeseen issues.

Closes #17

[petrzjunior]

I am a big fan of this. Moreover I would appreciate the ability so specify additional volumes and volume mounts. My use case is the Secrets Store CSI driver which allows mounting secrets only after they are mounted as a volume first.