Ecoer Logo
VOTING POWER100.00%
DOWNVOTE POWER100.00%
RESOURCE CREDITS100.00%
REPUTATION PROGRESS0.00%
Net Worth
0.007USD
STEEM
0.000STEEM
SBD
0.000SBD
Effective Power
5.001SP
├── Own SP
0.125SP
└── Incoming Deleg
+4.876SP

Detailed Balance

STEEM
balance
0.000STEEM
market_balance
0.000STEEM
savings_balance
0.000STEEM
reward_steem_balance
0.000STEEM
STEEM POWER
Own SP
0.125SP
Delegated Out
0.000SP
Delegation In
4.876SP
Effective Power
5.001SP
Reward SP (pending)
0.000SP
SBD
sbd_balance
0.000SBD
sbd_conversions
0.000SBD
sbd_market_balance
0.000SBD
savings_sbd_balance
0.000SBD
reward_sbd_balance
0.000SBD
{
  "balance": "0.000 STEEM",
  "savings_balance": "0.000 STEEM",
  "reward_steem_balance": "0.000 STEEM",
  "vesting_shares": "203.956016 VESTS",
  "delegated_vesting_shares": "0.000000 VESTS",
  "received_vesting_shares": "7939.703790 VESTS",
  "sbd_balance": "0.000 SBD",
  "savings_sbd_balance": "0.000 SBD",
  "reward_sbd_balance": "0.000 SBD",
  "conversions": []
}

Account Info

nameosoulmate
id905031
rank417,299
reputation0
created2018-04-02T09:26:24
recovery_accountsteem
proxyNone
post_count1
comment_count0
lifetime_vote_count0
witnesses_voted_for0
last_post2018-04-02T09:37:21
last_root_post2018-04-02T09:37:21
last_vote_time1970-01-01T00:00:00
proxied_vsf_votes0, 0, 0, 0
can_vote1
voting_power0
delayed_votes0
balance0.000 STEEM
savings_balance0.000 STEEM
sbd_balance0.000 SBD
savings_sbd_balance0.000 SBD
vesting_shares203.956016 VESTS
delegated_vesting_shares0.000000 VESTS
received_vesting_shares7939.703790 VESTS
reward_vesting_balance0.000000 VESTS
vesting_balance0.000 STEEM
vesting_withdraw_rate0.000000 VESTS
next_vesting_withdrawal1969-12-31T23:59:59
withdrawn0
to_withdraw0
withdraw_routes0
savings_withdraw_requests0
last_account_recovery1970-01-01T00:00:00
reset_accountnull
last_owner_update1970-01-01T00:00:00
last_account_update1970-01-01T00:00:00
minedNo
sbd_seconds0
sbd_last_interest_payment1970-01-01T00:00:00
savings_sbd_last_interest_payment1970-01-01T00:00:00
{
  "id": 905031,
  "name": "osoulmate",
  "owner": {
    "weight_threshold": 1,
    "account_auths": [],
    "key_auths": [
      [
        "STM52gx7qqxR1rtvRTdAqEZG7PP6mSLGTgzhyyrfyj2qJ24SCmYGp",
        1
      ]
    ]
  },
  "active": {
    "weight_threshold": 1,
    "account_auths": [],
    "key_auths": [
      [
        "STM88ySTnPnN1uHsgosxdq3R5NB9sZzzb5heemRVmuiLRpuafRw7D",
        1
      ]
    ]
  },
  "posting": {
    "weight_threshold": 1,
    "account_auths": [],
    "key_auths": [
      [
        "STM6wh28XJw9ZQhFwUfDQ7nrK4zad4XrBbkT4Ebn9mB9eg43rEBE3",
        1
      ]
    ]
  },
  "memo_key": "STM8Wvbh7ToYAnPQDt4CKiwExgJ7JV883ovHnHHapkga9DmTinyNK",
  "json_metadata": "{}",
  "posting_json_metadata": "",
  "proxy": "",
  "last_owner_update": "1970-01-01T00:00:00",
  "last_account_update": "1970-01-01T00:00:00",
  "created": "2018-04-02T09:26:24",
  "mined": false,
  "recovery_account": "steem",
  "last_account_recovery": "1970-01-01T00:00:00",
  "reset_account": "null",
  "comment_count": 0,
  "lifetime_vote_count": 0,
  "post_count": 1,
  "can_vote": true,
  "voting_manabar": {
    "current_mana": "8143659806",
    "last_update_time": 1779079785
  },
  "downvote_manabar": {
    "current_mana": 2035914951,
    "last_update_time": 1779079785
  },
  "voting_power": 0,
  "balance": "0.000 STEEM",
  "savings_balance": "0.000 STEEM",
  "sbd_balance": "0.000 SBD",
  "sbd_seconds": "0",
  "sbd_seconds_last_update": "1970-01-01T00:00:00",
  "sbd_last_interest_payment": "1970-01-01T00:00:00",
  "savings_sbd_balance": "0.000 SBD",
  "savings_sbd_seconds": "0",
  "savings_sbd_seconds_last_update": "1970-01-01T00:00:00",
  "savings_sbd_last_interest_payment": "1970-01-01T00:00:00",
  "savings_withdraw_requests": 0,
  "reward_sbd_balance": "0.000 SBD",
  "reward_steem_balance": "0.000 STEEM",
  "reward_vesting_balance": "0.000000 VESTS",
  "reward_vesting_steem": "0.000 STEEM",
  "vesting_shares": "203.956016 VESTS",
  "delegated_vesting_shares": "0.000000 VESTS",
  "received_vesting_shares": "7939.703790 VESTS",
  "vesting_withdraw_rate": "0.000000 VESTS",
  "next_vesting_withdrawal": "1969-12-31T23:59:59",
  "withdrawn": 0,
  "to_withdraw": 0,
  "withdraw_routes": 0,
  "curation_rewards": 0,
  "posting_rewards": 0,
  "proxied_vsf_votes": [
    0,
    0,
    0,
    0
  ],
  "witnesses_voted_for": 0,
  "last_post": "2018-04-02T09:37:21",
  "last_root_post": "2018-04-02T09:37:21",
  "last_vote_time": "1970-01-01T00:00:00",
  "post_bandwidth": 0,
  "pending_claimed_accounts": 0,
  "vesting_balance": "0.000 STEEM",
  "reputation": 0,
  "transfer_history": [],
  "market_history": [],
  "post_history": [],
  "vote_history": [],
  "other_history": [],
  "witness_votes": [],
  "tags_usage": [],
  "guest_bloggers": [],
  "rank": 417299
}

Withdraw Routes

IncomingOutgoing
Empty
Empty
{
  "incoming": [],
  "outgoing": []
}
From Date
To Date
steemdelegated 4.876 SP to @osoulmate
2026/05/18 04:49:45
delegatorsteem
delegateeosoulmate
vesting shares7939.703790 VESTS
Transaction InfoBlock #106148913/Trx c5c50b0f3fcf03730549d9a5d241e9a214ba2b12
View Raw JSON Data
{
  "trx_id": "c5c50b0f3fcf03730549d9a5d241e9a214ba2b12",
  "block": 106148913,
  "trx_in_block": 0,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2026-05-18T04:49:45",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "osoulmate",
      "vesting_shares": "7939.703790 VESTS"
    }
  ]
}
steemdelegated 3.210 SP to @osoulmate
2026/05/12 22:25:15
delegatorsteem
delegateeosoulmate
vesting shares5227.493385 VESTS
Transaction InfoBlock #105997957/Trx 80a9a9ac83c6cf18b58febe662b849938fed31c5
View Raw JSON Data
{
  "trx_id": "80a9a9ac83c6cf18b58febe662b849938fed31c5",
  "block": 105997957,
  "trx_in_block": 1,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2026-05-12T22:25:15",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "osoulmate",
      "vesting_shares": "5227.493385 VESTS"
    }
  ]
}
steemdelegated 4.883 SP to @osoulmate
2026/04/26 04:03:39
delegatorsteem
delegateeosoulmate
vesting shares7952.219546 VESTS
Transaction InfoBlock #105516438/Trx fd527f0ebbd778d22e49ade6d72c0d27ad17732f
View Raw JSON Data
{
  "trx_id": "fd527f0ebbd778d22e49ade6d72c0d27ad17732f",
  "block": 105516438,
  "trx_in_block": 2,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2026-04-26T04:03:39",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "osoulmate",
      "vesting_shares": "7952.219546 VESTS"
    }
  ]
}
steemdelegated 3.236 SP to @osoulmate
2026/01/23 20:05:57
delegatorsteem
delegateeosoulmate
vesting shares5269.040204 VESTS
Transaction InfoBlock #102866544/Trx 4dce4c952e85db55d764687d37d83dff3e347be3
View Raw JSON Data
{
  "trx_id": "4dce4c952e85db55d764687d37d83dff3e347be3",
  "block": 102866544,
  "trx_in_block": 1,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2026-01-23T20:05:57",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "osoulmate",
      "vesting_shares": "5269.040204 VESTS"
    }
  ]
}
steemdelegated 3.336 SP to @osoulmate
2024/12/17 15:17:18
delegatorsteem
delegateeosoulmate
vesting shares5433.259401 VESTS
Transaction InfoBlock #91312785/Trx b468a1dad77f397524713f545627ad1bc81f5ca1
View Raw JSON Data
{
  "trx_id": "b468a1dad77f397524713f545627ad1bc81f5ca1",
  "block": 91312785,
  "trx_in_block": 4,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2024-12-17T15:17:18",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "osoulmate",
      "vesting_shares": "5433.259401 VESTS"
    }
  ]
}
steemdelegated 3.440 SP to @osoulmate
2023/11/14 06:58:33
delegatorsteem
delegateeosoulmate
vesting shares5602.392933 VESTS
Transaction InfoBlock #79866942/Trx c0a16f64757114146f9eca66e3068f7d06ac352d
View Raw JSON Data
{
  "trx_id": "c0a16f64757114146f9eca66e3068f7d06ac352d",
  "block": 79866942,
  "trx_in_block": 0,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2023-11-14T06:58:33",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "osoulmate",
      "vesting_shares": "5602.392933 VESTS"
    }
  ]
}
steemdelegated 5.244 SP to @osoulmate
2023/09/22 08:39:36
delegatorsteem
delegateeosoulmate
vesting shares8539.301719 VESTS
Transaction InfoBlock #78360795/Trx 3c4aa943dca735eca6faf91bc41e76f8d239da6e
View Raw JSON Data
{
  "trx_id": "3c4aa943dca735eca6faf91bc41e76f8d239da6e",
  "block": 78360795,
  "trx_in_block": 6,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2023-09-22T08:39:36",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "osoulmate",
      "vesting_shares": "8539.301719 VESTS"
    }
  ]
}
steemdelegated 5.380 SP to @osoulmate
2022/11/03 16:20:51
delegatorsteem
delegateeosoulmate
vesting shares8761.353157 VESTS
Transaction InfoBlock #69118809/Trx 2a9a47213e82e3694540086ef991589de151cfcb
View Raw JSON Data
{
  "trx_id": "2a9a47213e82e3694540086ef991589de151cfcb",
  "block": 69118809,
  "trx_in_block": 3,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2022-11-03T16:20:51",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "osoulmate",
      "vesting_shares": "8761.353157 VESTS"
    }
  ]
}
steemdelegated 5.515 SP to @osoulmate
2022/01/17 21:41:27
delegatorsteem
delegateeosoulmate
vesting shares8981.460758 VESTS
Transaction InfoBlock #60822228/Trx 21587c484e2ea60de7f24eeb6d0d049bc5e0af2c
View Raw JSON Data
{
  "trx_id": "21587c484e2ea60de7f24eeb6d0d049bc5e0af2c",
  "block": 60822228,
  "trx_in_block": 4,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2022-01-17T21:41:27",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "osoulmate",
      "vesting_shares": "8981.460758 VESTS"
    }
  ]
}
steemdelegated 5.628 SP to @osoulmate
2021/06/14 04:56:03
delegatorsteem
delegateeosoulmate
vesting shares9165.655046 VESTS
Transaction InfoBlock #54612631/Trx 175bab12ab5fcac331ce64792f9022015ee02579
View Raw JSON Data
{
  "trx_id": "175bab12ab5fcac331ce64792f9022015ee02579",
  "block": 54612631,
  "trx_in_block": 6,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2021-06-14T04:56:03",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "osoulmate",
      "vesting_shares": "9165.655046 VESTS"
    }
  ]
}
steemdelegated 5.744 SP to @osoulmate
2020/12/11 15:09:39
delegatorsteem
delegateeosoulmate
vesting shares9353.077020 VESTS
Transaction InfoBlock #49359937/Trx ceef57cfb760484b699c27234dabf78df6f07319
View Raw JSON Data
{
  "trx_id": "ceef57cfb760484b699c27234dabf78df6f07319",
  "block": 49359937,
  "trx_in_block": 7,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2020-12-11T15:09:39",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "osoulmate",
      "vesting_shares": "9353.077020 VESTS"
    }
  ]
}
steemdelegated 1.174 SP to @osoulmate
2020/12/06 08:45:54
delegatorsteem
delegateeosoulmate
vesting shares1912.543513 VESTS
Transaction InfoBlock #49211473/Trx 72cfbc8fff2f18062b61be6471bf63af06b0374a
View Raw JSON Data
{
  "trx_id": "72cfbc8fff2f18062b61be6471bf63af06b0374a",
  "block": 49211473,
  "trx_in_block": 2,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2020-12-06T08:45:54",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "osoulmate",
      "vesting_shares": "1912.543513 VESTS"
    }
  ]
}
steemdelegated 5.747 SP to @osoulmate
2020/12/05 18:47:27
delegatorsteem
delegateeosoulmate
vesting shares9359.284874 VESTS
Transaction InfoBlock #49195019/Trx 75a711a86dd852be6805a4ac46913cad25602940
View Raw JSON Data
{
  "trx_id": "75a711a86dd852be6805a4ac46913cad25602940",
  "block": 49195019,
  "trx_in_block": 1,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2020-12-05T18:47:27",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "osoulmate",
      "vesting_shares": "9359.284874 VESTS"
    }
  ]
}
steemdelegated 1.179 SP to @osoulmate
2020/11/03 00:00:30
delegatorsteem
delegateeosoulmate
vesting shares1920.017158 VESTS
Transaction InfoBlock #48267655/Trx 5275dfb9a85121bf3b01157514533733145a42f6
View Raw JSON Data
{
  "trx_id": "5275dfb9a85121bf3b01157514533733145a42f6",
  "block": 48267655,
  "trx_in_block": 5,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2020-11-03T00:00:30",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "osoulmate",
      "vesting_shares": "1920.017158 VESTS"
    }
  ]
}
steemdelegated 5.872 SP to @osoulmate
2020/05/09 09:47:18
delegatorsteem
delegateeosoulmate
vesting shares9562.090233 VESTS
Transaction InfoBlock #43221779/Trx ba0d491e2225d53e6809ab00805eca83e33f5537
View Raw JSON Data
{
  "trx_id": "ba0d491e2225d53e6809ab00805eca83e33f5537",
  "block": 43221779,
  "trx_in_block": 7,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2020-05-09T09:47:18",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "osoulmate",
      "vesting_shares": "9562.090233 VESTS"
    }
  ]
}
steemdelegated 1.199 SP to @osoulmate
2020/05/08 14:00:03
delegatorsteem
delegateeosoulmate
vesting shares1953.311140 VESTS
Transaction InfoBlock #43198592/Trx 8631d872e073097c3add2fc9993c70dbd7ba3463
View Raw JSON Data
{
  "trx_id": "8631d872e073097c3add2fc9993c70dbd7ba3463",
  "block": 43198592,
  "trx_in_block": 9,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2020-05-08T14:00:03",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "osoulmate",
      "vesting_shares": "1953.311140 VESTS"
    }
  ]
}
steemdelegated 5.985 SP to @osoulmate
2019/06/23 13:53:15
delegatorsteem
delegateeosoulmate
vesting shares9746.328948 VESTS
Transaction InfoBlock #34052451/Trx b9448c234b533f3c99641efcf0878609bf04c66f
View Raw JSON Data
{
  "trx_id": "b9448c234b533f3c99641efcf0878609bf04c66f",
  "block": 34052451,
  "trx_in_block": 12,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2019-06-23T13:53:15",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "osoulmate",
      "vesting_shares": "9746.328948 VESTS"
    }
  ]
}
2019/04/02 10:52:12
parent authorosoulmate
parent permlinkkubernetes-v1-10-keepalived-ha
authorsteemitboard
permlinksteemitboard-notify-osoulmate-20190402t105211000z
title
bodyCongratulations @osoulmate! You received a personal award! <table><tr><td>https://steemitimages.com/70x70/http://steemitboard.com/@osoulmate/birthday1.png</td><td>Happy Birthday! - You are on the Steem blockchain for 1 year!</td></tr></table> <sub>_You can view [your badges on your Steem Board](https://steemitboard.com/@osoulmate) and compare to others on the [Steem Ranking](http://steemitboard.com/ranking/index.php?name=osoulmate)_</sub> ###### [Vote for @Steemitboard as a witness](https://v2.steemconnect.com/sign/account-witness-vote?witness=steemitboard&approve=1) to get one more award and increased upvotes!
json metadata{"image":["https://steemitboard.com/img/notify.png"]}
Transaction InfoBlock #31690890/Trx 0c7eef54a3b1dd620b2be697bfb6d54a6a999135
View Raw JSON Data
{
  "trx_id": "0c7eef54a3b1dd620b2be697bfb6d54a6a999135",
  "block": 31690890,
  "trx_in_block": 19,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2019-04-02T10:52:12",
  "op": [
    "comment",
    {
      "parent_author": "osoulmate",
      "parent_permlink": "kubernetes-v1-10-keepalived-ha",
      "author": "steemitboard",
      "permlink": "steemitboard-notify-osoulmate-20190402t105211000z",
      "title": "",
      "body": "Congratulations @osoulmate! You received a personal award!\n\n<table><tr><td>https://steemitimages.com/70x70/http://steemitboard.com/@osoulmate/birthday1.png</td><td>Happy Birthday! - You are on the Steem blockchain for 1 year!</td></tr></table>\n\n<sub>_You can view [your badges on your Steem Board](https://steemitboard.com/@osoulmate) and compare to others on the [Steem Ranking](http://steemitboard.com/ranking/index.php?name=osoulmate)_</sub>\n\n\n###### [Vote for @Steemitboard as a witness](https://v2.steemconnect.com/sign/account-witness-vote?witness=steemitboard&approve=1) to get one more award and increased upvotes!",
      "json_metadata": "{\"image\":[\"https://steemitboard.com/img/notify.png\"]}"
    }
  ]
}
steemdelegated 6.107 SP to @osoulmate
2018/07/02 11:52:21
delegatorsteem
delegateeosoulmate
vesting shares9945.389943 VESTS
Transaction InfoBlock #23832062/Trx 2b344242576a6880c2a4c85e28639ac87abcde96
View Raw JSON Data
{
  "trx_id": "2b344242576a6880c2a4c85e28639ac87abcde96",
  "block": 23832062,
  "trx_in_block": 22,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-07-02T11:52:21",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "osoulmate",
      "vesting_shares": "9945.389943 VESTS"
    }
  ]
}
steemdelegated 18.662 SP to @osoulmate
2018/04/02 11:38:51
delegatorsteem
delegateeosoulmate
vesting shares30389.310023 VESTS
Transaction InfoBlock #21213146/Trx 938707a4b98a715b4c9e847dce90218d55c7a720
View Raw JSON Data
{
  "trx_id": "938707a4b98a715b4c9e847dce90218d55c7a720",
  "block": 21213146,
  "trx_in_block": 33,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-04-02T11:38:51",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "osoulmate",
      "vesting_shares": "30389.310023 VESTS"
    }
  ]
}
2018/04/02 09:37:21
parent author
parent permlinkkubernetes
authorosoulmate
permlinkkubernetes-v1-10-keepalived-ha
titleKubernetes v1.10+Keepalived HA集群墙内部署实践
body导读:众所周知,K8S安装难点在于镜像下载。查询网上许多关于K8S安装部署的文章,作者要么是将镜像下载使用的工作交给了读者完成,要么是放在共享云盘中,由读者下载后导入使用。都知道,如果你不是该云盘提供商的会员,镜像下载速度堪比蜗牛。总之,三个字:”不方便“。基于最大化便利刚接触K8S的同行快速上手实践的目的,在参阅了众多同行关于K8S部署的文章,并经过反复实验验证后,将本人的实验成果在这里分享,希望可以帮助有需要的朋友。由于时间仓促,一些对本文撰写有价值的文章没有仔细考证作者和出处,在本文末尾的参阅文章中可能没有注明。如你发现本文中一些内容的原创属于你本人,请邮件联系本人处理。并在此感谢对本文创作产生帮助的作者。谢谢! 本文K8S集群高可用方案采用Keepalived。 实验环境: 1、3台centos 1611版本虚拟机,mini安装。Linux localhost 3.10.0-514.el7.x86_64 #1 SMP Tue Nov 22 16:42:41 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux 2、docker version Client: Version: 1.13.1 API version: 1.26 Package version: Go version: go1.8.3 Git commit: 774336d/1.13.1 Built: Wed Mar 7 17:06:16 2018 OS/Arch: linux/amd64 Server: Version: 1.13.1 API version: 1.26 (minimum version 1.12) Package version: Go version: go1.8.3 Git commit: 774336d/1.13.1 Built: Wed Mar 7 17:06:16 2018 OS/Arch: linux/amd64 Experimental: false 3、etcd Version: 3.1.13 4、kubeadm,kubelet,kubectl,kube-cni版本如下: -rw-r–r– 1 root root 18176678 Mar 30 00:08 5844c6be68e95a741f1ad403e5d4f6962044be060bc6df9614c2547fdbf91ae5-kubelet-1.10.0-0.x86_64.rpm -rw-r–r– 1 root root 17767206 Mar 30 00:07 8b0cb6654a2f6d014555c6c85148a5adc5918de937f608a30b0c0ae955d8abce-kubeadm-1.10.0-0.x86_64.rpm -rw-r–r– 1 root root 7945458 Mar 30 00:07 9ff2e28300e012e2b692e1d4445786f0bed0fd5c13ef650d61369097bfdd0519-kubectl-1.10.0-0.x86_64.rpm -rw-r–r– 1 root root 9008838 Mar 5 21:56 fe33057ffe95bfae65e2f269e1b05e99308853176e24a4d027bc082b471a07c0-kubernetes-cni-0.6.0-0.x86_64.rpm 5、k8s网络组件:flannel:v0.10.0-amd64 6、实验网络规划如下: host1 172.18.0.154/22 host2 172.18.0.155/22 host3 172.18.0.156/22 VIP 172.18.0.192/22 文章视频链接:https://pan.baidu.com/s/1XVagd765eGacuoR_cgesiQ 安装步骤: 0、请先从该链接下载后面步骤所需脚本https://pan.baidu.com/s/1oK7PRLeeYHrouNCRgIQlcQ 1、在3台主机中执行基础环境配置脚本 base-env-config.sh。 2、在主机1执行脚本 host1-base-env.sh 3、在主机2执行脚本 host2-base-env.sh 4、在主机3执行脚本 host3-base-env.sh 5、在host1主机执行如下命令 [root@host1 ~]# scp -r /etc/etcd/ssl [email protected]:/etc/etcd/ [root@host1 ~]# scp -r /etc/etcd/ssl [email protected]:/etc/etcd/ 6、在3台主机中分别执行脚本 etcd.sh 7、查看keepalived状态 systemctl status keepalived 8、查看etcd运行状态 在host1,host2,host3分别执行如下命令: etcdctl --endpoints=https://${NODE_IP}:2379 --ca-file=/etc/etcd/ssl/ca.pem --cert-file=/etc/etcd/ssl/etcd.pem --key-file=/etc/etcd/ssl/etcd-key.pem cluster-health 9、在3台主机上安装kubeadm,kubelet,kubctl,docker yum install kubelet kubeadm kubectl kubernetes-cni docker -y 10、在3台主机禁用docker启动项参数关于SELinux的设置 sed -i 's/--selinux-enabled/--selinux-enabled=false/g' /etc/sysconfig/docker 11、在3台主机的kubelet配置文件中添加如下参数 sed -i '9a\Environment="KUBELET_EXTRA_ARGS=--pod-infra-container-image=registry.cn-hangzhou.aliyuncs.com/osoulmate/pause-amd64:3.0"' /etc/systemd/system/kubelet.service.d/10-kubeadm.conf 12、在3台主机添加docker加速器配置(可选步骤) cat << > /etc/docker/daemon.json { “registry-mirrors”: [“https://yourself.mirror.aliyuncs.com”] #请自行申请阿里云账号获取镜像加速链接 } 13、在3台主机分别执行以下命令 systemctl daemon-reload systemctl enable docker && systemctl restart docker systemctl enable kubelet && systemctl restart kubelet 14、在3台主机中分别执行kubeadmconfig.sh生成配置文件config.yaml 15、在host1主机中首先执行kubeadm初始化操作 命令如下: kubeadm init –config config.yaml 16、在host1主机中执行初始化后操作 mkdir -p $HOME/.kube sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config sudo chown $(id -u):$(id -g) $HOME/.kube/config 17、将主机host1中kubeadm初始化后生成的证书和密钥文件拷贝至host2,host3相应目录下 scp -r /etc/kubernetes/pki [email protected]:/etc/kubernetes/ scp -r /etc/kubernetes/pki [email protected]:/etc/kubernetes/ 18、为主机host1安装网络组件 podnetwork【这里选用flannel】 kubectl apply -f https://raw.githubusercontent.com/coreos/flannel/master/Documentation/kube-flannel.yml systemctl stop kubelet #由于kubelet会调用docker到默认url【谷歌】下载镜像,所以先禁用 systemctl restart docker docker pull registry.cn-hangzhou.aliyuncs.com/osoulmate/flannel:v0.10.0-amd64 systemctl start kubelet 19、在host2,host3上执行如下命令 kubeadm init –config config.yaml mkdir -p $HOME/.kube sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config sudo chown $(id -u):$(id -g) $HOME/.kube/config kubectl apply -f https://raw.githubusercontent.com/coreos/flannel/master/Documentation/kube-flannel.yml systemctl stop kubelet #如果提示需要systemctl daemon-reload,则将守护进程重启后再停止kubelet服务。 systemctl restart docker docker pull registry.cn-hangzhou.aliyuncs.com/osoulmate/flannel:v0.10.0-amd64 systemctl start kubelet 20、查看集群各节点状态【这里仅在host1主机查看结果】 [root@host1 ~]# kubectl get nodes NAME STATUS ROLES AGE VERSION host1 Ready master 5m v1.10.0 host2 Ready master 1m v1.10.0 host3 Ready master 1m v1.10.0 [root@host1 ~]# kubectl get po –all-namespaces NAMESPACE NAME READY STATUS RESTARTS AGE kube-system coredns-7997f8864c-k9dcx 1/1 Running 0 5m kube-system coredns-7997f8864c-sv9rv 1/1 Running 0 5m kube-system kube-apiserver-host1 1/1 Running 1 4m kube-system kube-apiserver-host2 1/1 Running 0 1m kube-system kube-apiserver-host3 1/1 Running 0 1m kube-system kube-controller-manager-host1 1/1 Running 1 4m kube-system kube-controller-manager-host2 1/1 Running 0 1m kube-system kube-controller-manager-host3 1/1 Running 0 1m kube-system kube-flannel-ds-88tz5 1/1 Running 0 1m kube-system kube-flannel-ds-g9dpj 1/1 Running 0 2m kube-system kube-flannel-ds-h58tp 1/1 Running 0 1m kube-system kube-proxy-6fsvq 1/1 Running 1 5m kube-system kube-proxy-g8xnb 1/1 Running 1 1m kube-system kube-proxy-gmqv9 1/1 Running 1 1m kube-system kube-scheduler-host1 1/1 Running 1 5m kube-system kube-scheduler-host2 1/1 Running 1 1m kube-system kube-scheduler-host3 1/1 Running 0 1m 21、高可用验证 将host1关机,在host3上执行 while true; do sleep 1; kubectl get node;date; done 在host2上观察keepalived是否已切换为主状态。 Q&A 1、为什么在kubeadm init时出现kubelet 版本不支持系统中安装的etcd的报错? 因为本文k8s管理组件kubeadm,kubectl,kubelet的安装源为阿里云源,阿里云源会和最新k8s版本保持同步。如出现版本不兼容的问题,请按照报错提示安装相应版本的etcd或kubelet,kubeadm,kubectl组件。 2、为什么安装时间同步软件chrony? 由于集群采用keepalived检测集群各节点的活动状态,如不能保证各节点时间同步,会导致心跳异常,进而影响集群的故障倒换。当然,你也可以采用其它时间同步措施,只要能保证各节点之间的时间同步即可。 3、步骤18中为什么用kubectl应用了网络组件后还要用docker pull从阿里云拉取镜像呢? kubectl应用了flannel组件后默认会从谷歌镜像库中拉取镜像,所以要先停止kubelet服务,使其停止对docker的调用,在我们手动从阿里云拉取镜像后,再重启kubelet服务,k8s相关服务会自动识别镜像。在host2,host3主机kubeadm init完成后可能还会出现其它镜像包未拉取完成的情况,这时也可以采用这种方法:即停止kubelet服务,重启docker服务,手动拉取镜像【确定需要拉取那些镜像可先在主机上使用 kubectl get po –all-namespaces命令获取各主机镜像的当前状态。如READY列显示0/1表示镜像仍在拉取/创建中,可使用你下载的k8s压缩包中名称为阿里云镜像包的txt文档中的相应命令】,之后再启动kubelet服务。除flannel镜像外,理论上所有镜像在kubeadm init中都会从阿里云镜像库中拉取,所以,如果host2,host3在kubeadm init时有镜像没有拉取完成,可等待1-2分钟,如还未成功,直接重启kubelet服务即可。 参考文章: https://www.kubernetes.org.cn/3536.html https://docs.docker.com/install/linux/docker-ce/ubuntu/#os-requirements https://kubernetes.io/docs/setup/independent/install-kubeadm/ https://linux.cn/article-4764-1.html https://blog.csdn.net/yjk13703623757/article/details/78997157
json metadata{"tags":["kubernetes","keepalived"],"links":["https://pan.baidu.com/s/1XVagd765eGacuoR_cgesiQ","https://pan.baidu.com/s/1oK7PRLeeYHrouNCRgIQlcQ","https://yourself.mirror.aliyuncs.com","https://raw.githubusercontent.com/coreos/flannel/master/Documentation/kube-flannel.yml","https://www.kubernetes.org.cn/3536.html","https://docs.docker.com/install/linux/docker-ce/ubuntu/#os-requirements","https://kubernetes.io/docs/setup/independent/install-kubeadm/","https://linux.cn/article-4764-1.html","https://blog.csdn.net/yjk13703623757/article/details/78997157"],"app":"steemit/0.1","format":"markdown"}
Transaction InfoBlock #21210716/Trx 42d08840a56d24edbbf3cd0b731d77c7a9948886
View Raw JSON Data
{
  "trx_id": "42d08840a56d24edbbf3cd0b731d77c7a9948886",
  "block": 21210716,
  "trx_in_block": 29,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-04-02T09:37:21",
  "op": [
    "comment",
    {
      "parent_author": "",
      "parent_permlink": "kubernetes",
      "author": "osoulmate",
      "permlink": "kubernetes-v1-10-keepalived-ha",
      "title": "Kubernetes v1.10+Keepalived HA集群墙内部署实践",
      "body": "导读:众所周知,K8S安装难点在于镜像下载。查询网上许多关于K8S安装部署的文章,作者要么是将镜像下载使用的工作交给了读者完成,要么是放在共享云盘中,由读者下载后导入使用。都知道,如果你不是该云盘提供商的会员,镜像下载速度堪比蜗牛。总之,三个字:”不方便“。基于最大化便利刚接触K8S的同行快速上手实践的目的,在参阅了众多同行关于K8S部署的文章,并经过反复实验验证后,将本人的实验成果在这里分享,希望可以帮助有需要的朋友。由于时间仓促,一些对本文撰写有价值的文章没有仔细考证作者和出处,在本文末尾的参阅文章中可能没有注明。如你发现本文中一些内容的原创属于你本人,请邮件联系本人处理。并在此感谢对本文创作产生帮助的作者。谢谢!\n\n本文K8S集群高可用方案采用Keepalived。\n\n实验环境:\n1、3台centos 1611版本虚拟机,mini安装。Linux localhost 3.10.0-514.el7.x86_64 #1 SMP Tue Nov 22 16:42:41 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux\n\n2、docker version\nClient:\nVersion: 1.13.1\nAPI version: 1.26\nPackage version: \nGo version: go1.8.3\nGit commit: 774336d/1.13.1\nBuilt: Wed Mar 7 17:06:16 2018\nOS/Arch: linux/amd64\n\nServer:\nVersion: 1.13.1\nAPI version: 1.26 (minimum version 1.12)\nPackage version:\nGo version: go1.8.3\nGit commit: 774336d/1.13.1\nBuilt: Wed Mar 7 17:06:16 2018\nOS/Arch: linux/amd64\nExperimental: false\n\n3、etcd Version: 3.1.13\n\n4、kubeadm,kubelet,kubectl,kube-cni版本如下:\n-rw-r–r– 1 root root 18176678 Mar 30 00:08 5844c6be68e95a741f1ad403e5d4f6962044be060bc6df9614c2547fdbf91ae5-kubelet-1.10.0-0.x86_64.rpm\n-rw-r–r– 1 root root 17767206 Mar 30 00:07 8b0cb6654a2f6d014555c6c85148a5adc5918de937f608a30b0c0ae955d8abce-kubeadm-1.10.0-0.x86_64.rpm\n-rw-r–r– 1 root root 7945458 Mar 30 00:07 9ff2e28300e012e2b692e1d4445786f0bed0fd5c13ef650d61369097bfdd0519-kubectl-1.10.0-0.x86_64.rpm\n-rw-r–r– 1 root root 9008838 Mar 5 21:56 fe33057ffe95bfae65e2f269e1b05e99308853176e24a4d027bc082b471a07c0-kubernetes-cni-0.6.0-0.x86_64.rpm\n\n5、k8s网络组件:flannel:v0.10.0-amd64\n\n6、实验网络规划如下:\nhost1 172.18.0.154/22\nhost2 172.18.0.155/22\nhost3 172.18.0.156/22\nVIP 172.18.0.192/22\n\n文章视频链接:https://pan.baidu.com/s/1XVagd765eGacuoR_cgesiQ\n\n安装步骤:\n\n0、请先从该链接下载后面步骤所需脚本https://pan.baidu.com/s/1oK7PRLeeYHrouNCRgIQlcQ\n\n1、在3台主机中执行基础环境配置脚本 base-env-config.sh。\n\n2、在主机1执行脚本 host1-base-env.sh\n\n3、在主机2执行脚本 host2-base-env.sh\n\n4、在主机3执行脚本 host3-base-env.sh\n\n5、在host1主机执行如下命令\n[root@host1 ~]# scp -r /etc/etcd/ssl [email protected]:/etc/etcd/\n\n[root@host1 ~]# scp -r /etc/etcd/ssl [email protected]:/etc/etcd/\n\n6、在3台主机中分别执行脚本 etcd.sh\n\n7、查看keepalived状态\nsystemctl status keepalived\n\n8、查看etcd运行状态\n在host1,host2,host3分别执行如下命令:\netcdctl --endpoints=https://${NODE_IP}:2379 --ca-file=/etc/etcd/ssl/ca.pem --cert-file=/etc/etcd/ssl/etcd.pem --key-file=/etc/etcd/ssl/etcd-key.pem cluster-health\n\n9、在3台主机上安装kubeadm,kubelet,kubctl,docker\nyum install kubelet kubeadm kubectl kubernetes-cni docker -y\n\n10、在3台主机禁用docker启动项参数关于SELinux的设置\nsed -i 's/--selinux-enabled/--selinux-enabled=false/g' /etc/sysconfig/docker\n\n11、在3台主机的kubelet配置文件中添加如下参数\nsed -i '9a\\Environment=\"KUBELET_EXTRA_ARGS=--pod-infra-container-image=registry.cn-hangzhou.aliyuncs.com/osoulmate/pause-amd64:3.0\"' /etc/systemd/system/kubelet.service.d/10-kubeadm.conf\n\n12、在3台主机添加docker加速器配置(可选步骤)\ncat << > /etc/docker/daemon.json\n{\n“registry-mirrors”: [“https://yourself.mirror.aliyuncs.com”] #请自行申请阿里云账号获取镜像加速链接\n}\n\n13、在3台主机分别执行以下命令\nsystemctl daemon-reload\nsystemctl enable docker && systemctl restart docker\nsystemctl enable kubelet && systemctl restart kubelet\n\n14、在3台主机中分别执行kubeadmconfig.sh生成配置文件config.yaml\n\n15、在host1主机中首先执行kubeadm初始化操作\n命令如下:\nkubeadm init –config config.yaml\n\n16、在host1主机中执行初始化后操作\nmkdir -p $HOME/.kube\nsudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config\nsudo chown $(id -u):$(id -g) $HOME/.kube/config\n\n17、将主机host1中kubeadm初始化后生成的证书和密钥文件拷贝至host2,host3相应目录下\nscp -r /etc/kubernetes/pki [email protected]:/etc/kubernetes/\nscp -r /etc/kubernetes/pki [email protected]:/etc/kubernetes/\n\n18、为主机host1安装网络组件 podnetwork【这里选用flannel】\nkubectl apply -f https://raw.githubusercontent.com/coreos/flannel/master/Documentation/kube-flannel.yml\nsystemctl stop kubelet #由于kubelet会调用docker到默认url【谷歌】下载镜像,所以先禁用\nsystemctl restart docker\ndocker pull registry.cn-hangzhou.aliyuncs.com/osoulmate/flannel:v0.10.0-amd64\nsystemctl start kubelet\n\n19、在host2,host3上执行如下命令\nkubeadm init –config config.yaml\nmkdir -p $HOME/.kube\nsudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config\nsudo chown $(id -u):$(id -g) $HOME/.kube/config\n\nkubectl apply -f https://raw.githubusercontent.com/coreos/flannel/master/Documentation/kube-flannel.yml\nsystemctl stop kubelet #如果提示需要systemctl daemon-reload,则将守护进程重启后再停止kubelet服务。\nsystemctl restart docker\ndocker pull registry.cn-hangzhou.aliyuncs.com/osoulmate/flannel:v0.10.0-amd64\nsystemctl start kubelet\n\n20、查看集群各节点状态【这里仅在host1主机查看结果】\n[root@host1 ~]# kubectl get nodes\nNAME STATUS ROLES AGE VERSION\nhost1 Ready master 5m v1.10.0\nhost2 Ready master 1m v1.10.0\nhost3 Ready master 1m v1.10.0\n[root@host1 ~]# kubectl get po –all-namespaces\nNAMESPACE NAME READY STATUS RESTARTS AGE\nkube-system coredns-7997f8864c-k9dcx 1/1 Running 0 5m\nkube-system coredns-7997f8864c-sv9rv 1/1 Running 0 5m\nkube-system kube-apiserver-host1 1/1 Running 1 4m\nkube-system kube-apiserver-host2 1/1 Running 0 1m\nkube-system kube-apiserver-host3 1/1 Running 0 1m\nkube-system kube-controller-manager-host1 1/1 Running 1 4m\nkube-system kube-controller-manager-host2 1/1 Running 0 1m\nkube-system kube-controller-manager-host3 1/1 Running 0 1m\nkube-system kube-flannel-ds-88tz5 1/1 Running 0 1m\nkube-system kube-flannel-ds-g9dpj 1/1 Running 0 2m\nkube-system kube-flannel-ds-h58tp 1/1 Running 0 1m\nkube-system kube-proxy-6fsvq 1/1 Running 1 5m\nkube-system kube-proxy-g8xnb 1/1 Running 1 1m\nkube-system kube-proxy-gmqv9 1/1 Running 1 1m\nkube-system kube-scheduler-host1 1/1 Running 1 5m\nkube-system kube-scheduler-host2 1/1 Running 1 1m\nkube-system kube-scheduler-host3 1/1 Running 0 1m\n\n21、高可用验证\n将host1关机,在host3上执行\nwhile true; do sleep 1; kubectl get node;date; done\n在host2上观察keepalived是否已切换为主状态。\n\nQ&A\n\n1、为什么在kubeadm init时出现kubelet 版本不支持系统中安装的etcd的报错?\n\n因为本文k8s管理组件kubeadm,kubectl,kubelet的安装源为阿里云源,阿里云源会和最新k8s版本保持同步。如出现版本不兼容的问题,请按照报错提示安装相应版本的etcd或kubelet,kubeadm,kubectl组件。\n\n2、为什么安装时间同步软件chrony?\n\n由于集群采用keepalived检测集群各节点的活动状态,如不能保证各节点时间同步,会导致心跳异常,进而影响集群的故障倒换。当然,你也可以采用其它时间同步措施,只要能保证各节点之间的时间同步即可。\n\n3、步骤18中为什么用kubectl应用了网络组件后还要用docker pull从阿里云拉取镜像呢?\n\nkubectl应用了flannel组件后默认会从谷歌镜像库中拉取镜像,所以要先停止kubelet服务,使其停止对docker的调用,在我们手动从阿里云拉取镜像后,再重启kubelet服务,k8s相关服务会自动识别镜像。在host2,host3主机kubeadm init完成后可能还会出现其它镜像包未拉取完成的情况,这时也可以采用这种方法:即停止kubelet服务,重启docker服务,手动拉取镜像【确定需要拉取那些镜像可先在主机上使用 kubectl get po –all-namespaces命令获取各主机镜像的当前状态。如READY列显示0/1表示镜像仍在拉取/创建中,可使用你下载的k8s压缩包中名称为阿里云镜像包的txt文档中的相应命令】,之后再启动kubelet服务。除flannel镜像外,理论上所有镜像在kubeadm init中都会从阿里云镜像库中拉取,所以,如果host2,host3在kubeadm init时有镜像没有拉取完成,可等待1-2分钟,如还未成功,直接重启kubelet服务即可。\n\n参考文章:\nhttps://www.kubernetes.org.cn/3536.html \nhttps://docs.docker.com/install/linux/docker-ce/ubuntu/#os-requirements https://kubernetes.io/docs/setup/independent/install-kubeadm/ \nhttps://linux.cn/article-4764-1.html \nhttps://blog.csdn.net/yjk13703623757/article/details/78997157",
      "json_metadata": "{\"tags\":[\"kubernetes\",\"keepalived\"],\"links\":[\"https://pan.baidu.com/s/1XVagd765eGacuoR_cgesiQ\",\"https://pan.baidu.com/s/1oK7PRLeeYHrouNCRgIQlcQ\",\"https://yourself.mirror.aliyuncs.com\",\"https://raw.githubusercontent.com/coreos/flannel/master/Documentation/kube-flannel.yml\",\"https://www.kubernetes.org.cn/3536.html\",\"https://docs.docker.com/install/linux/docker-ce/ubuntu/#os-requirements\",\"https://kubernetes.io/docs/setup/independent/install-kubeadm/\",\"https://linux.cn/article-4764-1.html\",\"https://blog.csdn.net/yjk13703623757/article/details/78997157\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
    }
  ]
}
steemcreated a new account: @osoulmate
2018/04/02 09:26:24
fee0.100 STEEM
delegation30690.000000 VESTS
creatorsteem
new account nameosoulmate
owner{"weight_threshold":1,"account_auths":[],"key_auths":[["STM52gx7qqxR1rtvRTdAqEZG7PP6mSLGTgzhyyrfyj2qJ24SCmYGp",1]]}
active{"weight_threshold":1,"account_auths":[],"key_auths":[["STM88ySTnPnN1uHsgosxdq3R5NB9sZzzb5heemRVmuiLRpuafRw7D",1]]}
posting{"weight_threshold":1,"account_auths":[],"key_auths":[["STM6wh28XJw9ZQhFwUfDQ7nrK4zad4XrBbkT4Ebn9mB9eg43rEBE3",1]]}
memo keySTM8Wvbh7ToYAnPQDt4CKiwExgJ7JV883ovHnHHapkga9DmTinyNK
json metadata{}
extensions[]
Transaction InfoBlock #21210497/Trx 1399dd03893bcfe1f59c8427971d95cf24480650
View Raw JSON Data
{
  "trx_id": "1399dd03893bcfe1f59c8427971d95cf24480650",
  "block": 21210497,
  "trx_in_block": 41,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-04-02T09:26:24",
  "op": [
    "account_create_with_delegation",
    {
      "fee": "0.100 STEEM",
      "delegation": "30690.000000 VESTS",
      "creator": "steem",
      "new_account_name": "osoulmate",
      "owner": {
        "weight_threshold": 1,
        "account_auths": [],
        "key_auths": [
          [
            "STM52gx7qqxR1rtvRTdAqEZG7PP6mSLGTgzhyyrfyj2qJ24SCmYGp",
            1
          ]
        ]
      },
      "active": {
        "weight_threshold": 1,
        "account_auths": [],
        "key_auths": [
          [
            "STM88ySTnPnN1uHsgosxdq3R5NB9sZzzb5heemRVmuiLRpuafRw7D",
            1
          ]
        ]
      },
      "posting": {
        "weight_threshold": 1,
        "account_auths": [],
        "key_auths": [
          [
            "STM6wh28XJw9ZQhFwUfDQ7nrK4zad4XrBbkT4Ebn9mB9eg43rEBE3",
            1
          ]
        ]
      },
      "memo_key": "STM8Wvbh7ToYAnPQDt4CKiwExgJ7JV883ovHnHHapkga9DmTinyNK",
      "json_metadata": "{}",
      "extensions": []
    }
  ]
}

