# social-media

## Interesting Twitter Accounts

*Twitter is quick, it’s easy to communicate on, and is a very valuable social channel for a brand or business if you use it to its full potential, By following these news aggregators, rolling news channels, and companies, you can get the inside scoop of a story long before it hits the mainstream news outlets.*

### Community & events

* [K8sContributors](https://twitter.com/K8sContributors)
* [Kube Events](https://twitter.com/K8sEvents)
* [Kube Con](https://twitter.com/kubecon_)
* [Kubernetes](https://twitter.com/kubernetesio)
* [KubeWeekly](https://twitter.com/kubeweekly)

### Companies

* [Engine Yard](https://twitter.com/engineyard)
* [Google Cloud Platform](https://twitter.com/googlecloud)
* [Kubermatic](https://twitter.com/Kubermatic/)
* [Loft Labs](https://twitter.com/loft_sh)
* [Palark](https://twitter.com/palark_com)
* [Sysdig](https://twitter.com/sysdig)

### Other

* [LearnKube](https://x.com/learnk8s)
* [Kube Architect](https://x.com/k8sarchitect)
* [Kube Builders](https://x.com/kubebuilders)
* [Kubesploit](https://x.com/kubesploit)

## Other Social Media Accounts

### Telegram

* [Kubernative](https://t.me/kubernative)


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://ramitsurana.gitbook.io/awesome-kubernetes/docs/extras/social-media.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.