Skip to content
Cloudbricks.dev logo

Contact

How to reach cloudbricks.dev with a correction, a question, or a suggestion about an article.

Kishore 2 min read

I read every message about the site, especially corrections. If something in an article is wrong, out of date, or does not work in your environment, I want to know.

Where to reach me

The site does not run a contact form or a mailing list. The reliable channels are:

  • GitHub — open an issue on the repository for the project, or use the contact details on my profile.
  • YouTube — comment on the video that accompanies an article.

For a correction, a GitHub issue is best because it keeps the details in one place and makes it easy to link the fix back to the article.

What to include

To make a report actionable, please include:

  • The URL of the page
  • The version of the software you are using
  • What you expected to happen
  • What actually happened, including the exact error text
  • The relevant part of your configuration, with secrets removed

Please do not send passwords, private keys, or customer data. A redacted configuration is enough to reproduce most problems.

Corrections and updates

When a correction is confirmed, the article is updated and the change is noted where it is substantive. If a post is superseded by a newer version of the software, the post will say so rather than silently presenting old steps as current.

What I cannot help with

This is a personal blog, not a support desk. I cannot debug your production environment, review your architecture, or provide vendor support. Questions that are specific to a lab setup covered on the site are welcome; general consulting requests are not.

Response time

Messages are answered on a best-effort basis, usually within a week. A clear, reproducible report is much more likely to get a useful reply than a one-line “it doesn’t work.”

Privacy

The site does not collect contact details through a form. Anything you post on GitHub or YouTube is governed by those platforms. See the Privacy Policy for how the site itself handles data.