-
Notifications
You must be signed in to change notification settings - Fork 29
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
13 changed files
with
4,441 additions
and
64 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,71 @@ | ||
--- | ||
name: "[Provider Audit] Template" | ||
about: This is a template for all Akash Providers looking to be audited. Please fill | ||
out all fields below. | ||
title: '' | ||
labels: Provider Audit | ||
assignees: brewsterdrinkwater, andy108369 | ||
|
||
--- | ||
|
||
--- | ||
name: "[Provider Audit] Template" | ||
about: This is for Akash users interested in having their providers audited by Akash | ||
title: "[Provider Audit] Template" | ||
labels: Provider Audit | ||
assignees: andy108369 | ||
|
||
--- | ||
## Prerequisite Steps: | ||
|
||
### 1. Make sure your provider has community provider attributes: | ||
|
||
``` | ||
Example: | ||
$ provider-services query provider get akash1<REDACTED> -o text | ||
... | ||
attributes: | ||
... | ||
- key: host | ||
value: akash | ||
- key: tier | ||
value: community | ||
``` | ||
|
||
[Ref documentation:](https://docs.akash.network/providers/akash-audited-attributes#standard-attributes). | ||
|
||
### 2. Make sure your provider *.ingress resolves to your provider IP (ideally worker node IP) | ||
``` | ||
host <anything>.ingress.<yourdomain> | ||
``` | ||
|
||
Example: | ||
``` | ||
$ host anything.ingress.akash.pro | ||
anything.ingress.akash.pro is an alias for nodes.akash.pro. | ||
nodes.akash.pro has address 65.108.6.185 | ||
``` | ||
|
||
- More info on what DNS records should look like are available in the [Akash Documentation here](https://docs.akash.network/providers/build-a-cloud-provider/akash-cloud-provider-build-with-helm-charts/step-5-domain-name-review). | ||
|
||
### 3. Please make sure your Akash provider doesn't block any Akash specific ports. | ||
|
||
- If you are using a firewall, please follow this doc: | ||
https://docs.akash.network/providers/build-a-cloud-provider/akash-cloud-provider-build-with-helm-charts/step-9-firewall-rule-review | ||
- If you are behind NAT, then you need to make sure these ports are open between your provider worker nodes and the internet. | ||
|
||
|
||
|
||
# Audit Steps: | ||
|
||
#### 1. ***Title the issue: " [Provider Audit]: Provider Address" (e.g. "[Provider Audit]: provider.europlots.com")*** | ||
#### 2. Wait for response via comments. If no issues during provider Audit, process will be complete, provider should start bidding on leases, and Audit ticket will be closed. | ||
#### 3. If there are issues during the provider Audit, debug those issues, and Audit will be complete. | ||
#### 4. Audit Issue will be closed by core team member. | ||
|
||
|
||
## Leave contact information (optional) | ||
1. Name | ||
2. Discord handle or Telegram handle | ||
3. Contact email address |
This file was deleted.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.