Account Metadata

POSTING JSON METADATA
None
JSON METADATA
None
{
  "posting_json_metadata": {},
  "json_metadata": {}
}

Auth Keys

Owner
Single Signature
Public Keys
STM52gx7qqxR1rtvRTdAqEZG7PP6mSLGTgzhyyrfyj2qJ24SCmYGp1/1
Active
Single Signature
Public Keys
STM88ySTnPnN1uHsgosxdq3R5NB9sZzzb5heemRVmuiLRpuafRw7D1/1
Posting
Single Signature
Public Keys
STM6wh28XJw9ZQhFwUfDQ7nrK4zad4XrBbkT4Ebn9mB9eg43rEBE31/1
Memo
STM8Wvbh7ToYAnPQDt4CKiwExgJ7JV883ovHnHHapkga9DmTinyNK
{
  "owner": {
    "weight_threshold": 1,
    "account_auths": [],
    "key_auths": [
      [
        "STM52gx7qqxR1rtvRTdAqEZG7PP6mSLGTgzhyyrfyj2qJ24SCmYGp",
        1
      ]
    ]
  },
  "active": {
    "weight_threshold": 1,
    "account_auths": [],
    "key_auths": [
      [
        "STM88ySTnPnN1uHsgosxdq3R5NB9sZzzb5heemRVmuiLRpuafRw7D",
        1
      ]
    ]
  },
  "posting": {
    "weight_threshold": 1,
    "account_auths": [],
    "key_auths": [
      [
        "STM6wh28XJw9ZQhFwUfDQ7nrK4zad4XrBbkT4Ebn9mB9eg43rEBE3",
        1
      ]
    ]
  },
  "memo": "STM8Wvbh7ToYAnPQDt4CKiwExgJ7JV883ovHnHHapkga9DmTinyNK"
}

Witness Votes

0 / 30
No active witness votes.
[]