7
7
8
8
#
9
9
10
- [ ![ Build status] ( https://img.shields.io/github/workflow/status/devopstoday11 /tarian/CI?style=flat )] ( https://github.com/devopstoday11 /tarian/actions )
11
- [ ![ Go Report Card] ( https://goreportcard.com/badge/github.com/devopstoday11 /tarian )] ( https://goreportcard.com/report/github.com/devopstoday11 /tarian )
10
+ [ ![ Build status] ( https://img.shields.io/github/workflow/status/kube-tarian /tarian/CI?style=flat )] ( https://github.com/kube-tarian /tarian/actions )
11
+ [ ![ Go Report Card] ( https://goreportcard.com/badge/github.com/kube-tarian /tarian )] ( https://goreportcard.com/report/github.com/kube-tarian /tarian )
12
12
13
13
#
14
14
@@ -34,7 +34,7 @@ Why another new security tool when there are many tools available already, like
34
34
#### Architecture diagram
35
35
> I will finalize the design diagram soon once I finish talking to some security experts (I already talked to few, and have few more discussions pending).
36
36
37
- ![ Arch. Diagram] ( https://github.com/devopstoday11 /tarian/blob/5eeed9a0bd5875e6cee423d2d12161a3f7d2d84c/Kube-Tarian.svg )
37
+ ![ Arch. Diagram] ( https://github.com/kube-tarian /tarian/blob/5eeed9a0bd5875e6cee423d2d12161a3f7d2d84c/Kube-Tarian.svg )
38
38
39
39
#
40
40
@@ -58,7 +58,7 @@ helm install tarian-postgresql bitnami/postgresql -n tarian-system \
58
58
3 . Install tarian
59
59
60
60
``` bash
61
- helm repo add tarian https://devopstoday11 .github.io/tarian
61
+ helm repo add tarian https://kube-tarian .github.io/tarian
62
62
helm repo update
63
63
64
64
helm install tarian-server tarian/tarian-server --devel -n tarian-system
@@ -80,14 +80,14 @@ kubectl exec -ti deploy/tarian-server -n tarian-system -- ./tarian-server db mig
80
80
## Configuration
81
81
82
82
See helm chart values for
83
- - [ tarian-server] ( https://github.com/devopstoday11 /tarian/blob/main/charts/tarian-server/values.yaml )
84
- - [ tarian-cluster-agent] ( https://github.com/devopstoday11 /tarian/blob/main/charts/tarian-cluster-agent/values.yaml )
83
+ - [ tarian-server] ( https://github.com/kube-tarian /tarian/blob/main/charts/tarian-server/values.yaml )
84
+ - [ tarian-cluster-agent] ( https://github.com/kube-tarian /tarian/blob/main/charts/tarian-cluster-agent/values.yaml )
85
85
86
86
## Usage
87
87
88
88
### Use tarianctl to control tarian-server
89
89
90
- 1 . Download from Github [ release page] ( https://github.com/devopstoday11 /tarian/releases/download/v0.0.3-alpha3/tarian_0.0.3-alpha3_linux_amd64.tar.gz )
90
+ 1 . Download from Github [ release page] ( https://github.com/kube-tarian /tarian/releases/download/v0.0.3-alpha3/tarian_0.0.3-alpha3_linux_amd64.tar.gz )
91
91
2 . Extract the file and copy tarianctl to your PATH directory
92
92
3 . Expose tarian-server to your machine, through Ingress or port-forward. For this example, we'll use port-forward:
93
93
@@ -149,8 +149,8 @@ accessible with `tarianctl get events`.
149
149
# ## Demo: Try a pod that violates the constraints
150
150
151
151
` ` ` bash
152
- kubectl apply -f https://raw.githubusercontent.com/devopstoday11 /tarian/main/dev/config/monitored-pod/configmap.yaml
153
- kubectl apply -f https://raw.githubusercontent.com/devopstoday11 /tarian/main/dev/config/monitored-pod/pod.yaml
152
+ kubectl apply -f https://raw.githubusercontent.com/kube-tarian /tarian/main/dev/config/monitored-pod/configmap.yaml
153
+ kubectl apply -f https://raw.githubusercontent.com/kube-tarian /tarian/main/dev/config/monitored-pod/pod.yaml
154
154
155
155
# wait for it to become ready
156
156
kubectl wait --for=condition=ready pod nginx
0 commit comments