Investigate and Fix Potential Breakages from App-Template Version Update

[osnabrugge]

Investigate and Fix Potential Breakages from App-Template Version Update

Findings:

• The recent commit updates the app-template version, which affects various Kubernetes kustomization.yaml files and related configurations.
• Key files impacted:
  • kubernetes/main/apps/default/compreface/app/kustomization.yaml
  • kubernetes/main/apps/default/atuin/app/kustomization.yaml
  • kubernetes/main/apps/default/prowlarr/app/kustomization.yaml
  • kubernetes/main/apps/default/authelia/app/kustomization.yaml
  • kubernetes/main/templates/volsync/readme.md
  • kubernetes/main/templates/volsync/r2.yaml

Action Items:

1. Review kustomization.yaml Files:

   • Ensure all kustomization.yaml files reference the correct paths and resources.
   • Validate the configMapGenerator and generatorOptions sections for authelia and other related apps.

2. Test VolSync Configuration:

   • Ensure the volsync template and related configuration in r2.yaml are correctly set up for ReplicationSource and ReplicationDestination.

3. Update Documentation:

   • Verify and update the readme.md for volsync to reflect the correct configurations and any new required/optional postBuild variables.

4. Run Tests:

   • Execute the necessary tests within the repo to confirm compatibility with the updated app-template version.

References:

• Commit 135b56bbdeb0b62ef8fd3564293e79939e9acdb0: Update app-template from 3.4.0 to 3.5.1.
• Commit Comparison: 6d23aa66ca7a707249b7f4c2ca28bf46e4ab1357...86062681a96dc15b6afe9d6b5dd2178f57ee0ebc: Review the changes introduced between versions 3.5.1 and 3.40.

Detailed Changes to Investigate:

• values.yaml:

  • Synchronize your local values.yaml with the upstream changes.
  • Look for any new configuration options or removed settings that may affect your deployments.

• kustomization.yaml:

  • For compreface, atuin, and prowlarr, ensure the resources and paths are correctly referenced.
  • For authelia, check and validate configMapGenerator and generatorOptions settings.

• VolSync Configuration:

  • Ensure r2.yaml is correctly configured for both ReplicationSource and ReplicationDestination.
  • Validate postBuild configurations in readme.md and ensure all required variables are set correctly.

Next Steps:

1. Synchronize and Validate Configurations:

   • Update values.yaml to match upstream changes.
   • Validate all kustomization.yaml files and ensure correct resource paths and configurations.

2. Test Deployments:

   • Deploy the updated charts in a staging environment to validate the changes.
   • Monitor for any issues and adjust configurations as needed.

3. Document and Communicate:

   • Update documentation to reflect the new configurations and any additional steps required.
   • Communicate the changes and required actions to all team members (that would be me 👌.