Init security tracker domain and monitoring #520
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Depends on #519 |
mweinelt
reviewed
Dec 11, 2024
Erethon
force-pushed
the
init-security-tracker
branch
from
2a5040b to
1421d44
Compare
mweinelt
approved these changes
Dec 12, 2024
|
DNS changes applied. |
|
Thank you both! I've configured the host to use that domain now, so feel free to apply the prometheus changes whenever you have the time. |
|
Also applied. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 is a PR to setup the Nixpkgs Security Tracker on the nixos.org domain.
On the surface this PR is very simple as it only:
tracker.security.nixos.orgthat points to a Hetzner Cloud VM host (188.245.41.195)The VM is part of the
nixpkgs-security-trackerHetzner Cloud project which @zimbatm gave me access to a while ago.The configuration of this host will eventually be here, but please note that this draft PR contains the important bits for now and isn't merged yet as it depends on having a .nixos.org domain for the host.
I've copy-pasted
ssh-keys.nixas it exists in commit 0d476c9, so everyone from the (current) infra team has access to the host as root.I think if this is merged and applied as is, we'll get an alert for the domain. If we don't mind that, this is the simplest option to move forward as I'll be able to generate a certificate for
tracker.security.nixos.orgthen and the alert will go away. Otherwise, we can first only apply the Terraform DNS change and later the Prometheus change to avoid the alert.