373b8c3513
**Description**
<!--
Please include a summary of the change and which issue is fixed. Please
also include relevant motivation and context. List any dependencies that
are required for this change.
-->
⚒️ Fixes # <!--(issue)-->
Adds ingress GUI for Codeserver.
I pretty much generated a chart's `questions.yaml` and copied over the
main ingress section (with some small modifications). Let me know if
there is a 'smarter' way to do this.
**⚙️ Type of change**
- [X] ⚙️ Feature/App addition
- [ ] 🪛 Bugfix
- [ ] ⚠️ Breaking change (fix or feature that would cause existing
functionality to not work as expected)
- [ ] 🔃 Refactor of current code
**🧪 How Has This Been Tested?**
<!--
Please describe the tests that you ran to verify your changes. Provide
instructions so we can reproduce. Please also list any relevant details
for your test configuration
-->
Tested this on a SCALE system, with the Recyclarr chart (see notes).
Overall seems to work fine. I managed to add an ingress to the
Codeserver addon and use it to access its service.
I also compared the YAML of the created addon ingress against the YAML
of the main ingress of another chart. They seem identical (minus
expected differences such as names and such).
**📃 Notes:**
<!-- Please enter any other relevant information here -->
A few caveats worth mentioning (not related to but affecting this PR):
1. There is a fairly recent patch fixing a bug with the Codeserver addon
ingress (https://github.com/truecharts/library-charts/pull/615). Some
charts have not received the Common update yet (Recyclarr hasn't). I had
to manually change the Common version in Recyclarr's `Chart.yaml` and do
a `helm dep update` in order to test my changes. So it is probably a
good idea to wait until all apps get the Common update before we merge
this.
2. I am not sure if this is a bug or a feature, but when I enabled the
Codeserver addon for Recyclarr, and checked the service name with
`kubectl` I got this:
```bash
# k3s kubectl get service -n ix-recyclarr
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
recyclarr LoadBalancer 172.17.57.246 192.168.123.123 36107/TCP 71s
```
However, the Codeserver ingress assumes the name of the service to be
`$APPNAME-codeserver`:
|
||
---|---|---|
.chglog | ||
.devcontainer | ||
.github | ||
.vscode | ||
charts | ||
templates | ||
tools | ||
.all-contributorsrc | ||
.editorconfig | ||
.gitignore | ||
.helmdocsignore | ||
.markdownlint.yaml | ||
.pre-commit-config.yaml | ||
.snyk | ||
CNAME | ||
LICENSE | ||
cr.yaml | ||
cspell.config.yaml | ||
package.json | ||
yarn.lock |
.github/README.md
TrueCharts
Community Chart Catalog for TrueNAS SCALE
TrueCharts is a catalog of highly optimised TrueNAS SCALE Charts. Made for the community, By the community!
Our primary goals are:
-
Micro-Service Centered
-
Native Kubernetes
-
Stability
-
Consistency
All our charts are supposed to work together, be easy to setup using the TrueNAS UI and, above all, give the average user more than enough options to tune things to their liking.
Getting started using TrueCharts
Installing TrueCharts within TrueNAS SCALE, is possible using the TrueNAS SCALE Catalog list.
Check TrueCharts Quick-Start Guides for more information.
Support
Please check our FAQ, manual and Issue tracker There is a significant chance your issue has been reported before!
Still something not working as expected? Contact us! and we'll figure it out together!
Roadmap
For big changes we do have a roadmap, every spot on the roadmap is synced to a TrueNAS SCALE Release and should be read as "Should be added at or before this release"
Restructure of the Project - TrueNAS SCALE "Bluefin" 22.xx ALPHA 1
The current project is hitting internal performance issues, for this reason we need to rework the structure and split some parts of the project into separate repositories.
Refactor the Common Chart - TrueNAS SCALE "Bluefin" 22.xx ALPHA 2
The shared Common (chart) basis, used by all our Charts, needs some significant code cleanup. Primarily all code needs to follow a standardised format and comply to the same standard
Increased test coverage - TrueNAS SCALE "Bluefin" 22.xx BETA 1
With most parts of our project somewhat cleaned up, we need to work on increasing the coverage of our test system. Our unit tests should cover all features and we should also take upgrades into account when testing Chart changes
Development
Our development process is fully distributed and agile, so every chart-maintainer is free to set their own roadmap and development speed and does not have to comply to a centralised roadmap. This ensures freedom and flexibility for everyone involved and makes sure you, the end user, always has the latest and greatest of every Chart installed.
Getting into creating Charts
Creating charts takes some getting used to, as it's based on Helm charts. We highly suggest prior know-how on creation/modifying Helm Charts, before taking on the challenge of creating SCALE Apps.
For more information on creating SCALE Apps and Helm charts, please check out our development manual
Automation and you
We provide a lot of tools to make it easier to develop charts, templates, automated testing, automated fixes, automated docs. Even automated update is included. We also actively try to collaborate with other k8s community projects on tooling, for the betterment of all!
Those tools do, however, take time to develop and are certainly not bug free. If you find mistakes in our tooling, please feel free to repost issues or submit any fixes you feel appropriate!
Contact and Support
To contact the TrueCharts project:
-
Create an issue on Github issues
-
Open a Support Ticket
-
Send us an email
Featured Projects
A lot of our work is based on the great effort of others. We would love to extend special thanks to these projects we owe a lot to:
TrueNAS SCALE | K8S-At-Home | Traefik | Authelia |
Contributors ✨
Thanks goes to these wonderful people (emoji key):
This project follows the all-contributors specification. Contributions of any kind welcome!
Licence
Truecharts, is primarily based on a BSD-3-clause license, this ensures almost everyone can use and modify our charts. As a lot of Charts are based on upstream Helm Charts, Licences can vary on a per-Chart basis. This can easily be seen by the presence of a "LICENSE" file in said folder.
An exception to this, has been made for every document inside folders labeled as docs
or doc
and their subfolders: those folders are not licensed under BSD-3-clause and are considered "all rights reserved". Said content can be modified and changes submitted per PR, in accordance to the github End User License Agreement.
SPDX-License-Identifier: BSD-3-Clause