Closed vadasambar closed 1 year ago
suraj1
: refactored the code further. Abstracted out runner
package for parsing, processing logs and suggesting a netpol (might need another look)suraj1
: added better error handlingsuraj1
: added architecture diagramsuraj1
: added runner interfacesuraj1
: made corednsrunner
conform to runner interfacesuraj1
: added thread safe loggingsuraj1
: replaced custom logger
package with default log
's log.Default()
which provides thread safetysuraj1
: fixed errors, refactored code, removed Initialize
from RunnerInterface
suraj1
: fixed a bug where goroutine closure in a for loop always uses the last value in the iterationsuraj1
: added a doc line explaining how tweaking core-dns Corefile is less risky than it sounds (with screenshots)
suraj1
[ ] Create an issue around evaluator transposer function doesn't understand json without indentations
e.g., for json
evalValue before {
"in": ["@faas.com", {
"var": ["email"]
}]
}
evalValue after
"in": ["@faas.com", {
"var": ["email"]
}]
for yaml <- needs more info here
evalValue before {"in":["@faas.com",{"var":["email"]}]}
evalValue after "in":["@faas.com",{"var":["email"]}
Based on print statements just after this line and after this line.
suraj1
[ ] Create an issue around evaluator transposer function doesn't understand json without indentations
e.g., for json
evalValue before {
"in": ["@faas.com", {
"var": ["email"]
}]
}
evalValue after
"in": ["@faas.com", {
"var": ["email"]
}]
for yaml <- needs more info here
evalValue before {"in":["@faas.com",{"var":["email"]}]}
evalValue after "in":["@faas.com",{"var":["email"]}
Based on print statements just after this line and after this line.
suraj1
: added levelled logging with logrussuraj1
: implemented a part of multi-threaded log processing
suraj1
[ ] Create an issue around evaluator transposer function doesn't understand json without indentations
e.g., for json
evalValue before {
"in": ["@faas.com", {
"var": ["email"]
}]
}
evalValue after
"in": ["@faas.com", {
"var": ["email"]
}]
for yaml <- needs more info here
evalValue before {"in":["@faas.com",{"var":["email"]}]}
evalValue after "in":["@faas.com",{"var":["email"]}
Based on print statements just after this line and after this line.
suraj1
: finish multi-threaded log processingsuraj1
: re-factor the code and fix bugs (log message getting duplicated etc.,)suraj1
: rename podMapping
-> hostnamePodMapping
and change some internals (so that works better with rest of the functions like suggestNetPol
)suraj1
: added nicer stdoutsuraj1
: added suggest-netpol
flagsuraj1
: updated README with extra TODOssuraj1
: finished a part of figuring out the data suraj1
needs with just log
instead of log . "suraj1:{remote}:{port}:{name}:{rcode}"
suraj1
suraj1
needs with just log
instead of log . "suraj1:{remote}:{port}:{name}:{rcode}"
[ ] Create an issue around evaluator transposer function doesn't understand json without indentations
e.g., for json
evalValue before {
"in": ["@faas.com", {
"var": ["email"]
}]
}
evalValue after
"in": ["@faas.com", {
"var": ["email"]
}]
for yaml <- needs more info here
evalValue before {"in":["@faas.com",{"var":["email"]}]}
evalValue after "in":["@faas.com",{"var":["email"]}
Based on print statements just after this line and after this line.
suraj1
: added support for figuring out the data suraj1
needs with just log
instead of log . "suraj1:{remote}:{port}:{name}:{rcode}"
suraj1
: added flag to customize concurrency
suraj1
[ ] Create an issue around evaluator transposer function doesn't understand json without indentations
e.g., for json
evalValue before {
"in": ["@faas.com", {
"var": ["email"]
}]
}
evalValue after
"in": ["@faas.com", {
"var": ["email"]
}]
for yaml <- needs more info here
evalValue before {"in":["@faas.com",{"var":["email"]}]}
evalValue after "in":["@faas.com",{"var":["email"]}
Based on print statements just after this line and after this line.
suraj1
: added support for figuring out the data suraj1
needs with just log
instead of log . "suraj1:{remote}:{port}:{name}:{rcode}"
suraj1
: added flag to customize concurrency
suraj1
: added wait-for-logs
flag to customize wait duration until relevant logs appearsuraj1
: renamed the project to kico
kico
:
kico
does.gitignore
file[ ] Create an issue around evaluator transposer function doesn't understand json without indentations
e.g., for json
evalValue before {
"in": ["@faas.com", {
"var": ["email"]
}]
}
evalValue after
"in": ["@faas.com", {
"var": ["email"]
}]
for yaml <- needs more info here
evalValue before {"in":["@faas.com",{"var":["email"]}]}
evalValue after "in":["@faas.com",{"var":["email"]}
Based on print statements just after this line and after this line.
keptn
: making datadog-service compatible with 0.20.0-next.0
version of Keptnflagd
: working on taking https://github.com/open-feature/flagd/pull/206 to completion[ ] Create an issue around evaluator transposer function doesn't understand json without indentations
e.g., for json
evalValue before {
"in": ["@faas.com", {
"var": ["email"]
}]
}
evalValue after
"in": ["@faas.com", {
"var": ["email"]
}]
for yaml <- needs more info here
evalValue before {"in":["@faas.com",{"var":["email"]}]}
evalValue after "in":["@faas.com",{"var":["email"]}
Based on print statements just after this line and after this line.
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Normal Scheduled 5m30s default-scheduler Successfully assigned keptn/approval-service-7898b7cd4-ppt9v to minikube
Warning Failed 5m26s (x2 over 5m27s) kubelet Error: failed to start container "wait-for-nats": Error response from daemon: OCI runtime create failed: container_linux.go:380: starting container process caused: process_linux.go:545: container init caused: process_linux.go:508: setting cgroup config for procHooks process caused: failed to write "8388608": write /sys/fs/cgroup/memory/kubepods/burstable/pod2575f5f0-fdec-41b4-9c8b-b8da2d5f3562/wait-for-nats/memory.memsw.limit_in_bytes: device or resource busy: unknown
Normal Pulled 5m12s (x3 over 5m27s) kubelet Container image "curlimages/curl:7.85.0" already present on machine
Normal Created 5m12s (x3 over 5m27s) kubelet Created container wait-for-nats
Normal Started 5m11s kubelet Started container wait-for-nats
Normal Started 4m53s (x2 over 4m54s) kubelet Started container wait-for-mongodb-datastore
Normal Pulled 4m12s (x4 over 4m55s) kubelet Container image "curlimages/curl:7.85.0" already present on machine
Normal Created 4m12s (x4 over 4m55s) kubelet Created container wait-for-mongodb-datastore
Warning Failed 4m12s (x2 over 4m38s) kubelet Error: failed to start container "wait-for-mongodb-datastore": Error response from daemon: OCI runtime create failed: container_linux.go:380: starting container process caused: process_linux.go:545: container init caused: process_linux.go:508: setting cgroup config for procHooks process caused: failed to write "8388608": write /sys/fs/cgroup/memory/kubepods/burstable/pod2575f5f0-fdec-41b4-9c8b-b8da2d5f3562/wait-for-mongodb-datastore/memory.memsw.limit_in_bytes: device or resource busy: unknown
Warning BackOff 25s (x21 over 4m53s) kubelet Back-off restarting failed container
Pods:
runner@fv-az456-633:~/work/datadog-service/datadog-service$ kubectl get po -nkeptn
NAME READY STATUS RESTARTS AGE
api-gateway-nginx-6954fcf89f-ks5wn 1/1 Running 0 6m43s
api-service-66696fd86b-d5kwf 1/1 Running 0 6m43s
approval-service-7898b7cd4-ppt9v 0/1 Init:CrashLoopBackOff 8 (18s ago) 6m43s
bridge-84564d9d59-m2sfx 1/1 Running 0 6m42s
keptn-mongo-c65bdf548-rf82m 1/1 Running 0 6m42s
keptn-nats-0 1/1 Running 0 6m32s
lighthouse-service-c7869f86c-6bcbl 0/1 Init:CrashLoopBackOff 6 (46s ago) 6m43s
mongodb-datastore-68b8bff8d-t2v76 1/1 Running 0 6m43s
remediation-service-59c7fc99f6-wkps7 0/1 Init:CrashLoopBackOff 8 (20s ago) 6m42s
resource-service-6d5dd448c4-jxtlh 1/1 Running 0 6m43s
secret-service-5fff5f9b8c-grlkx 1/1 Running 0 6m42s
shipyard-controller-fcbf5bc49-zt445 1/1 Running 0 6m42s
action-install-keptn
Github action and released my own patched version to support --timeout
flag in helmkeptn
: debugging issue with datadog-service integration tests with 1.0.0
version of Keptn where installation of Keptn helm chart fails with timed out waiting for condition
flagd
: working on fixing tests in https://github.com/open-feature/flagd/pull/206
[ ] Create an issue around evaluator transposer function doesn't understand json without indentations
e.g., for json
evalValue before {
"in": ["@faas.com", {
"var": ["email"]
}]
}
evalValue after
"in": ["@faas.com", {
"var": ["email"]
}]
for yaml <- needs more info here
evalValue before {"in":["@faas.com",{"var":["email"]}]}
evalValue after "in":["@faas.com",{"var":["email"]}
Based on print statements just after this line and after this line.
flagd
: tests are failing for https://github.com/open-feature/flagd/pull/206Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Normal Scheduled 5m30s default-scheduler Successfully assigned keptn/approval-service-7898b7cd4-ppt9v to minikube
Warning Failed 5m26s (x2 over 5m27s) kubelet Error: failed to start container "wait-for-nats": Error response from daemon: OCI runtime create failed: container_linux.go:380: starting container process caused: process_linux.go:545: container init caused: process_linux.go:508: setting cgroup config for procHooks process caused: failed to write "8388608": write /sys/fs/cgroup/memory/kubepods/burstable/pod2575f5f0-fdec-41b4-9c8b-b8da2d5f3562/wait-for-nats/memory.memsw.limit_in_bytes: device or resource busy: unknown
Normal Pulled 5m12s (x3 over 5m27s) kubelet Container image "curlimages/curl:7.85.0" already present on machine
Normal Created 5m12s (x3 over 5m27s) kubelet Created container wait-for-nats
Normal Started 5m11s kubelet Started container wait-for-nats
Normal Started 4m53s (x2 over 4m54s) kubelet Started container wait-for-mongodb-datastore
Normal Pulled 4m12s (x4 over 4m55s) kubelet Container image "curlimages/curl:7.85.0" already present on machine
Normal Created 4m12s (x4 over 4m55s) kubelet Created container wait-for-mongodb-datastore
Warning Failed 4m12s (x2 over 4m38s) kubelet Error: failed to start container "wait-for-mongodb-datastore": Error response from daemon: OCI runtime create failed: container_linux.go:380: starting container process caused: process_linux.go:545: container init caused: process_linux.go:508: setting cgroup config for procHooks process caused: failed to write "8388608": write /sys/fs/cgroup/memory/kubepods/burstable/pod2575f5f0-fdec-41b4-9c8b-b8da2d5f3562/wait-for-mongodb-datastore/memory.memsw.limit_in_bytes: device or resource busy: unknown
Warning BackOff 25s (x21 over 4m53s) kubelet Back-off restarting failed container
Pods:
runner@fv-az456-633:~/work/datadog-service/datadog-service$ kubectl get po -nkeptn
NAME READY STATUS RESTARTS AGE
api-gateway-nginx-6954fcf89f-ks5wn 1/1 Running 0 6m43s
api-service-66696fd86b-d5kwf 1/1 Running 0 6m43s
approval-service-7898b7cd4-ppt9v 0/1 Init:CrashLoopBackOff 8 (18s ago) 6m43s
bridge-84564d9d59-m2sfx 1/1 Running 0 6m42s
keptn-mongo-c65bdf548-rf82m 1/1 Running 0 6m42s
keptn-nats-0 1/1 Running 0 6m32s
lighthouse-service-c7869f86c-6bcbl 0/1 Init:CrashLoopBackOff 6 (46s ago) 6m43s
mongodb-datastore-68b8bff8d-t2v76 1/1 Running 0 6m43s
remediation-service-59c7fc99f6-wkps7 0/1 Init:CrashLoopBackOff 8 (20s ago) 6m42s
resource-service-6d5dd448c4-jxtlh 1/1 Running 0 6m43s
secret-service-5fff5f9b8c-grlkx 1/1 Running 0 6m42s
shipyard-controller-fcbf5bc49-zt445 1/1 Running 0 6m42s
keptn
: fixed timed out waiting for condition
issue in integration tests in datadog-service
flagd
: fixed tests failing when make test
is runflagd
: addressed all the comments and fixed a bug in the yaml support PR
keptn
: working on making datadog-service
compatible with 1.0.0
[ ] Create an issue around evaluator transposer function doesn't understand json without indentations
e.g., for json
evalValue before {
"in": ["@faas.com", {
"var": ["email"]
}]
}
evalValue after
"in": ["@faas.com", {
"var": ["email"]
}]
for yaml <- needs more info here
evalValue before {"in":["@faas.com",{"var":["email"]}]}
evalValue after "in":["@faas.com",{"var":["email"]}
Based on print statements just after this line and after this line.
google.com
works)keptn
: working on making datadog-service
compatible with 1.0.0
[ ] Create an issue around evaluator transposer function doesn't understand json without indentations
e.g., for json
evalValue before {
"in": ["@faas.com", {
"var": ["email"]
}]
}
evalValue after
"in": ["@faas.com", {
"var": ["email"]
}]
for yaml <- needs more info here
evalValue before {"in":["@faas.com",{"var":["email"]}]}
evalValue after "in":["@faas.com",{"var":["email"]}
Based on print statements just after this line and after this line.
nslookup
sites like google.com
works fine. Seems like a DNS issue (more details here)keptn
: working on making datadog-service
compatible with 1.0.0
[ ] Create an issue around evaluator transposer function doesn't understand json without indentations
e.g., for json
evalValue before {
"in": ["@faas.com", {
"var": ["email"]
}]
}
evalValue after
"in": ["@faas.com", {
"var": ["email"]
}]
for yaml <- needs more info here
evalValue before {"in":["@faas.com",{"var":["email"]}]}
evalValue after "in":["@faas.com",{"var":["email"]}
Based on print statements just after this line and after this line.
keptn
: working on making datadog-service
compatible with 1.0.0
[ ] Create an issue around evaluator transposer function doesn't understand json without indentations
e.g., for json
evalValue before {
"in": ["@faas.com", {
"var": ["email"]
}]
}
evalValue after
"in": ["@faas.com", {
"var": ["email"]
}]
for yaml <- needs more info here
evalValue before {"in":["@faas.com",{"var":["email"]}]}
evalValue after "in":["@faas.com",{"var":["email"]}
Based on print statements just after this line and after this line.
keptn
: working on making datadog-service
compatible with 1.0.0
[ ] Create an issue around evaluator transposer function doesn't understand json without indentations
e.g., for json
evalValue before {
"in": ["@faas.com", {
"var": ["email"]
}]
}
evalValue after
"in": ["@faas.com", {
"var": ["email"]
}]
for yaml <- needs more info here
evalValue before {"in":["@faas.com",{"var":["email"]}]}
evalValue after "in":["@faas.com",{"var":["email"]}
Based on print statements just after this line and after this line.
keptn
: working on making datadog-service
compatible with 1.0.0
[ ] Create an issue around evaluator transposer function doesn't understand json without indentations
e.g., for json
evalValue before {
"in": ["@faas.com", {
"var": ["email"]
}]
}
evalValue after
"in": ["@faas.com", {
"var": ["email"]
}]
for yaml <- needs more info here
evalValue before {"in":["@faas.com",{"var":["email"]}]}
evalValue after "in":["@faas.com",{"var":["email"]}
Based on print statements just after this line and after this line.
keptn
: working on making datadog-service
compatible with 1.0.0
blogposts
: working on corefile-poc
blogposts
: gathering info for blogpost[ ] Create an issue around evaluator transposer function doesn't understand json without indentations
e.g., for json
evalValue before {
"in": ["@faas.com", {
"var": ["email"]
}]
}
evalValue after
"in": ["@faas.com", {
"var": ["email"]
}]
for yaml <- needs more info here
evalValue before {"in":["@faas.com",{"var":["email"]}]}
evalValue after "in":["@faas.com",{"var":["email"]}
Based on print statements just after this line and after this line.
keptn
: working on making datadog-service
compatible with 1.0.0
[ ] Create an issue around evaluator transposer function doesn't understand json without indentations
e.g., for json
evalValue before {
"in": ["@faas.com", {
"var": ["email"]
}]
}
evalValue after
"in": ["@faas.com", {
"var": ["email"]
}]
for yaml <- needs more info here
evalValue before {"in":["@faas.com",{"var":["email"]}]}
evalValue after "in":["@faas.com",{"var":["email"]}
Based on print statements just after this line and after this line.
keptn
: working on making datadog-service
compatible with 1.0.0
suraj2
[ ] Create an issue around evaluator transposer function doesn't understand json without indentations
e.g., for json
evalValue before {
"in": ["@faas.com", {
"var": ["email"]
}]
}
evalValue after
"in": ["@faas.com", {
"var": ["email"]
}]
for yaml <- needs more info here
evalValue before {"in":["@faas.com",{"var":["email"]}]}
evalValue after "in":["@faas.com",{"var":["email"]}
Based on print statements just after this line and after this line.
suraj2
suraj2
[ ] Create an issue around evaluator transposer function doesn't understand json without indentations
e.g., for json
evalValue before {
"in": ["@faas.com", {
"var": ["email"]
}]
}
evalValue after
"in": ["@faas.com", {
"var": ["email"]
}]
for yaml <- needs more info here
evalValue before {"in":["@faas.com",{"var":["email"]}]}
evalValue after "in":["@faas.com",{"var":["email"]}
Based on print statements just after this line and after this line.
gave up on suraj2
as an idea because it didn't satisfy my criteria
completed the first PoC for suraj3
fixed lint failure in the CI in https://github.com/open-feature/flagd/pull/206
addressed comment https://github.com/open-feature/flagd/pull/206#discussion_r1058501584
started looking at suraj3
looking at Tests failing after updating Keptn version to 1.0.0 in master branch's integration tests keptn-sandbox/datadog-service#140
[ ] Create an issue around evaluator transposer function doesn't understand json without indentations
e.g., for json
evalValue before {
"in": ["@faas.com", {
"var": ["email"]
}]
}
evalValue after
"in": ["@faas.com", {
"var": ["email"]
}]
for yaml <- needs more info here
evalValue before {"in":["@faas.com",{"var":["email"]}]}
evalValue after "in":["@faas.com",{"var":["email"]}
Based on print statements just after this line and after this line.
Last month's thread: Nov 2022: https://github.com/vadafoss/daily-updates/issues/2
What
This is an issue to update daily status on what I am doing as a member of vadafoss community.
How
Follow this format
やったこと: yatta-koto lit. 'things I did' in Japanese (I just find it sounds closer to what I want to say) Problem (optional): problems I faced Try (optional): what I am trying TODO (optional): things to do WIP (optional): work in progress