WEEK 4: ENTRY 2

 Today at my internship, I worked on the configuration of my Kubernetes deployment. A Kubernetes Deployment is simply “used to tell Kubernetes how to create or modify instances of the pods that hold a containerized application.” My Kubernetes deployment was done  through the Gitlab CI/CD Pipeline, which is not as easy and simple as I initially thought.  I have been working on it for two days before it successfully passed all the test cases today. Prior to today, my manager and I were copying a codebase from a Github repo project that was similar to what my project is based on: Using GET Request to request data from an API.  Although the codebase we were referencing looks all great and easy to read and understand, I must say that it was not a good idea to copy it. Partly because we had to change many lines of code in that codebase to customize it to our desired configuration. This methodology has taken us several commits and pushes to GitLab before it finally worked today. 


Not only did it pose a lot of bug issues and trials and errors, it also gave me less time to understand the codebase before making changes to it. So too, I was merely a driver, which means I was only taking instructions to execute. Sometimes, my manager takes some time to explain the main concept, but I was mainly focusing on executing the commands that I was told rather than retaining all that was thrown at me. I approached it this way because I thought the process was a one-time execution and I would not have to worry about using those commands and concepts. It turns out that I was totally wrong because whenever my GitLab pipeline test fails, I was expected to read the error message and troubleshoot it. Most error messages were similar, but because I was not retaining the concepts, I struggled to fix them. I was so mad over my actions because my manager told me at some point that we fixed this kind of error yesterday, so I expected you to remember. 


Besides, the Kubernetes deployment joins my project files and some kubernetes configuration files that were needed to make sure that my continuous integration/continuous deployment pipeline passes. The kubernetes deployment files contain yaml, sh, and yaml files. And since I was not retaining the concepts that I was introduced to during the codebase refactoring, I had to struggle understanding that the way we pass .sh variable values’ indices is quite different from programming languages, say Python. .sh variable values’ indices start from 1 unlike how we start indexing from 0 with Python. The mistake of just running the commands and refactoring the original codebase without retaining or understanding the concepts cost me a lot today. I had to spend some time reading and trying to remember what we did yesterday. Thus, in the future, I intend to not just follow the instructions blindly, but to rather understand the processes and concepts that I am being introduced to. Also, I intend to take notes and revisit them after my work day each day henceforth.


Comments

Post a Comment

Popular posts from this blog

WEEK 4: ENTRY 3

  Today at my internship, I was assigned the issue of troubleshooting why my GET request Golang code is unable to generate the data from my http server. Since it was a combination of k8s deployment and Golang go, it was trickier and harder than I envisioned. The k8s was mainly used to orchestrate the objects that are needed to generate keytab from my pods. After several debugging: comparing and contrast the referred file I used as a source code coupled with looking up the errors on Stack flow (suggested me to delete my deployment and redeployed), I was still unable to fix the issue. Partly was because I did not understand what the error message was pointing at. Thus, I had to consult a member of the k8s team, who figured out that my deployment.yaml file was missing some configurations that needed to generate my key-tab. Simply, I needed the key-tab in order to be able to make the HTTP Get Request get my desired data.   Although the recommended solution from my consultation wor...
Read more

WEEK 6: ENTRY 3

  At my internship today, I continued unmarshalling the Json data I got back from Big Query API. Having tried replicating the data on the Go playground and using the Go unmarshall function yesterday, I did develop a better understanding of the json structure. I used Go’s struct to do the unmarshalling. Unlike the json data I got from my query, the documentation’s json data does not have any schema metadata and so I thought the same approach would not work. Little did I know that the schema data can be ignored when unmarshalling json data and that you can only concentrate on the part of the Json you want to unmarshall. When I consulted my buddy, he hopped on a zoom call with me and we did pair programming. I was the driver while he was the navigator, basically explaining what we were doing because he has more knowledge on Go and Json data manipulation. Working with him gave me more skills and confidence in what I was doing. He helped in not just using the Go struct, but also in tryi...
Read more

WEEK 7: ENTRY 1

  It sometimes feels like we are not good enough when our tries don’t work. Well at my internship today, I worked on resolving the json unmarshalling issue I was stuck with last Friday. After several back-and-forth consultations with my buddy and manager, I finally got a better understanding of how they wanted me to present the data. Basically, the data should be in a simple json array that could be manipulated easier. This is because as the json comes in key:pair format, I would need to extract all the keys and use those keys to send an HTTPS request to Elasticsearch Rest API.  Even though the approach was well defined and clear to me, I still struggled to implement it using the Golang Struct and Maps. One of the obstacles I had was because after unmarshalling the json data, the output was in a Golang interface type, which was not iterable like say a slice. A Golang slice is the equivalent  of a python array. Therefore, to overcome that barrier, I created an empty slice ...
Read more