(fleet/netbox) Deploy netbox on Kueyen #1033
Draft
+430
−0
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request introduces configuration and secret management for deploying NetBox via Helm in the fleet system. The changes add manifests for external secrets, a Helm deployment definition, and a comprehensive values file for customizing the NetBox deployment, including security, persistence, and ingress settings.
NetBox Helm Deployment Configuration:
fleet/lib/netbox/fleet.yaml
to define the NetBox Helm chart deployment, including repository, version, and namespace settings.fleet/lib/netbox/values.yaml
with detailed configuration for NetBox, covering superuser setup, ingress, persistence, resource limits, security contexts, and integration with Valkey for authentication.External Secret Management:
fleet/lib/netbox/externalsecret-netbox-secrets.yaml
to provision NetBox credentials (username, password, email, API token) from OnePassword using ExternalSecret.fleet/lib/netbox/externalsecret-netbox-valkey.yaml
to provision Valkey password for NetBox from OnePassword using ExternalSecret.Fleet Directory Integration:
kueyen
cluster.