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

Dec 2022 #4

Closed
vadasambar opened this issue Dec 1, 2022 · 19 comments
Closed

Dec 2022 #4

vadasambar opened this issue Dec 1, 2022 · 19 comments

Comments

@vadasambar
Copy link
Contributor

Last month's thread:
Nov 2022: #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

## <3-letter-month> <2-letter-day> <4-letter-year>
### やったこと
### Problem
### Try
### TODO
### WIP

やったこと: 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

@vadasambar
Copy link
Contributor Author

vadasambar commented Dec 1, 2022

Dec 1 2022

やったこと

  • 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 handling
  • suraj1: added architecture diagram
  • suraj1: added runner interface
  • suraj1: made corednsrunner conform to runner interface
  • suraj1: added thread safe logging
  • suraj1: replaced custom logger package with default log's log.Default() which provides thread safety
  • suraj1: 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 iteration
  • suraj1: added a doc line explaining how tweaking core-dns Corefile is less risky than it sounds (with screenshots)

WIP

  • Working on suraj1

TODO

Based on print statements just after this line and after this line.

Problem

@vadasambar
Copy link
Contributor Author

vadasambar commented Dec 5, 2022

Dec 5 2022

やったこと

WIP

  • Working on suraj1

TODO

Based on print statements just after this line and after this line.

Problem

@vadasambar
Copy link
Contributor Author

Dec 6 2022

やったこと

  • suraj1: added levelled logging with logrus
  • suraj1: implemented a part of multi-threaded log processing

WIP

  • Working on suraj1
    • looking into a fix for log messages getting duplicated

TODO

Based on print statements just after this line and after this line.

Problem

@vadasambar
Copy link
Contributor Author

vadasambar commented Dec 7, 2022

Dec 7 2022

やったこと

  • suraj1: finish multi-threaded log processing
  • suraj1: 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 stdout
  • suraj1: added suggest-netpol flag
  • suraj1: updated README with extra TODOs
  • suraj1: finished a part of figuring out the data suraj1 needs with just log instead of log . "suraj1:{remote}:{port}:{name}:{rcode}"

WIP

  • Working on suraj1
    • Support figuring out the data suraj1 needs with just log instead of log . "suraj1:{remote}:{port}:{name}:{rcode}"

TODO

Based on print statements just after this line and after this line.

Problem

@vadasambar
Copy link
Contributor Author

Dec 8 2022

やったこと

  • 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

WIP

  • Working on suraj1

TODO

Based on print statements just after this line and after this line.

Problem

@vadasambar
Copy link
Contributor Author

Dec 9 2022

やったこと

  • 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 appear
  • suraj1: renamed the project to kico
  • kico:
    • updated README with user facing information
    • added diagram to explain what kico does
    • added license
    • added .gitignore file
    • added logo
    • made the project public at https://github.com/vadasambar/kico (tweet)

WIP

TODO

Based on print statements just after this line and after this line.

Problem

@vadasambar
Copy link
Contributor Author

vadasambar commented Dec 12, 2022

Dec 12 2022

やったこと

WIP

TODO

Based on print statements just after this line and after this line.

Problem

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

@vadasambar
Copy link
Contributor Author

vadasambar commented Dec 13, 2022

Dec 13 2022

やったこと

WIP

  • keptn: 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 feat: support yaml evaluator open-feature/flagd#206

TODO

Based on print statements just after this line and after this line.

Problem

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

@vadasambar
Copy link
Contributor Author

vadasambar commented Dec 14, 2022

Dec 14 2022

やったこと

  • keptn: fixed timed out waiting for condition issue in integration tests in datadog-service
  • flagd: fixed tests failing when make test is run
  • flagd: addressed all the comments and fixed a bug in the yaml support PR

WIP

  • keptn: working on making datadog-service compatible with 1.0.0

TODO

Based on print statements just after this line and after this line.

Problem

@vadasambar
Copy link
Contributor Author

vadasambar commented Dec 15, 2022

Dec 15 2022

やったこと

  • re-installed my OS to see if it fixes Fix core-dns issue for my local minikube cluster #3 (it fixed CoreDNS timeouts but I am not able to access the internet from pods. DNS lookup on external sites like google.com works)
  • spent some time debugging in-pod internet access (details from here)

WIP

  • keptn: working on making datadog-service compatible with 1.0.0

TODO

Based on print statements just after this line and after this line.

Problem

@vadasambar
Copy link
Contributor Author

vadasambar commented Dec 16, 2022

Dec 16 2022

やったこと

WIP

  • keptn: working on making datadog-service compatible with 1.0.0

TODO

Based on print statements just after this line and after this line.

Problem

@vadasambar
Copy link
Contributor Author

vadasambar commented Dec 19, 2022

Dec 19 2022

やったこと

WIP

  • keptn: working on making datadog-service compatible with 1.0.0
  • working on refining my schedule

TODO

Based on print statements just after this line and after this line.

Problem

@vadasambar
Copy link
Contributor Author

vadasambar commented Dec 20, 2022

Dec 20 2022

やったこと

WIP

  • keptn: working on making datadog-service compatible with 1.0.0
  • blogposts

TODO

Based on print statements just after this line and after this line.

Problem

@vadasambar
Copy link
Contributor Author

vadasambar commented Dec 21, 2022

Dec 21 2022

やったこと

WIP

  • keptn: working on making datadog-service compatible with 1.0.0
  • blogposts

TODO

Based on print statements just after this line and after this line.

Problem

@vadasambar
Copy link
Contributor Author

vadasambar commented Dec 22, 2022

Dec 22 2022

やったこと

WIP

  • keptn: working on making datadog-service compatible with 1.0.0
  • blogposts: working on corefile-poc
  • blogposts: gathering info for blogpost

TODO

Based on print statements just after this line and after this line.

Problem

@vadasambar
Copy link
Contributor Author

vadasambar commented Dec 26, 2022

Dec 26 2022

やったこと

WIP

  • keptn: working on making datadog-service compatible with 1.0.0
  • planning

TODO

Based on print statements just after this line and after this line.

Problem

@vadasambar
Copy link
Contributor Author

vadasambar commented Dec 27, 2022

Dec 27 2022

やったこと

WIP

TODO

Based on print statements just after this line and after this line.

Problem

@vadasambar
Copy link
Contributor Author

vadasambar commented Dec 28, 2022

Dec 28 2022

やったこと

  • added boilerplate for suraj2

WIP

TODO

Based on print statements just after this line and after this line.

Problem

@vadasambar
Copy link
Contributor Author

vadasambar commented Dec 29, 2022

Dec 29 2022

やったこと

WIP

TODO

Based on print statements just after this line and after this line.

Problem

@vadasambar vadasambar mentioned this issue Jan 3, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant