Area(s)
area:k8s, area:system, area:container
What's missing?
k8s.*/container.filesystem.* and system.filesystem.* model the same concept two different ways:
| Concept |
k8s / container |
system |
| used |
*.filesystem.usage |
system.filesystem.usage with system.filesystem.state=used |
| free |
*.filesystem.available |
system.filesystem.usage with state=free |
| total |
*.filesystem.capacity |
system.filesystem.limit (#1633) |
The k8s side uses separate metric names; system uses one metric + a state attribute + a limit metric.
Describe the solution you'd like
A SIG decision, ideally before promoting *.filesystem.* to RC. I think the best path forward is to reconcile the k8s metrics to match the filesystem metrics, but this would be a breaking change. The other option is to accept the difference.
Tip
React with 👍 to help prioritize this issue. Please use comments to provide useful context, avoiding +1 or me too, to help us triage it. Learn more here.
Area(s)
area:k8s, area:system, area:container
What's missing?
k8s.*/container.filesystem.*andsystem.filesystem.*model the same concept two different ways:*.filesystem.usagesystem.filesystem.usagewithsystem.filesystem.state=used*.filesystem.availablesystem.filesystem.usagewithstate=free*.filesystem.capacitysystem.filesystem.limit(#1633)The k8s side uses separate metric names; system uses one metric + a
stateattribute + alimitmetric.system.filesystem.*attributes as release candidate #3826Describe the solution you'd like
A SIG decision, ideally before promoting
*.filesystem.*to RC. I think the best path forward is to reconcile the k8s metrics to match the filesystem metrics, but this would be a breaking change. The other option is to accept the difference.Tip
React with 👍 to help prioritize this issue. Please use comments to provide useful context, avoiding
+1orme too, to help us triage it. Learn more here.