Draft
Conversation
✅ Deploy Preview for metal-stack-io ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Gerrit91
reviewed
Feb 23, 2026
| | VXLAN | Switches, Firewalls | Encapsulate Layer 2 frames in Layer 3 packets for network virtualization. | | ||
| | EVPN | Switches, Firewalls | Overlay network technology for scalable and flexible network architectures. | | ||
| | VPN | Firewalls | Management access [without open SSH ports](../../../contributing/04-Proposals/MEP9/README.md). | | ||
| | VPN | Firewalls | Management access [without open SSH ports](..//community/MEP-9-no-open-ports-to-the-data-center). | |
Contributor
There was a problem hiding this comment.
Suggested change
| | VPN | Firewalls | Management access [without open SSH ports](..//community/MEP-9-no-open-ports-to-the-data-center). | | |
| | VPN | Firewalls | Management access [without open SSH ports](/community/MEP-9-no-open-ports-to-the-data-center). | |
| @@ -15,7 +15,7 @@ The minimal need to know principle is a security concept that restricts access t | |||
| ### RBAC | |||
|
|
|||
| :::info | |||
| As of now metal-stack does not implement fine-grained Role-Based Access Control (RBAC) within the `metal-api` but this is worked on in [MEP-4](../../../contributing/01-Proposals/MEP4/README.md). | |||
| As of now metal-stack does not implement fine-grained Role-Based Access Control (RBAC) within the `metal-api` but this is worked on in [MEP-4](..//community/MEP-4-multi-tenancy-for-the-metal-api). | |||
Contributor
There was a problem hiding this comment.
Suggested change
| As of now metal-stack does not implement fine-grained Role-Based Access Control (RBAC) within the `metal-api` but this is worked on in [MEP-4](..//community/MEP-4-multi-tenancy-for-the-metal-api). | |
| As of now metal-stack does not implement fine-grained Role-Based Access Control (RBAC) within the `metal-api` but this is worked on in [MEP-4](/community/MEP-4-multi-tenancy-for-the-metal-api). |
| @@ -116,7 +116,7 @@ Please note that every [networking setup](../../05-Concepts/03-Network/01-theory | |||
| | VLAN | Switches, Firewalls | Layer 2 traffic segmentation. | | |||
| | VXLAN | Switches, Firewalls | Encapsulate Layer 2 frames in Layer 3 packets for network virtualization. | | |||
| | EVPN | Switches, Firewalls | Overlay network technology for scalable and flexible network architectures. | | |||
| | VPN | Firewalls | Management access [without open SSH ports](../../../contributing/01-Proposals/MEP9/README.md). | | |||
| | VPN | Firewalls | Management access [without open SSH ports](..//community/MEP-9-no-open-ports-to-the-data-center). | | |||
Contributor
There was a problem hiding this comment.
Suggested change
| | VPN | Firewalls | Management access [without open SSH ports](..//community/MEP-9-no-open-ports-to-the-data-center). | | |
| | VPN | Firewalls | Management access [without open SSH ports](/community/MEP-9-no-open-ports-to-the-data-center). | |
| @@ -15,7 +15,7 @@ The minimal need to know principle is a security concept that restricts access t | |||
| ### RBAC | |||
|
|
|||
| :::info | |||
| As of now metal-stack does not implement fine-grained Role-Based Access Control (RBAC) within the `metal-api` but this is worked on in [MEP-4](../../../contributing/01-Proposals/MEP4/README.md). | |||
| As of now metal-stack does not implement fine-grained Role-Based Access Control (RBAC) within the `metal-api` but this is worked on in [MEP-4](..//community/MEP-4-multi-tenancy-for-the-metal-api). | |||
Contributor
There was a problem hiding this comment.
Suggested change
| As of now metal-stack does not implement fine-grained Role-Based Access Control (RBAC) within the `metal-api` but this is worked on in [MEP-4](..//community/MEP-4-multi-tenancy-for-the-metal-api). | |
| As of now metal-stack does not implement fine-grained Role-Based Access Control (RBAC) within the `metal-api` but this is worked on in [MEP-4](/community/MEP-4-multi-tenancy-for-the-metal-api). |
| @@ -116,7 +116,7 @@ Please note that every [networking setup](../../05-Concepts/03-Network/01-theory | |||
| | VLAN | Switches, Firewalls | Layer 2 traffic segmentation. | | |||
| | VXLAN | Switches, Firewalls | Encapsulate Layer 2 frames in Layer 3 packets for network virtualization. | | |||
| | EVPN | Switches, Firewalls | Overlay network technology for scalable and flexible network architectures. | | |||
| | VPN | Firewalls | Management access [without open SSH ports](../../../contributing/01-Proposals/MEP9/README.md). | | |||
| | VPN | Firewalls | Management access [without open SSH ports](..//community/MEP-9-no-open-ports-to-the-data-center). | | |||
Contributor
There was a problem hiding this comment.
Suggested change
| | VPN | Firewalls | Management access [without open SSH ports](..//community/MEP-9-no-open-ports-to-the-data-center). | | |
| | VPN | Firewalls | Management access [without open SSH ports](/community/MEP-9-no-open-ports-to-the-data-center). | |
| @@ -116,7 +116,7 @@ Please note that every [networking setup](../../05-Concepts/03-Network/01-theory | |||
| | VLAN | Switches, Firewalls | Layer 2 traffic segmentation. | | |||
| | VXLAN | Switches, Firewalls | Encapsulate Layer 2 frames in Layer 3 packets for network virtualization. | | |||
| | EVPN | Switches, Firewalls | Overlay network technology for scalable and flexible network architectures. | | |||
| | VPN | Firewalls | Management access [without open SSH ports](../../../contributing/01-Proposals/MEP9/README.md). | | |||
| | VPN | Firewalls | Management access [without open SSH ports](..//community/MEP-9-no-open-ports-to-the-data-center). | | |||
Contributor
There was a problem hiding this comment.
Suggested change
| | VPN | Firewalls | Management access [without open SSH ports](..//community/MEP-9-no-open-ports-to-the-data-center). | | |
| | VPN | Firewalls | Management access [without open SSH ports](/community/MEP-9-no-open-ports-to-the-data-center). | |
| @@ -15,7 +15,7 @@ The minimal need to know principle is a security concept that restricts access t | |||
| ### RBAC | |||
|
|
|||
| :::info | |||
| As of now metal-stack does not implement fine-grained Role-Based Access Control (RBAC) within the `metal-api` but this is worked on in [MEP-4](../../../contributing/01-Proposals/MEP4/README.md). | |||
| As of now metal-stack does not implement fine-grained Role-Based Access Control (RBAC) within the `metal-api` but this is worked on in [MEP-4](..//community/MEP-4-multi-tenancy-for-the-metal-api). | |||
Contributor
There was a problem hiding this comment.
Suggested change
| As of now metal-stack does not implement fine-grained Role-Based Access Control (RBAC) within the `metal-api` but this is worked on in [MEP-4](..//community/MEP-4-multi-tenancy-for-the-metal-api). | |
| As of now metal-stack does not implement fine-grained Role-Based Access Control (RBAC) within the `metal-api` but this is worked on in [MEP-4](/community/MEP-4-multi-tenancy-for-the-metal-api). |
| @@ -116,7 +116,7 @@ Please note that every [networking setup](../../05-Concepts/03-Network/01-theory | |||
| | VLAN | Switches, Firewalls | Layer 2 traffic segmentation. | | |||
| | VXLAN | Switches, Firewalls | Encapsulate Layer 2 frames in Layer 3 packets for network virtualization. | | |||
| | EVPN | Switches, Firewalls | Overlay network technology for scalable and flexible network architectures. | | |||
| | VPN | Firewalls | Management access [without open SSH ports](../../../contributing/01-Proposals/MEP9/README.md). | | |||
| | VPN | Firewalls | Management access [without open SSH ports](..//community/MEP-9-no-open-ports-to-the-data-center). | | |||
Contributor
There was a problem hiding this comment.
Suggested change
| | VPN | Firewalls | Management access [without open SSH ports](..//community/MEP-9-no-open-ports-to-the-data-center). | | |
| | VPN | Firewalls | Management access [without open SSH ports](/community/MEP-9-no-open-ports-to-the-data-center). | |
| @@ -15,7 +15,7 @@ The minimal need to know principle is a security concept that restricts access t | |||
| ### RBAC | |||
|
|
|||
| :::info | |||
| As of now metal-stack does not implement fine-grained Role-Based Access Control (RBAC) within the `metal-api` but this is worked on in [MEP-4](../../../contributing/01-Proposals/MEP4/README.md). | |||
| As of now metal-stack does not implement fine-grained Role-Based Access Control (RBAC) within the `metal-api` but this is worked on in [MEP-4](..//community/MEP-4-multi-tenancy-for-the-metal-api). | |||
Contributor
There was a problem hiding this comment.
Suggested change
| As of now metal-stack does not implement fine-grained Role-Based Access Control (RBAC) within the `metal-api` but this is worked on in [MEP-4](..//community/MEP-4-multi-tenancy-for-the-metal-api). | |
| As of now metal-stack does not implement fine-grained Role-Based Access Control (RBAC) within the `metal-api` but this is worked on in [MEP-4](/community/MEP-4-multi-tenancy-for-the-metal-api). |
| @@ -116,7 +116,7 @@ Please note that every [networking setup](../../05-Concepts/03-Network/01-theory | |||
| | VLAN | Switches, Firewalls | Layer 2 traffic segmentation. | | |||
| | VXLAN | Switches, Firewalls | Encapsulate Layer 2 frames in Layer 3 packets for network virtualization. | | |||
| | EVPN | Switches, Firewalls | Overlay network technology for scalable and flexible network architectures. | | |||
| | VPN | Firewalls | Management access [without open SSH ports](../../../contributing/01-Proposals/MEP9/README.md). | | |||
| | VPN | Firewalls | Management access [without open SSH ports](..//community/MEP-9-no-open-ports-to-the-data-center). | | |||
Contributor
There was a problem hiding this comment.
Suggested change
| | VPN | Firewalls | Management access [without open SSH ports](..//community/MEP-9-no-open-ports-to-the-data-center). | | |
| | VPN | Firewalls | Management access [without open SSH ports](/community/MEP-9-no-open-ports-to-the-data-center). | |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Description
In the past we had a few issues with the contributing / community docs being versioned and therefore outdated. We want them as up to date as possible.
This also lead to hard to understand issues and confusion like this: #205 (comment)
AI Transparency
I used duck.ai with ChatGPT 5 to brainstorm possible solutions as I could not find fitting scenarios to do unversioned docs with all the docs features on the official docusaurus documentation.
The code changes themselves are all made by humans.