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
helm template test sentrius-chart-launcher --dry-run
66
+
helm template test sentrius-chart --set environment=local --set ingress.tlsEnabled=false --dry-run
67
+
68
+
# Test with custom values
69
+
helm template test sentrius-chart-launcher \
70
+
--set tenant=my-tenant \
71
+
--set baseRelease=my-sentrius \
72
+
--dry-run
73
+
```
74
+
75
+
## Known Issues
76
+
77
+
### Sentrius Chart Ingress Template
78
+
79
+
The main `sentrius-chart` has a known issue with the ingress template that causes linting failures. This is a YAML parsing issue in the conditional annotations section. The CI/CD pipeline handles this gracefully:
80
+
81
+
- Identifies the issue during linting
82
+
- Continues testing other charts
83
+
- Provides warnings rather than failing the entire pipeline
84
+
85
+
### Workarounds
86
+
87
+
Until the ingress template is fixed, you can:
88
+
89
+
1. Use the `sentrius-chart-launcher` which works correctly
90
+
2. Test `sentrius-chart` with `ingress.tlsEnabled=false`
91
+
3. Use the local deployment scripts which work around the issue
92
+
93
+
## Chart Testing Best Practices
94
+
95
+
### For Developers
96
+
97
+
1.**Always test locally** before pushing:
98
+
```bash
99
+
./ops-scripts/test-helm-charts.sh
100
+
```
101
+
102
+
2.**Test with different environments**:
103
+
- Local (`environment=local`)
104
+
- GKE (`environment=gke`)
105
+
- AWS (`environment=aws`)
106
+
107
+
3.**Validate template rendering** with various configurations
108
+
109
+
4.**Check for proper schema** in Chart.yaml files
110
+
111
+
### For CI/CD
112
+
113
+
1.**Linting runs on every push** and pull request
114
+
2.**Integration testing runs on pull requests** using Kind clusters
The new testing ensures these scripts work with validated charts.
127
+
128
+
## Future Improvements
129
+
130
+
Potential enhancements for the CI/CD testing:
131
+
132
+
1.**Fix ingress template** YAML parsing issues
133
+
2.**Add security scanning** for Helm charts
134
+
3.**Performance testing** for large deployments
135
+
4.**Multi-cluster testing** for different Kubernetes versions
136
+
5.**Automated deployment** to staging environments
137
+
138
+
## Troubleshooting
139
+
140
+
### Common Issues
141
+
142
+
1.**Chart linting failures**: Usually YAML syntax or template issues
143
+
2.**Template rendering failures**: Often due to missing or invalid values
144
+
3.**Integration test failures**: May indicate resource conflicts or insufficient cluster resources
145
+
146
+
### Debug Commands
147
+
148
+
```bash
149
+
# Verbose linting
150
+
helm lint sentrius-chart --debug
151
+
152
+
# Template with debug output
153
+
helm template test sentrius-chart --debug
154
+
155
+
# Validate generated YAML
156
+
helm template test sentrius-chart-launcher | kubectl apply --dry-run=client -f -
157
+
```
158
+
159
+
## Conclusion
160
+
161
+
The new Helm chart CI/CD testing provides robust validation for Sentrius deployments, ensuring reliability and compatibility across different environments while maintaining development velocity.
0 commit comments