The Masa Testnet and access bootnodes and node IP's

Masa Testnet Node V1.0

Get An OpenVPN File

You must must be connected to our OpenVPN network in order to join the Masa Testnet and access bootnodes and node IP's. Please reach out to an admin on Discord (https://discord.gg/SXwRKNMc) to get an OpenVPN file! Please download the OpenVPN Connect client to connect to the Masa Testnet cluster here

Check you can access the node IP range througe OpenVPN

Check your routing table by running netstat -rn from the command line to ensure you can access the Masa Testnet. You will see 172.16.239/24 10.254.0.17 UGSc utun4 if you have OpenVPN setup correctly.

   netstat -rn

   Internet:
   Destination        Gateway            Flags        Netif Expire
   default            192.168.1.1        UGScg          en0       
   10.254.0.1/32      10.254.0.17        UGSc         utun4       
   10.254.0.16/30     10.254.0.18        UGSc         utun4       
   10.254.0.17        10.254.0.18        UH           utun4       
   127                127.0.0.1          UCS            lo0       
   127.0.0.1          127.0.0.1          UH             lo0       
   169.254            link#6             UCS            en0      !
   172.16.239/24      10.254.0.17        UGSc         utun4       

Get Docker

  1. Install Docker (https://www.docker.com/get-started)
    • If your Docker distribution does not contain docker-compose, follow this to install Docker Compose
    • Make sure your Docker daemon has at least 4G memory
    • Required Docker Engine 18.02.0+ and Docker Compose 1.21+

Install The Masa Testnet Node v1.0

git clone https://github.com/masa-finance/masa-node-v1
cd masa-node-v1

Directory structure

masa-node-v1/
├── network
│   ├── testnet
│       ├── genesis.json
├── node
│   ├── data
├── node-ui
├── docker-compose.yml
├── genesis.json
  1. Run PRIVATE_CONFIG=ignore docker-compose up -d

    cd masa-node-v1
    PRIVATE_CONFIG=ignore docker-compose up -d
  2. Run docker ps to verify that you masa-node container is healthy

  3. Run docker logs <container-name> -f to view the logs for a particular container

  4. Note: to attach geth to your node Javascript console (use the same container id or name from docker ps

    docker exec -it masa-node-v10_masa-node_1 geth attach /qdata/dd/geth.ipc
    Welcome to the Geth JavaScript console!
    
    instance: Geth/node1-istanbul/v1.9.24-stable-d5ef77ca(quorum-v21.7.1)/linux-amd64/go1.15.5
    coinbase: 0xa3178965a2022c8374afe6690182f54d48208d0a
    at block: 18008 (Thu Dec 09 2021 20:45:32 GMT+0000 (UTC))
    datadir: /qdata/dd
    modules: admin:1.0 debug:1.0 eth:1.0 istanbul:1.0 miner:1.0 net:1.0 personal:1.0 rpc:1.0 txpool:1.0 web3:1.0
    To exit, press ctrl-d
    > 
    
  5. To shutdown the Masa Testnet Node

    docker-compose down

Troubleshooting Docker

  1. Docker is frozen or containers crash and reboot
    • Check if your Docker daemon is allocated enough memory (minimum 4G)

Node UI

Specification

  • Next.js & Typescript
  • Docker for deployment

Config

Next.js is launched in Docker using the following Dockerfile

# Naively Simple Node Dockerfile

FROM node:14.17-alpine

RUN mkdir -p /home/app/ && chown -R node:node /home/app
WORKDIR /home/app
COPY --chown=node:node . .

USER node

RUN yarn install --frozen-lockfile
RUN yarn build

EXPOSE 3000
CMD [ "yarn", "start" ]

Running

cd node-ui

Build the image docker build -t masa-node-ui .

Check the local built image docker image ls

Start the docker container docker run -p 3000:3000 masa-node-ui

Navigate to you local host to interact with the Masa Node http://localhost:3000

Owner
Masa Finance
🌽 Masa is a decentralized financial data platform that allows you to own and share your financial data with one-click
Masa Finance
Comments
  • Add community bootnode address (#20)

    Add community bootnode address (#20)

    Co-authored-by: Brendan Playford [email protected] Hello. I have a few nodes:

    admin.addPeer("enode://51846037004a1e50958d84b0f5d8fde5c300187a54494fb5e215497acae59d7d2c1f61259b36c80126ccce09e2743f684dd933b998d74f84faaf7a0820e6d790@65.21.121.69:21000")

    admin.addPeer("enode://8174e0f80c6fd2b2ce5e0397ffac2735d1e7167edce14474cead7f61e8851e025ade36d313949ec823489d3121e946a07e6751e68febc2ee1070e05271055cce@65.108.108.247:21000")

    admin.addPeer("enode://8dc0c8c302a7da774cf8a25eb993aad97efc941dfbff442b9c4d4ed2d3f0e02883c5cb50acf73bab676bf8e6b634b2cb8c7c0172a399c7064e7491226b9d1ee7@65.21.72.147:21000")

    admin.addPeer("enode://f4596869310c039ca6a07899e9062a63fa22c6ec7b2fce8bb83913c55a08ebe32a0cbce6eddae126660cabbed4cf893cb64d712a49f7d18464fc96ed2f81c507@142.132.146.169:21000")

    admin.addPeer("enode://c197862d4fa7325565b466189ede79587dabdda0ca82921a7560029315e820aacd2e53f855228984e0bb71545237d9d02786f7360cbc3c0fc140df7a5121a4b9@65.21.224.199:21000?discport=41306")

    admin.addPeer("enode://d1b0d78cb6942f081531063e827b900c5884687f13470adcae317990c9fd170908e09cbaeb5cb4abc5d5982c3bc68c0145dc38436cf6abc9580b5e88e678d7f1@65.108.127.24:21000")

    admin.addPeer("enode://61b7dd5149e9c9554f2535354b6f4ede3455929ceb610cc1f033a09cdb458b6aedbc54e06ebcac7c154185efef80320066ce12dc6eb775d461aad8e715ef60fe@65.21.131.58:21000")

    admin.addPeer("enode://ab00488ef44267628df414756db1174761485c76a88a23c1fd1475717f93530a1fa7c2621a3b55f40a930b847a84bedb67627bc335d54a15adf588bd05f46fd9@65.108.109.162:21000")

    admin.addPeer("enode://0a65f145c007313dc2cb672bf380abedca22f197868b2900d386289c9f0634f4fe8ebe791a1a80b36e347e04886062a54f0d66dc8a4216961bd5621ba5d4a748@65.108.121.245:21000")

    admin.addPeer("enode://8ca09502a18b5296880a946672a7ae771c4787744a3cf90431be965304e590213f4716e549d1e0a9edded81d2e6e5fc9a4f750906c832d6a6f107dfcba1a1e69@65.21.137.115:21000")

  • Cant start UI container

    Cant start UI container

    Hello!

    1. PRIVATE_CONFIG=ignore docker-compose up -d ui
    2. docker logs masa-node-v10_ui_1
    3. standard_init_linux.go:228: exec user process caused: exec format error

    uname -a Linux Ubuntu-2110-impish-amd64-base 5.13.0-21-generic #21-Ubuntu SMP Tue Oct 19 08:59:28 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

    docker version

    Client: Docker Engine - Community
     Version:           20.10.12
     API version:       1.41
     Go version:        go1.16.12
     Git commit:        e91ed57
     Built:             Mon Dec 13 11:45:33 2021
     OS/Arch:           linux/amd64
     Context:           default
     Experimental:      true
    
    Server: Docker Engine - Community
     Engine:
      Version:          20.10.12
      API version:      1.41 (minimum version 1.12)
      Go version:       go1.16.12
      Git commit:       459d0df
      Built:            Mon Dec 13 11:43:41 2021
      OS/Arch:          linux/amd64
      Experimental:     false
     containerd:
      Version:          1.4.12
      GitCommit:        7b11cfaabd73bb80907dd23182b9347b4245eb5d
     runc:
      Version:          1.0.2
      GitCommit:        v1.0.2-0-g52b36a2
     docker-init:
      Version:          0.19.0
      GitCommit:        de40ad0
    

    cat /etc/os-release

    PRETTY_NAME="Ubuntu 21.10"
    NAME="Ubuntu"
    VERSION_ID="21.10"
    VERSION="21.10 (Impish Indri)"
    

    docker-compose version

    docker-compose version 1.27.4, build unknown
    docker-py version: 4.4.4
    CPython version: 3.9.7
    OpenSSL version: OpenSSL 1.1.1l  24 Aug 2021
    

    docker image ls

    REPOSITORY                 TAG       IMAGE ID       CREATED       SIZE
    hideonbushx/node-ui        latest    9429770f1aa3   2 weeks ago   1.47GB
    
  • add community bootnode

    add community bootnode

    admin.addPeer("enode://2cd0ee8aba8f7386ef440ed616730c5b1dc4066468d4c4155f60454a606d3094e96c53b06c6d9ea13a667f3af478e7e5639752359796ad43b6cb63b172234c0f@83.171.248.44:21000")

  • New boot node

    New boot node

    admin.addPeer("enode://ede91c3f91059c22f7518f1493dcb7b703e0a8611bfdf91d131221e212912cb308e0cf23c6f9156eb00b21d5b1f7f5ecc3625583cb777d4fb8a78273620985f6@94.250.201.137:30300")

  • OpenVPN server dropped connection

    OpenVPN server dropped connection

    I've installed and run a node more than 20h ago, but new day at morning I've discovered the VPN server dropped me and I can't access to network anymore. Maybe I could have access when somebody leaves. Looks like OpenVPN server has no more IPs for connections. Some guy wrote about it in the discord:

    mercury — Today, в 7:33
    I have some problems with openvpn connection, tun0 interface just do not receive any IP
    I think there just no more IPs left on the server side @teslashibe
    You are using net30 topology, so there is only 64 in /24 net
    I think we better use subnet topology on server https://community.openvpn.net/openvpn/wiki/Topology
    
    Correct me if I'm wrong, please
    

    Here is some logs:

    root@localhost:~/masanode/masa-node-v1.0# docker ps
    CONTAINER ID   IMAGE                             COMMAND                  CREATED        STATUS                  PORTS                                                                                               NAMES
    7d3f7a4bdd9a   quorumengineering/quorum:21.7.1   "/bin/sh -c 'DDIR=/q…"   17 hours ago   Up 16 hours (healthy)   8546/tcp, 21000/tcp, 30303/tcp, 50400/tcp, 30303/udp, 0.0.0.0:22001->8545/tcp, :::22001->8545/tcp   masa-node-v10_masa-node_1
    
    root@localhost:~# netstat -rn
    Kernel IP routing table
    Destination     Gateway         Genmask         Flags   MSS Window  irtt Iface
    0.0.0.0         10.255.255.1    0.0.0.0         UG        0 0          0 ens192
    10.255.255.1    0.0.0.0         255.255.255.255 UH        0 0          0 ens192
    172.16.240.0    0.0.0.0         255.255.255.0   U         0 0          0 br-c97d3f3c1d40
    172.17.0.0      0.0.0.0         255.255.0.0     U         0 0          0 docker0
    root@localhost:~# openvpn3 sessions-list
    No sessions available
    root@localhost:~# openvpn3 session-start --config ${OPENVPN_CONFIG}
    Using pre-loaded configuration profile '/root/openvpnconfig/masausrbad.ovpn'
    Session path: /net/openvpn/v3/sessions/50c0a47esc077s4d16sbc6cs7f4a20f490da
    session-start: ** ERROR ** Failed to start session
    root@localhost:~# openvpn3 session-start --config ${OPENVPN_CONFIG}
    Using pre-loaded configuration profile '/root/openvpnconfig/masausrbad.ovpn'
    Session path: /net/openvpn/v3/sessions/e6d2bd45s02cfs42fas93c9s7b7a26c92800
    session-start: ** ERROR ** Failed to start session
    root@localhost:~# openvpn3 session-start --config ${OPENVPN_CONFIG}
    Using pre-loaded configuration profile '/root/openvpnconfig/masausrbad.ovpn'
    Session path: /net/openvpn/v3/sessions/8fcb31cas190es4dd2sb4dbs9b4eaff655c8
    session-start: ** ERROR ** Failed to start session
    root@localhost:~# openvpn3 session-start --config ${OPENVPN_CONFIG}
    Using pre-loaded configuration profile '/root/openvpnconfig/masausrbad.ovpn'
    Session path: /net/openvpn/v3/sessions/5ae9a48ds90a6s4555s9adfs6335f9cf959a
    session-start: ** ERROR ** Failed to start session
    root@localhost:~# openvpn3 session-start --config ${OPENVPN_CONFIG}
    Using pre-loaded configuration profile '/root/openvpnconfig/masausrbad.ovpn'
    Session path: /net/openvpn/v3/sessions/70d071f1s0d19s41ccs87a4sa0acd745cf22
    session-start: ** ERROR ** Failed to start session
    root@localhost:~# openvpn3 session-start --config ${OPENVPN_CONFIG}
    Using pre-loaded configuration profile '/root/openvpnconfig/masausrbad.ovpn'
    Session path: /net/openvpn/v3/sessions/9e92bf18sbbafs4fdds87f5s6be3b69e2f96
    session-start: ** ERROR ** Failed to start session
    root@localhost:~# openvpn3 session-start --config ${OPENVPN_CONFIG}
    Using pre-loaded configuration profile '/root/openvpnconfig/masausrbad.ovpn'
    Session path: /net/openvpn/v3/sessions/dbcfb42ds1343s44b0s813as974d80e76806
    session-start: ** ERROR ** Failed to start session
    

    p.s. just got connected when made more tries. But docker container didn't start to work itself. Just restarted docker container and it works fine, but problem with max connections still alive.

  • Several issues and one question

    Several issues and one question

    Hi, it's not the first time setting up a node, but a Masa node with go-ethereum and within Docker.

    After fixing the two issues already reported here I'm now at the following points:

    • running "make test" I get ok github.com/ethereum/go-ethereum/trie
      FAIL util.go:47: exit status 1 exit status 1 make: *** [Makefile:41: test] Error 1

    • when I run geth he does not abort due to an error, but is looking for peer nodes, wrting something to disk/cache etc.

    • executing PRIVATE_CONFIG=ignore geth --identity MasaMoonNode --datadir data --bootnodes enode://91a3c3d5e76b0acf05d9abddee959f1bcbc7c91537d2629288a9edd7a3df90acaa46ffba0e0e5d49a20598e0960ac458d76eb8fa92a1d64938c0a3a3d60f8be4@54.158.188.182:21000 --emitcheckpoints --istanbul.blockperiod 1 --mine --miner.threads 1 --syncmode full --verbosity 5 --networkid 190250 --rpc --rpccorsdomain "" --rpcvhosts "" --rpcaddr 127.0.0.1 --rpcport 8545 --rpcapi admin,db,eth,debug,miner,net,shh,txpool,personal,web3,quorum,istanbul --port 30300 I get the error "flag provided but not defined: -emitcheckpoints". While looking up this error I got references like "the flag provided but not defined message means that you are running a standard Ethereum geth executable, not Quorum. You need to make sure the Quorum geth is the first one found in your path." Since I have not read anything about Quorum in the Masa guide I'm uncertain to install Quorum and configure it. Any idea?

    • And the last thing is: Executing docker-compose up ui gives me: [+] Running 2/2 ⠿ Network ui_default Created 0.1s ⠿ Container ui-ui-1 Created 0.1s Attaching to ui-ui-1 ui-ui-1 | standard_init_linux.go:228: exec user process caused: exec format error ui-ui-1 exited with code 1

    So, that are the current issues. Now the question: I have setup ufw on my VPS. Which port do I need to open for incoming requests? Are there any incoming requests? I saw port 8545, 21000, 30300 and 3000 for the UI.

    Ah, there is another question: I saw the issue someone trying to connect MetaMask to Masa. I did not find anything about that in the guide. Where to look for and why should it be done?

    many thanks for any help

  • add community bootnod

    add community bootnod

    enode://e51f5b732a1f12b53932a33b5b44adc81b8f72f714e653e89a353103c560cdbd8af3d0ab7c49cfa252f6e54f438d64bc3f15c2a547095a18a41e64e55ce69456@141.94.253.202:30300

  • source build error (Run With Geth)

    source build error (Run With Geth)

    current source (56eaa139da476ac7067ed8816958fae4d62e822b) not build:

    go version

    $ go version
    go version go1.17.5 linux/amd64
    

    build error

    ~/masa-node-v1.0/src$ make all
    env GO111MODULE=on go run build/ci.go install
    >>> /usr/local/go/bin/go build -trimpath -v -o /home/setar/masa-node-v1.0/src/build/bin/abidump ./cmd/abidump
    signer/core/api.go:29:2: no required module provides package github.com/ethereum/go-ethereum/accounts/keystore; to add it:
            go get github.com/ethereum/go-ethereum/accounts/keystore
    

    error on get go module

    ~/masa-node-v1.0/src$ go get github.com/ethereum/go-ethereum/accounts/keystore
    go get github.com/ethereum/go-ethereum/accounts/keystore: no matching versions for query "upgrade"
    
  • flag provided but not defined: -emitcheckpoints

    flag provided but not defined: -emitcheckpoints

    after

    PRIVATE_CONFIG=ignore geth --identity LuckyNodeTech --datadir data --bootnodes enode://91a3c3d5e76b0acf05d9abddee959f1bcbc7c91537d2629288a9edd7a3df90acaa46ffba0e0e5d49a20598e0960ac458d76eb8fa92a1d64938c0a3a3d60f8be4@54.158.188.182:21000 --emitcheckpoints --istanbul.blockperiod 1 --mine --miner.threads 1 --syncmode full --verbosity 5 --networkid 190250 --rpc --rpccorsdomain "*" --rpcvhosts "*" --rpcaddr 127.0.0.1 --rpcport 8545 --rpcapi admin,db,eth,debug,miner,net,shh,txpool,personal,web3,quorum,istanbul --port 30300

    I get flag provided but not defined: -emitcheckpoints

    Any idea?

  • How can i change port http://localhost:3000/ to another

    How can i change port http://localhost:3000/ to another

    Hello! I have installed node Taraxa and Taraxa has already use port http://localhost:3000/. In this way when i have installed Masa-finance, i have an error "Bind for 0.0.0.0:3000 failed: port is already allocated ERROR: for ui Cannot start service ui: driver failed programming external connectivity on endpoint masa-node-v10_ui_1 (dcbc12fcdca8679aa4d7ac6d288a81691aabf281cc5b0f5d1d7cfe45f1acd8bc): Bind for 0.0.0.0:3000 failed: port is already allocated"

    What i gone do?

  • Empty container data dir after restart docker

    Empty container data dir after restart docker

    bad idea to recreate data dirs on every restart container. i think base structure and genesis need to creane first run only ...

    But i am not yet ready to offer a beautiful method for implementing this.

    setar@masa-node:~/masa-node-v1.0$ git diff
    diff --git a/docker-compose.yml b/docker-compose.yml
    index 18934f8c..9dd8f944 100644
    --- a/docker-compose.yml
    +++ b/docker-compose.yml
    @@ -21,14 +21,10 @@ x-masa-testnet-node-v10-def:
         - -c
         - |
           DDIR=/qdata/dd
    -      rm -rf $${DDIR}
    -      mkdir -p $${DDIR}/keystore
    -      mkdir -p $${DDIR}/geth
           GENESIS_FILE="/network/genesis.json"
           CONSENSUS_RPC_API="istanbul"
           NETWORK_ID=$$(cat $${GENESIS_FILE} | grep chainId | awk -F " " '{print $$2}' | awk -F "," '{print $$1}')
           GETH_ARGS_istanbul="--emitcheckpoints --istanbul.blockperiod 1 --mine --miner.threads 1 --syncmode full"
    -      geth --datadir $${DDIR} init $${GENESIS_FILE}
           geth \
             --identity node$${NODE_ID}-${MASA_CONSENSUS:-istanbul} \
             --datadir $${DDIR} \
    @@ -54,6 +50,7 @@ services:
         hostname: masa-node
         ports:
           - "22001:8545"
    +      - "21000:21000"
         volumes:
           - vol1:/qdata
           - ./network/testnet:/network:ro
    
  • Docker - Error initialising Private Transaction Manager

    Docker - Error initialising Private Transaction Manager

    Hi, I tried to pull Docker containers on Ubuntu 20.04 and node container is constantly crashing with the following error error uname -a gives '...5.4.0-105-generic #119-Ubuntu SMP Mon Mar 7 18:49:24 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux'

    Latest docker

    Docker-compose is v2.6.1

    Any ideas how to fix it?

  • --emitcheckpoint error

    --emitcheckpoint error

    gave my node identity with this geth --identity JohnpaulifediNODE and its syncing image

    now i started the node with this PRIVATE_CONFIG=ignore geth --identity JohnpaulifediNODE --datadir data --bootnodes enode://91a3c3d5e76b0acf05d9abddee959f1bcbc7c91537d2629288a9edd7a3df90acaa46ffba0e0e5d49a20598e0960ac458d76eb8fa92a1d64938c0a3a3d60f8be4@54.158.188.182:21000 --emitcheckpoints --istanbul.blockperiod 10 --mine --miner.threads 1 --syncmode full --verbosity 5 --networkid 190260 --rpc --rpccorsdomain "" --rpcvhosts "" --rpcaddr 127.0.0.1 --rpcport 8545 --rpcapi admin,db,eth,debug,miner,net,shh,txpool,personal,web3,quorum,istanbul --port 30300

    got this erorr image

    echo path not same with guide image

    geth version image

    make test was this image

    but syncing when from 4% to 17% image

    what could be the issue here?

  • add bootnode

    add bootnode

    enode://85d15b93169559f59a0630a5246c53adaf36ec00f99e715de465f107bfe75cdbe065d73047288d82d67f6984f7de4820bf61c20d61f7c6add3c1b546bf48ee52@91.189.133.78:30300

  • Docker-compose Extends not supported in version 3 schema

    Docker-compose Extends not supported in version 3 schema

    Command PRIVATE_CONFIG=ignore docker-compose up -d Throw an error:

    ERROR: The Compose file './docker-compose.yml' is invalid because:
    Unsupported config option for services.ui: 'extends'
    

    https://github.com/masa-finance/masa-node-v1.0/blob/768dfdc28e3ea33822ac9c8317f8fd8d6c2fbeca/docker-compose.yml#L51

    Docker version 20.10.16 docker-compose version 1.25.0

network-node-manager is a kubernetes controller that controls the network configuration of a node to resolve network issues of kubernetes.
network-node-manager is a kubernetes controller that controls the network configuration of a node to resolve network issues of kubernetes.

Network Node Manager network-node-manager is a kubernetes controller that controls the network configuration of a node to resolve network issues of ku

Dec 18, 2022
Golang-for-node-devs - Golang for Node.js developers

Golang for Node.js developers Who is this video for? Familiar with Node.js and i

Dec 7, 2022
Using this you can access node external ip address value from your pod.

Using this you can access node external ip address value from your pod.

Jan 30, 2022
An operator to manage node labels, annotations, and taints.

NodeConfig Operator An operator to manage node labels, annotations and taints based on NodeConfig Custom Resource. Comparison to alternatives: https:/

Dec 2, 2022
👻 A simple API to inter-process communicating between Go and Node

go-to-node A simple API to inter-process communicating between Go and NodeJS. Quick start Go to Node main.go: package main import ( "fmt" "os" "os

Jan 7, 2022
Prometheus exporter for Chia node metrics

chia_exporter Prometheus metric collector for Chia nodes, using the local RPC API Building and Running With the Go compiler tools installed: go build

Sep 19, 2022
Official Golang implementation of the Thinkium node

Go Thinkium Official Golang implementation of the Thinkium node. Building the source mkdir build docker run --rm -w /go/src/github.com/ThinkiumGroup/g

Nov 22, 2022
nano-gpu-agent is a Kubernetes device plugin for GPU resources allocation on node.
nano-gpu-agent is a Kubernetes device plugin for GPU resources allocation on node.

Nano GPU Agent About this Project Nano GPU Agent is a Kubernetes device plugin implement for gpu allocation and use in container. It runs as a Daemons

Dec 29, 2022
ADK Node ( a.k.a ADKgo v2 ) for the ADK Mesh with full Smart Contract support [Mainnet]

ADKGo SmartNode (MAINNET v2) Official Golang implementation of the ADK Mesh protocol with Smart Contract funtionality BASE NODE SETUP STEPS (on clean

Nov 24, 2021
Kubernetes Node Performance Validator

Kubernetes Node Performance Evaluator This repository contains a set of tools for testing the performance of all the nodes in a kubernetes cluster. Wh

Dec 24, 2021
Karpenter: an open-source node provisioning project built for Kubernetes
Karpenter: an open-source node provisioning project built for Kubernetes

Karpenter is an open-source node provisioning project built for Kubernetes. Its goal is to improve the efficiency and cost of running workloads on Kub

Dec 1, 2022
sample apps docker with postgres-node.js-golang

Belajar Docker untuk Pemula - Membuat TODO App TODO app ini adalah contoh app untuk mendemokan proses membuat aplikasi dengan Docker, terdiri dari: Fr

Jan 2, 2022
dashd-go is an alternative full node dash implementation written in Go (golang)

dashd-go is an alternative full node dash implementation written in Go (golang)

Jan 26, 2022
Drain-my-spot - Service draining the k8s worker node in case of spot instances related event occurrence

drain-my-spot Service draining the k8s worker node in case of spot instances rel

Feb 5, 2022
Kubectl plugin shows pod x node matrix with suitable colors to mitigate troubleshooting effort.

kubectl-pod-node-matrix WORK IN PROGRESS!! This plugin shows pod x node matrix with suitable colors to mitigate troubleshooting effort. Details Troubl

May 11, 2022
GitOops is a tool to help attackers and defenders identify lateral movement and privilege escalation paths in GitHub organizations by abusing CI/CD pipelines and GitHub access controls.
GitOops is a tool to help attackers and defenders identify lateral movement and privilege escalation paths in GitHub organizations by abusing CI/CD pipelines and GitHub access controls.

GitOops is a tool to help attackers and defenders identify lateral movement and privilege escalation paths in GitHub organizations by abusing CI/CD pipelines and GitHub access controls.

Jan 2, 2023
Pomerium is an identity-aware access proxy.

Pomerium is an identity-aware proxy that enables secure access to internal applications. Pomerium provides a standardized interface to add access cont

Jan 1, 2023
Fast, concurrent, streaming access to Amazon S3, including gof3r, a CLI. http://godoc.org/github.com/rlmcpherson/s3gof3r

s3gof3r s3gof3r provides fast, parallelized, pipelined streaming access to Amazon S3. It includes a command-line interface: gof3r. It is optimized for

Dec 26, 2022
Google Compute Engine (GCE) VM takeover via DHCP flood - gain root access by getting SSH keys added by google_guest_agent

Abstract This is an advisory about an unpatched vulnerability (at time of publishing this repo, 2021-06-25) affecting virtual machines in Google's Com

Nov 9, 2022