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.

Sign up for GitHub

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

Jump to bottom

Nov 2022 #2

Closed
vadasambar opened this issue Nov 3, 2022 · 22 comments
Closed

Nov 2022 #2

vadasambar opened this issue Nov 3, 2022 · 22 comments
Labels
daily-updates

Comments

@vadasambar
Copy link
Contributor

vadasambar commented Nov 3, 2022 •
edited
Loading

Last month's thread:
Oct 2022: #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
Copy link
Contributor Author

Nov 1 2022

やったこと

WIP

Try

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

TODO

Problem

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

@vadasambar
Copy link
Contributor Author

Nov 2 2022

やったこと

WIP

Try

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

TODO

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
    image
    image

@vadasambar
Copy link
Contributor Author

vadasambar commented Nov 3, 2022 •
edited
Loading

Nov 3 2022

やったこと

WIP

Try

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

TODO

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
    image
    image
  • 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
Copy link
Contributor Author

Nov 4 2022

やったこと

WIP

Try

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

TODO

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
    image
    image
  • 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
Copy link
Contributor Author

vadasambar commented Nov 4, 2022 •
edited
Loading

Nov 4 2022

やったこと

WIP

Try

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

TODO

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
    image
    image
    • turns out my core-dns is not working properly. I created a fresh new minikube cluster without lifecycle-controller and see the same problem.

image

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

@vadasambar
Copy link
Contributor Author

vadasambar commented Nov 7, 2022 •
edited
Loading

Nov 7 2022

やったこと

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

WIP

Try

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

TODO

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
    image
    image
    • turns out my core-dns is not working properly. I created a fresh new minikube cluster without lifecycle-controller and see the same problem.

image

  • Not feeling well today either :(

@vadasambar
Copy link
Contributor Author

Nov 8 2022

  • Holiday

@vadasambar
Copy link
Contributor Author

vadasambar commented Nov 9, 2022 •
edited
Loading

Nov 9 2022

やったこと

WIP

Try

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

TODO

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
    image
    image
    • turns out my core-dns is not working properly. I created a fresh new minikube cluster without lifecycle-controller and see the same problem.

image

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

@vadasambar
Copy link
Contributor Author

vadasambar commented Nov 10, 2022 •
edited
Loading

Nov 10 2022

やったこと

WIP

TODO

Problem

@vadasambar
Copy link
Contributor Author

vadasambar commented Nov 11, 2022 •
edited
Loading

Nov 11 2022

やったこと

WIP

TODO

Problem

@vadasambar
Copy link
Contributor Author

vadasambar commented Nov 14, 2022 •
edited
Loading

Nov 14 2022

やったこと

WIP

TODO

Problem

@vadasambar
Copy link
Contributor Author

vadasambar commented Nov 15, 2022 •
edited
Loading

Nov 15 2022

やったこと

WIP

TODO

Problem

@vadasambar
Copy link
Contributor Author

vadasambar commented Nov 16, 2022 •
edited
Loading

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 Fix core-dns issue for my local minikube cluster #3 (comment)
  • 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

TODO

Problem

@vadasambar
Copy link
Contributor Author

vadasambar commented Nov 17, 2022 •
edited
Loading

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 (Fix core-dns issue for my local minikube cluster #3). Makes me think there is something really broken about my docker or my host machine.
  • add fix for yaml -> json conversion in flagd open-feature/flagd@c5c8bc9 . Turns out the evaluator transposer function doesn't understand json without indentations

WIP

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

@vadasambar
Copy link
Contributor Author

vadasambar commented Nov 18, 2022 •
edited
Loading

Nov 18 2022

やったこと

WIP

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

@vadasambar
Copy link
Contributor Author

vadasambar commented Nov 21, 2022 •
edited
Loading

Nov 21 2022

やったこと

WIP

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

@vadasambar
Copy link
Contributor Author

vadasambar commented Nov 22, 2022 •
edited
Loading

Nov 22 2022

やったこと

WIP

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

@vadasambar
Copy link
Contributor Author

vadasambar commented Nov 23, 2022 •
edited
Loading

Nov 23 2022

やったこと

WIP

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

@vadasambar
Copy link
Contributor Author

vadasambar commented Nov 24, 2022 •
edited
Loading

Nov 24 2022

やったこと

WIP

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

@vadasambar
Copy link
Contributor Author

vadasambar commented Nov 28, 2022 •
edited
Loading

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

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

Problem

@vadasambar
Copy link
Contributor Author

vadasambar commented Nov 29, 2022 •
edited
Loading

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

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

Problem

@vadasambar
Copy link
Contributor Author

vadasambar commented Nov 30, 2022 •
edited
Loading

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

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

Problem

@vadasambar vadasambar mentioned this issue Dec 1, 2022
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
daily-updates
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@vadasambar