@ru_devops - страница 1320 - Telegram web archive

Aleksey

Нет у меня все на вм

Tadeusz

ну у тебя сколько вм/нод с pg?

Aleksey

Докеры в этой инфре не дают плюсов. Только головную боль

Aleksey

ну у тебя сколько вм/нод с pg?

3.

Aleksey

Плюс две под хапрокси

Tadeusz

воот, etcd у тебя там же стоят рядом с pg ?

Aleksey

Нет. У меня консул и он отдельно

Tadeusz

блин, понял

Anonymous

Info будет жить. Поприветствуем!

Womchik

что-то у меня патрони кластер не стартует. обе ноды в uninitialized и ждут мастера

Tadeusz

у меня одна не стартует (первая), остальные ок и etcd и haproxy

Tadeusz

member 1bab629f01fa9065 is healthy: got healthy result from http://10.0.0.116:2379 member 8ecb6af518d241cc is healthy: got healthy result from http://10.0.0.114:2379 member b2e169fcb8a34028 is healthy: got healthy result from http://10.0.0.110:2379

Tadeusz

+---------+----------+------------+--------+---------+----+-----------+ | Cluster | Member | Host | Role | State | TL | Lag in MB | +---------+----------+------------+--------+---------+----+-----------+ | patroni | patroni2 | 10.0.0.104 | | running | 10 | 0 | | patroni | patroni3 | 10.0.0.106 | Leader | running | 10 | 0 | +---------+----------+------------+--------+---------+----+-----------+

Anonymous

ㅤ будет жить. Поприветствуем!

Combot

combot.org/c/-1001057069601

Andrey

Так, коллеги, а чего все сидим и молчим-то? 🙂 Тут Rancher анонсировали самостоятельный kubernetes-дистрибутив. 🆕 Посмотреть и скачать можно здесь: https://k3os.io/ ℹ️ Анонс в блоге: https://rancher.com/blog/2019/announcing-k3os-kubernetes-operating-system/ #kubernetes #rancher #linux

Andrey

Что думаете?

Niko

недостаточно было ранчерОС

🏳️ Phil

Опс, не успел

Danila

спасибо Фил

Danila

а

Andrey

Что вы думаете о куберос?

Tadeusz

а что с этим можно сделать?) CRITICAL: system ID mismatch, node patroni1 belongs to a different cluster

Tadeusz

ага, снес postgresql/data/* и рестартанул - все ок

Anonymous

Ivan Boyko будет жить. Поприветствуем!

Иван Бойко

Всем привет 😎

Tadeusz

В этом чятике

🏳️ Phil

Началось в колхозе утро On Thursday, April 25th, 2019, we discovered unauthorized access to a single Hub database storing a subset of non-financial user data. Upon discovery, we acted quickly to intervene and secure the site. We want to update you on what we've learned from our ongoing investigation, including which Hub accounts are impacted, and what actions users should take. Here is what we’ve learned: During a brief period of unauthorized access to a Docker Hub database, sensitive data from approximately 190,000 accounts may have been exposed (less than 5% of Hub users). Data includes usernames and hashed passwords for a small percentage of these users, as well as Github and Bitbucket tokens for Docker autobuilds. Actions to Take: We are asking users to change their password on Docker Hub and any other accounts that shared this password. For users with autobuilds that may have been impacted, we have revoked GitHub tokens and access keys, and ask that you reconnect to your repositories and check security logs to see if any unexpected actions have taken place. You may view security actions on your GitHub or BitBucket accounts to see if any unexpected access has occurred over the past 24 hours -see https://help.github.com/en/articles/reviewing-your-security-log and https://bitbucket.org/blog/new-audit-logs-give-you-the-who-what-when-and-where This may affect your ongoing builds from our Automated build service. You may need to unlink and then relink your Github and Bitbucket source provider as described in https://docs.docker.com/docker-hub/builds/link-source/ We are enhancing our overall security processes and reviewing our policies. Additional monitoring tools are now in place. Our investigation is still ongoing, and we will share more information as it becomes available. Thank you, Kent