cluster-api-provider-nest
By kubernetes-sigs
cloud_metadata_extractor
Cloud metadata extraction tools and scripts (by opsdisk)
cluster-api-provider-nest | cloud_metadata_extractor | |
---|---|---|
1 | 1 | |
- | 32 | |
- | - | |
- | 0.0 | |
- | 12 months ago | |
Python | ||
- | - |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
cluster-api-provider-nest
Posts with mentions or reviews of cluster-api-provider-nest.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-11-27.
-
Amazon EC2 Enhances Defense in Depth with Default IMDSv2
Kubernetes has a lot of limitations from a multi tenancy perspective.
It's functional, but I think it's not as polished as the rest of Kubernetes which is why Kubernetes has a multi tenancy SIG that spawned the hierarchical namespace controller (https://github.com/kubernetes-sigs/hierarchical-namespaces) and virtual clusters (https://github.com/kubernetes-sigs/cluster-api-provider-nest...)
cloud_metadata_extractor
Posts with mentions or reviews of cloud_metadata_extractor.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-11-27.
-
Amazon EC2 Enhances Defense in Depth with Default IMDSv2
If anyone is curious on how this can be abused, here's my "There's no place like 169.254.169.254 - (Ab)using cloud metadata URLs" slides [1] and talk [2] from 2019.
tl;dr - misconfigured reverse proxies allowed cloud metadata URL access across the bigger cloud providers.
[1] https://github.com/opsdisk/cloud_metadata_extractor/blob/mas...
[2] https://www.youtube.com/watch?v=vxReTpBCmh8