Skip to content
PAASBOXPAASBOXPAASBOX

Support

PaaSbox is one person, and I read every message. Replies are best effort, usually within one business day. There is no ticket system, no phone line and no SLA.

  • Contact: email support@mitjamartini.com. Feedback goes to the same address. For a security issue, read security reports first.
  • The open components: the docs describe each one and its status. Apart from the node images, their repositories are not public yet; once they are, bug reports go there as issues. Until then, write to the address above with the component in the subject.
  • PaaSbox Clusters: it ran end to end in a lab but cannot be booked yet, so there is no customer cluster to support. Questions about how it works go to the same address; how it works is in the docs.
  • A setup, consulting or a course: call me. PaaSbox does not offer Gardener clusters; see Gardener on Hetzner for the open components.
  • Training: write to me with the course you mean. See training.
  • Privacy and your data: see the privacy policy. To exercise a right it names, write to the address above.
  • Before you write: troubleshooting and the FAQ may already have the answer, and operated in the open says what is built today and what is not.

What to include

Section titled “What to include”

A message I can act on without a round trip says:

  • what you were trying to do, what happened instead, and what you expected;
  • which page, component or command it is about, with its version or release if it has one;
  • the exact command and its full output, or the error as text rather than a screenshot;
  • the names of what is involved: the cluster, the app, the server type and the Hetzner location.

Never put a Hetzner API token, a kubeconfig, an S3 key or a password into a message. If output contains one, replace it with <redacted> before you send it.

Security reports

Section titled “Security reports”

If you believe you have found a security issue in PaaSbox, this site or one of its components, email support@mitjamartini.com with “security” in the subject. The same address is in /.well-known/security.txt. Do not open a public issue, and do not test against systems that are not yours.

Say what you found, where, how to reproduce it, and what an attacker could do with it. A person reads it, not an autoresponder, and I answer in English or German.