k8s-triage-robot
commented
2 years ago The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.
This bot triages issues and PRs according to the following rules:
- After 90d of inactivity,
lifecycle/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas applied, the issue is closed
You can:
- Mark this issue or PR as fresh with
/remove-lifecycle stale - Mark this issue or PR as rotten with
/lifecycle rotten - Close this issue or PR with
/close - Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
joaocc
steache
SebSa
What would you like to be added: Make the content of txt-owner-id records based on a hash of the current information. It could be a hash of each individual data element, or an be a hash of combined info of all records.
Why is this needed: txt-owner-id records currently expose a set of information in cleartext (namespace, internal service name, ...) which can provide insights into the internals of an organization's deployment. Hashing the information would still allow for comparison when the elements are known, but would prevent the public in general from learning about the namespaces, services and other elements of the internal infrastructure