Nov 2022

[vadasambar]

Last month's thread: Oct 2022: https://github.com/vadafoss/daily-updates/issues/1

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]

Nov 1 2022

やったこと

• Tried out open-feature-operator on my local k8s cluster
• https://github.com/open-feature/open-feature-operator/issues/198 was fixed

  WIP

• Reading https://opentelemetry.io/docs/concepts/observability-primer/
• Trying out lifecycle-controller on my local machine
  • Building and deploying the operator and scheduler on my local machine
• Reading about json schema
• Reading about schema

Try

• Try converting the sample SLO in datadog-service into OpenSLO's SLO format

  TODO

• [ ] Upload the logo with license and font information in https://github.com/vadafoss/.github

Problem

• I don't understand what otel does
• I don't understand json schema

[vadasambar]

Nov 2 2022

やったこと

• Read about schema
• Tried out flagd

  WIP

• Reading https://opentelemetry.io/docs/concepts/observability-primer/
• Trying out lifecycle-controller on my local machine
  • Building and deploying the operator and scheduler on my local machine
  • Trying out the operator with released manifests (i.e., using the release images; I am not building the images)
• Reading about json schema
• Started looking into https://github.com/open-feature/flagd/issues/180 (draft PR)

Try

• Try converting the sample SLO in datadog-service into OpenSLO's SLO format

  TODO

• [ ] Upload the logo with license and font information in https://github.com/vadafoss/.github

Problem

• I don't understand what otel does
• I don't understand json schema
• task pods fail to access the code url in my local minikube cluster

[vadasambar]

Nov 3 2022

やったこと

• wrote a question about compare_with in Keptn slack
• created an issue around a question I had in about thresholdMetric and budgetingMethod for thresholdMetric in OpenSLO: https://github.com/OpenSLO/OpenSLO/issues/185
• started a thread for questions around flagd in OpenFeature CNCF slack channel (link)

WIP

• Reading https://opentelemetry.io/docs/concepts/observability-primer/
• Trying to fix the problem with my minikube cluster where task pods fail because of dns resolution
• Trying out lifecycle-controller on my local machine
  • Building and deploying the operator and scheduler on my local machine
  • Trying out the operator with released manifests (i.e., using the release images; I am not building the images)
• Reading about json schema
• Working on https://github.com/open-feature/flagd/issues/180 (draft PR)
• Going through the code for flagd

Try

• Try converting the sample SLO in datadog-service into OpenSLO's SLO format

  TODO

• [ ] Upload the logo with license and font information in https://github.com/vadafoss/.github

Problem

• I don't understand what otel does
• I don't understand json schema
• task pods fail to access the code url in my local minikube cluster
• I don't understand the following in flagd:
  1. Why do we use Source and Fetch in ISync interface (I thought Source would give us the desired state and Fetch would give us the current state of the system but it looks like Source gives us the URL of the file in case of FilePathSync SyncImpl) and pass it down to updateState.
  2. Why do the state Flags have a Source field and why do we compare it with the source fetched from the SyncImpl (FilePathSync under the hood) here ? Started a thread around these questions in OpenFeature CNCF slack channel here

[vadasambar]

Nov 4 2022

やったこと

WIP

• Reading https://opentelemetry.io/docs/concepts/observability-primer/
• Trying to fix the problem with my minikube cluster where task pods fail because of dns resolution
• Trying out lifecycle-controller on my local machine
  • Building and deploying the operator and scheduler on my local machine
  • Trying out the operator with released manifests (i.e., using the release images; I am not building the images)
• Reading about json schema
• Working on https://github.com/open-feature/flagd/issues/180 (draft PR)
• Going through the code for flagd

Try

• Try converting the sample SLO in datadog-service into OpenSLO's SLO format

  TODO

• [ ] Upload the logo with license and font information in https://github.com/vadafoss/.github

Problem

• I don't understand what otel does
• I don't understand json schema
• task pods fail to access the code url in my local minikube cluster
• I don't understand the following in flagd:
  1. Why do we use Source and Fetch in ISync interface (I thought Source would give us the desired state and Fetch would give us the current state of the system but it looks like Source gives us the URL of the file in case of FilePathSync SyncImpl) and pass it down to updateState.
  2. Why do the state Flags have a Source field and why do we compare it with the source fetched from the SyncImpl (FilePathSync under the hood) here ? Started a thread around these questions in OpenFeature CNCF slack channel here

[vadasambar]

Nov 4 2022

やったこと

• tweeted about vscode Error loading workspace error https://twitter.com/_vadasambar/status/1588403390337282049
• wrote a blogpost How to find Project ID and Issue Type ID in Jira without any special permissions https://vadasambar.com/post/misc/how-to-find-project-id-and-issue-type-id-in-jira-without-elevated-any-special-permissions/
• skimmed through the answers to my flagd questions https://cloud-native.slack.com/archives/C03J36ZP020/p1667506037108809

  WIP

• Reading https://opentelemetry.io/docs/concepts/observability-primer/
• Trying to fix the problem with my minikube cluster where task pods fail because of dns resolution
  • The problem is with minikube itself not able to resolve external DNS. I see the problem in a fresh new cluster without lifecycle-controller
• Trying out lifecycle-controller on my local machine
  • Building and deploying the operator and scheduler on my local machine
  • Trying out the operator with released manifests (i.e., using the release images; I am not building the images)
• Reading about json schema
• Working on https://github.com/open-feature/flagd/issues/180 (draft PR)
• Going through the code for flagd

Try

• Try converting the sample SLO in datadog-service into OpenSLO's SLO format

  TODO

• [ ] Upload the logo with license and font information in https://github.com/vadafoss/.github
• [ ] Go through the answers for flagd questions https://cloud-native.slack.com/archives/C03J36ZP020/p1667506037108809 once more, confirm my understanding and go back with additional questions if any

Problem

• I don't understand what otel does
• I don't understand json schema
• task pods fail to access the code url in my local minikube cluster
  • turns out my core-dns is not working properly. I created a fresh new minikube cluster without lifecycle-controller and see the same problem.

• Not feeling well since afternoon. Didn't get much time to spend on flagd.

[vadasambar]

Nov 7 2022

やったこと

• Didn't do much because I am not feeling well today either :(

  WIP

• Reading https://opentelemetry.io/docs/concepts/observability-primer/
• Trying to fix the problem with my minikube cluster where task pods fail because of dns resolution
  • The problem is with minikube itself not able to resolve external DNS. I see the problem in a fresh new cluster without lifecycle-controller
• Trying out lifecycle-controller on my local machine
  • Building and deploying the operator and scheduler on my local machine
  • Trying out the operator with released manifests (i.e., using the release images; I am not building the images)
• Reading about json schema
• Working on https://github.com/open-feature/flagd/issues/180 (draft PR)
• Going through the code for flagd

Try

• Try converting the sample SLO in datadog-service into OpenSLO's SLO format

  TODO

• [ ] Upload the logo with license and font information in https://github.com/vadafoss/.github
• [ ] Go through the answers for flagd questions https://cloud-native.slack.com/archives/C03J36ZP020/p1667506037108809 once more, confirm my understanding and go back with additional questions if any

Problem

• I don't understand what otel does
• I don't understand json schema
• task pods fail to access the code url in my local minikube cluster
  • turns out my core-dns is not working properly. I created a fresh new minikube cluster without lifecycle-controller and see the same problem.

• Not feeling well today either :(

[vadasambar]

Nov 8 2022

• Holiday

[vadasambar]

Nov 9 2022

やったこと

• re-installed minikube (to no avail; it didn't fix the networking issue :,( )
• added my info for Keptn governing board election: created https://github.com/keptn/community/pull/197
• went through the answers for flagd questions https://cloud-native.slack.com/archives/C03J36ZP020/p1667506037108809 (again). Don't have any questions as of now.

  WIP

• Reading https://opentelemetry.io/docs/concepts/observability-primer/
• Trying to fix the problem with my minikube cluster where task pods fail because of dns resolution
  • The problem is with minikube itself not able to resolve external DNS. I see the problem in a fresh new cluster without lifecycle-controller
• Trying out lifecycle-controller on my local machine
  • Building and deploying the operator and scheduler on my local machine
  • Trying out the operator with released manifests (i.e., using the release images; I am not building the images)
• Reading about json schema
• Working on https://github.com/open-feature/flagd/issues/180 (draft PR)
• Going through the code for flagd

Try

• Try converting the sample SLO in datadog-service into OpenSLO's SLO format

  TODO

• [ ] Upload the logo with license and font information in https://github.com/vadafoss/.github
• [x] Go through the answers for flagd questions https://cloud-native.slack.com/archives/C03J36ZP020/p1667506037108809 once more, confirm my understanding and go back with additional questions if any

Problem

• I don't understand what otel does
• I don't understand json schema
• task pods fail to access the code url in my local minikube cluster
  • turns out my core-dns is not working properly. I created a fresh new minikube cluster without lifecycle-controller and see the same problem.

• re-installing minikube doesn't fix core-dns issue

[vadasambar]

Nov 10 2022

やったこと

• created an issue to discuss OpenSLO adoption in Keptn https://github.com/OpenSLO/OpenSLO/issues/187 (slack thread in Keptn here, OpenSLO here)
• Tried converting the sample SLO in datadog-service into OpenSLO's SLO format here
• A part of making json_evaluator composable to support other file types https://github.com/open-feature/flagd/pull/206/commits/7aa703fbafaf5a623261e7abfb2f27c8cc70fc06
• Went through the code for flagd

  WIP

• Reading https://opentelemetry.io/docs/concepts/observability-primer/
• Fixing core-dns issue in minikube https://github.com/vadafoss/daily-updates/issues/3#issuecomment-1311223583
• Trying out lifecycle-controller on my local machine
  • Building and deploying the operator and scheduler on my local machine
  • Trying out the operator with released manifests (i.e., using the release images; I am not building the images)
• Reading about json schema
• Working on https://github.com/open-feature/flagd/issues/180 (draft PR)

TODO

• [ ] Upload the logo with license and font information in https://github.com/vadafoss/.github

Problem

• I don't understand what otel does
• I don't understand json schema
• https://github.com/vadafoss/daily-updates/issues/3

[vadasambar]

Nov 11 2022

やったこと

• replied to weyert https://github.com/OpenSLO/OpenSLO/issues/187#issuecomment-1311300801
• tweeted about shuffle sharding: https://twitter.com/_vadasambar/status/1590966204843577344
• did a part of converting yaml to json approach for flagd yaml evaluator support: https://github.com/open-feature/flagd/pull/206/commits/cef8463a7aff8f48dbc049dcaab86177c3aadd08

  WIP

• Reading https://opentelemetry.io/docs/concepts/observability-primer/
• Fixing core-dns issue in minikube https://github.com/vadafoss/daily-updates/issues/3#issuecomment-1311223583
• Trying out lifecycle-controller on my local machine
  • Building and deploying the operator and scheduler on my local machine
  • Trying out the operator with released manifests (i.e., using the release images; I am not building the images)
• Reading about json schema
• Working on https://github.com/open-feature/flagd/issues/180 (draft PR)
• Working on another blogpost around flagd

TODO

• [ ] Upload the logo with license and font information in https://github.com/vadafoss/.github

Problem

• I don't understand what otel does
• I don't understand json schema
• https://github.com/vadafoss/daily-updates/issues/3

[vadasambar]

Nov 14 2022

やったこと

• Read https://opentelemetry.io/docs/concepts/observability-primer/

• Read about query routing in CoreDNS https://coredns.io/2016/10/13/query-routing/

• Created an issue in minikube repo for core-dns issue in minikube: https://github.com/kubernetes/minikube/issues/15354

• tried yaml->map->json conversion for flagd yaml support

  WIP

• Fixing core-dns issue in minikube https://github.com/vadafoss/daily-updates/issues/3#issuecomment-1311223583

• Trying out lifecycle-controller on my local machine

  • Building and deploying the operator and scheduler on my local machine
  • Trying out the operator with released manifests (i.e., using the release images; I am not building the images)

• Reading about json schema

• Working on https://github.com/open-feature/flagd/issues/180 (draft PR)

• Working on another blogpost around flagd https://github.com/open-feature/flagd/pull/206/commits/8a38e3c5d30dcbaac5f40c01169b329ca092fa02

TODO

• [ ] Upload the logo with license and font information in https://github.com/vadafoss/.github
• [x] Read about query routing in CoreDNS https://coredns.io/2016/10/13/query-routing/
• [ ] Read about how queries are processed in CoreDNS https://coredns.io/2017/06/08/how-queries-are-processed-in-coredns/
• [x] Read more about CoreDNS configuration file https://coredns.io/manual/configuration/

Problem

• I don't understand what otel does
• I don't understand json schema
• https://github.com/vadafoss/daily-updates/issues/3
• I don't understand how CoreDNS processes queries

[vadasambar]

Nov 15 2022

やったこと

• flagd yaml support: cleaned up the code a bit https://github.com/open-feature/flagd/pull/206/commits/9ec8f7e53bf7e1b55bfbf44f0e686f9dbaa5060c

  WIP

• Fixing core-dns issue in minikube https://github.com/vadafoss/daily-updates/issues/3

• Trying out lifecycle-controller on my local machine

  • Trying out the operator with released manifests (i.e., using the release images; I am not building the images)
  • Trying lifecycle-controller in a k3d cluster. lifecycle-controller is not able to schedule a pod with no pre-deployment-task for some reason. Talking in #keptn-app-lifecycle-wg channel on CNCF slack here

• Reading about json schema

• Working on https://github.com/open-feature/flagd/issues/180 (draft PR)

• Working on another blogpost around flagd https://github.com/open-feature/flagd/pull/206/commits/8a38e3c5d30dcbaac5f40c01169b329ca092fa02

  • Looking at json.Unmarshal error when converting yaml config -> json config -> json.Unmarshal

TODO

• [ ] Upload the logo with license and font information in https://github.com/vadafoss/.github
• [ ] Do the TODO in https://github.com/vadafoss/daily-updates/issues/3#issuecomment-1316452258
• [ ] Try building and deploying the lifecycle-toolkit operator and scheduler on my local machine

  Problem

• I don't understand what otel does
• I don't understand json schema
• https://github.com/vadafoss/daily-updates/issues/3
• I don't understand how CoreDNS processes queries

[vadasambar]

Nov 16 2022

やったこと

• Did some more investigation on pods stuck in Pending when trying keptn lifecycle-toolkit. Details in the CNCF slack thread here

• Did the TODO in https://github.com/vadafoss/daily-updates/issues/3#issuecomment-1316452258

• Continued my investigation of CoreDNS issue in minikube (check the issue for more details)

• flagd yaml support: continued debugging why yaml->json-> setState fails

  • seems like something happens in transposeEvaluators here which leads to the problem

    WIP

• Fixing core-dns issue in minikube https://github.com/vadafoss/daily-updates/issues/3

• Trying out lifecycle-controller on my local machine

  • Trying out the operator with released manifests (i.e., using the release images; I am not building the images)
  • Trying lifecycle-controller in a k3d cluster. lifecycle-controller is not able to schedule a pod with no pre-deployment-task for some reason. Talking in #keptn-app-lifecycle-wg channel on CNCF slack here

• Reading about json schema

• Working on https://github.com/open-feature/flagd/issues/180 (draft PR)

• Working on another blogpost around flagd https://github.com/open-feature/flagd/pull/206/commits/8a38e3c5d30dcbaac5f40c01169b329ca092fa02

  • Looking at json.Unmarshal error when converting yaml config -> json config -> json.Unmarshal

TODO

• [ ] Upload the logo with license and font information in https://github.com/vadafoss/.github
• [ ] Try building and deploying the lifecycle-toolkit operator and scheduler on my local machine

  Problem

• I don't understand what otel does
• I don't understand json schema
• https://github.com/vadafoss/daily-updates/issues/3
• I don't understand how CoreDNS processes queries

[vadasambar]

Nov 17 2022

やったこと

• Updated my kubectl and k3d to 1.24.4 because keptn lifecycle-toolkit needs kubernetes version >=1.24

• Tried creating a cluster on kind to see if I face the same issue as k3d when trying to lifecycle-toolkit but kind also has the same CoreDNS problem (https://github.com/vadafoss/daily-updates/issues/3). Makes me think there is something really broken about my docker or my host machine.

• add fix for yaml -> json conversion in flagd https://github.com/open-feature/flagd/pull/206/commits/c5c8bc9157febbb23ffc525138632901c1776293 . Turns out the evaluator transposer function doesn't understand json without indentations

  WIP

• Fixing core-dns issue in minikube https://github.com/vadafoss/daily-updates/issues/3

• Trying out lifecycle-controller on my local machine

  • Trying out the operator with released manifests (i.e., using the release images; I am not building the images)
  • Trying lifecycle-controller in a k3d cluster. lifecycle-controller is not able to schedule a pod with no pre-deployment-task for some reason. Talking in #keptn-app-lifecycle-wg channel on CNCF slack here

• Reading about json schema

• Working on https://github.com/open-feature/flagd/issues/180 (draft PR)

• Working on another blogpost around flagd https://github.com/open-feature/flagd/pull/206/commits/8a38e3c5d30dcbaac5f40c01169b329ca092fa02

  • Looking at json.Unmarshal error when converting yaml config -> json config -> json.Unmarshal

TODO

• [ ] Upload the logo with license and font information in https://github.com/vadafoss/.github
• [ ] Try building and deploying the lifecycle-toolkit operator and scheduler on my local machine

• [ ] Create an issue around evaluator transposer function doesn't understand json without indentations

  • e.g., for json

    {"level":"info","msg":"metrics listening at 8014","time":"2022-11-17T23:51:42+05:30"}
    evalValue {
              "in": ["@faas.com", {
                "var": ["email"]
              }]
        }
    evalValue after 
              "in": ["@faas.com", {
                "var": ["email"]
              }]

  • for yaml <- needs more info here

Problem

• I don't understand what otel does
• I don't understand json schema
• https://github.com/vadafoss/daily-updates/issues/3
• I don't understand how CoreDNS processes queries

[vadasambar]

Nov 18 2022

やったこと

• tweeted about soft-eviction limit in Kubernetes: https://twitter.com/_vadasambar/status/1593457932561051648

• gathered some more info about yaml -> json indentation issue (check the TODO below)

  WIP

• Fixing core-dns issue in minikube https://github.com/vadafoss/daily-updates/issues/3

• Trying out lifecycle-controller on my local machine

  • Trying out the operator with released manifests (i.e., using the release images; I am not building the images)
  • Trying lifecycle-controller in a k3d cluster. lifecycle-controller is not able to schedule a pod with no pre-deployment-task for some reason. Talking in #keptn-app-lifecycle-wg channel on CNCF slack here

• Reading about json schema

• Working on https://github.com/open-feature/flagd/issues/180 (draft PR)

• Working on another blogpost around flagd https://github.com/open-feature/flagd/pull/206/commits/8a38e3c5d30dcbaac5f40c01169b329ca092fa02

  • Looking at json.Unmarshal error when converting yaml config -> json config -> json.Unmarshal

TODO

• [ ] Upload the logo with license and font information in https://github.com/vadafoss/.github
• [ ] Try building and deploying the lifecycle-toolkit operator and scheduler on my local machine

• [ ] 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.

Problem

• I don't understand what otel does
• I don't understand json schema
• https://github.com/vadafoss/daily-updates/issues/3
• I don't understand how CoreDNS processes queries

[vadasambar]

Nov 21 2022

やったこと

• watched Keptn lifecycle toolkit in a nutshell: https://www.youtube.com/watch?v=K-cvnZ8EtGc
• downloaded new LTS of Xubuntu
• flagd yaml support: refactored code https://github.com/open-feature/flagd/pull/206/commits/e29e894e85b401cbd2e02c75c97d8b34718709f7

WIP

• Fixing core-dns issue in minikube https://github.com/vadafoss/daily-updates/issues/3
• Trying out lifecycle-controller on my local machine
  • Trying out the operator with released manifests (i.e., using the release images; I am not building the images)
  • Trying lifecycle-controller in a k3d cluster. lifecycle-controller is not able to schedule a pod with no pre-deployment-task for some reason. Talking in #keptn-app-lifecycle-wg channel on CNCF slack here
• Reading about json schema
• Working on https://github.com/open-feature/flagd/issues/180 (draft PR)
• Working on another blogpost around flagd https://github.com/open-feature/flagd/pull/206/commits/8a38e3c5d30dcbaac5f40c01169b329ca092fa02
  • Looking at json.Unmarshal error when converting yaml config -> json config -> json.Unmarshal

TODO

• [ ] Upload the logo with license and font information in https://github.com/vadafoss/.github
• [ ] Try building and deploying the lifecycle-toolkit operator and scheduler on my local machine

• [ ] 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.

Problem

• I don't understand what otel does
• I don't understand json schema
• https://github.com/vadafoss/daily-updates/issues/3
• I don't understand how CoreDNS processes queries

[vadasambar]

Nov 22 2022

やったこと

• tried lifecycle-toolkit with example podtatohead manifests on my local machine with release manifests (I am not building the images)
• made flagd yaml support PR ready for review: https://github.com/open-feature/flagd/pull/206/files

  WIP

• Trying building and deploying the lifecycle-toolkit operator and scheduler on my local machine
• Fixing core-dns issue in minikube https://github.com/vadafoss/daily-updates/issues/3
• Reading about json schema
• Working on another blogpost around flagd https://github.com/open-feature/flagd/pull/206/commits/8a38e3c5d30dcbaac5f40c01169b329ca092fa02
  • Looking at json.Unmarshal error when converting yaml config -> json config -> json.Unmarshal

TODO

• [ ] Upload the logo with license and font information in https://github.com/vadafoss/.github

• [ ] 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.

Problem

• I don't understand what otel does
• I don't understand json schema
• https://github.com/vadafoss/daily-updates/issues/3
• I don't understand how CoreDNS processes queries

[vadasambar]

Nov 23 2022

やったこと

• read http://json-schema.org/understanding-json-schema/basics.html
• attended Keptn community meeting
• flagd yaml evaluator support: fixed lint error and re-worded a code comment

  WIP

• Reading https://www.digitalocean.com/community/tutorials/how-to-inspect-kubernetes-networking
• Trying building and deploying the lifecycle-toolkit operator and scheduler on my local machine
• Fixing core-dns issue in minikube https://github.com/vadafoss/daily-updates/issues/3
• Working on another blogpost around flagd https://github.com/open-feature/flagd/pull/206/commits/8a38e3c5d30dcbaac5f40c01169b329ca092fa02

TODO

• [ ] Upload the logo with license and font information in https://github.com/vadafoss/.github

• [ ] 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.

Problem

• I don't understand what otel does
• https://github.com/vadafoss/daily-updates/issues/3
• I don't understand how CoreDNS processes queries

[vadasambar]

Nov 24 2022

やったこと

• worked out a plan to implement suraj1
• added basic skaffold/boilerplate for suraj1
• Learned about CoreDNS's log plugin https://coredns.io/plugins/log/

  WIP

• Reading https://www.digitalocean.com/community/tutorials/how-to-inspect-kubernetes-networking
• Looking for a way to track incoming traffic to the pod (tcpdump might be useful)
• Trying building and deploying the lifecycle-toolkit operator and scheduler on my local machine
• Fixing core-dns issue in minikube https://github.com/vadafoss/daily-updates/issues/3
• Working on another blogpost around flagd https://github.com/open-feature/flagd/pull/206/commits/8a38e3c5d30dcbaac5f40c01169b329ca092fa02
• Learning about CoreDNS's log plugin https://coredns.io/plugins/log/
• Started working on suraj1

TODO

• [ ] Upload the logo with license and font information in https://github.com/vadafoss/.github

• [ ] 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.

Problem

• I don't understand what otel does
• https://github.com/vadafoss/daily-updates/issues/3
• I don't understand how CoreDNS processes queries

[vadasambar]

Nov 28 2022

やったこと

• fixed clientset in suraj1
• found a way to show logs for core-dns pods using client-go in suraj1
• added a part of code for figuring out Service FQDNs from the pod name passed as an argument
• added code to figure out current namespace from the kubeconfig

WIP

• working on suraj1

TODO

• [ ] Trying building and deploying the lifecycle-toolkit operator and scheduler on my local machine
• [ ] Fixing core-dns issue in minikube https://github.com/vadafoss/daily-updates/issues/3
• [ ] Working on another blogpost around flagd https://github.com/open-feature/flagd/pull/206/commits/8a38e3c5d30dcbaac5f40c01169b329ca092fa02
• [ ] Finish reading https://www.digitalocean.com/community/tutorials/how-to-inspect-kubernetes-networking
• [ ] Upload the logo with license and font information in https://github.com/vadafoss/.github

• [ ] 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.

Problem

• I don't understand what otel does
• https://github.com/vadafoss/daily-updates/issues/3
• I don't understand how CoreDNS processes queries

[vadasambar]

Nov 29 2022

やったこと

• suraj1: make connection records unique and print them since there are many duplicates because the same fromPod accesses the toPod multiple times
• suraj1: finish the code to create fqdns out of toPod Service names
• Wrote a new blogpost: https://vadasambar.com/post/go/converting-yaml-to-json-without-struct/
• suraj1: add code to suggest a NetworkPolicy (needs more testing)

  WIP

• Working on suraj1

TODO

• [ ] Trying building and deploying the lifecycle-toolkit operator and scheduler on my local machine
• [ ] Fixing core-dns issue in minikube https://github.com/vadafoss/daily-updates/issues/3
• [ ] Working on another blogpost around flagd https://github.com/open-feature/flagd/pull/206/commits/8a38e3c5d30dcbaac5f40c01169b329ca092fa02
• [ ] Finish reading https://www.digitalocean.com/community/tutorials/how-to-inspect-kubernetes-networking
• [ ] Upload the logo with license and font information in https://github.com/vadafoss/.github

• [ ] 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.

Problem

• I don't understand what otel does
• https://github.com/vadafoss/daily-updates/issues/3
• I don't understand how CoreDNS processes queries

[vadasambar]

Nov 30 2022

やったこと

• suraj1: wrote code to tail coredns pod logs
• suraj1: wrote a piece of code to get coredns Corefile ConfigMap
• suraj1: wrote code to wait for suraj1 log to appear (gave up on writing to Corefile ConfigMap)
• suraj1: added description and usage info in cobra command
• suraj1: abstracted out code into separate functions

  WIP

• Working on suraj1

TODO

• [ ] Trying building and deploying the lifecycle-toolkit operator and scheduler on my local machine
• [ ] Fixing core-dns issue in minikube https://github.com/vadafoss/daily-updates/issues/3
• [ ] Working on another blogpost around flagd https://github.com/open-feature/flagd/pull/206/commits/8a38e3c5d30dcbaac5f40c01169b329ca092fa02
• [ ] Finish reading https://www.digitalocean.com/community/tutorials/how-to-inspect-kubernetes-networking
• [ ] Upload the logo with license and font information in https://github.com/vadafoss/.github

• [ ] 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.

Problem

• I don't understand what otel does
• https://github.com/vadafoss/daily-updates/issues/3
• I don't understand how CoreDNS processes queries