logs to populate the termination message if the user does not write to the
  termination message log file. The termination message file is now properly
  readable for end users and has a maximum size (4k bytes) to prevent abuse.
  Each pod may have up to 12k bytes of termination messages before the contents
  of each will be truncated.
* Do not delete pod objects until all its compute resource footprint has been
  reclaimed.

kaas.gg
khplay.nl

// Kapsi : https://kapsi.fi
// Submitted by Tomi Juntunen <******@****.***>
kapsi.fi

// Katholieke Universiteit Leuven: https://www.kuleuven.be
// Submitted by Abuse KU Leuven <abuse@kuleuven.be>
ezproxy.kuleuven.be
kuleuven.cloud

// Keyweb AG : https://www.keyweb.de
// Submitted by Martin Dannehl <******@****.***>
keymachine.de