Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Chaincode attackathon notes #4

Open
9 tasks
pinheadmz opened this issue Sep 17, 2024 · 2 comments
Open
9 tasks

Chaincode attackathon notes #4

pinheadmz opened this issue Sep 17, 2024 · 2 comments

Comments

@pinheadmz
Copy link
Contributor

pinheadmz commented Sep 17, 2024

@mplsgrant
Copy link

  1. kubectl commands like get pods may not be reliable because of default namesapce, prefer warnet status

    • or provide guidance on how to set default namespace
    • or warnet auth should set default namespace

It looks to that the create_kubeconfigs function over in bitcoin-dev-project/warnet#598 that @josibake and I are working on should provide a default namespace for those users who perform the warnet auth on the kubeconfig file that create_kubeconfigs generates.

You can see the namespace set here: https://github.com/bitcoin-dev-project/warnet/blob/297ded4e4ea638f78605eb88b17ae7a39aec4843/src/warnet/admin.py#L110

@pinheadmz
Copy link
Contributor Author

You can see the namespace set here:

Ok great. The config file i distributed was directly from digital ocean's web console

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants