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 worked, I was still receiving some “undirect” errors from my server side. I must confess that at this point, I was so overwhelmed and discouraged because it seems I have spent a whole week on the same issue, which is not a good sign. However, my manager said that unlike other teams, my team focuses on infra and not just the implementation of the design. I have been working on the deployment setup in order to help me understand the basics behind infra. 

So too, I had a one-and-one informal feedback with my manager today to see where I’m doing well and where I need improvements. He outlined that I should improve the pace at which I work as well as my troubleshooting skills. He suggested that I should always try to figure out the issues before asking for some assistance. He also mention that I shouldn’t compare my project’s timeline to other teams because we are working on totally different projects and structure. It struck me hard but I am looking forward to using this constructive feedback to improve and adjust to the flow of the team, while also developing a great sense of understanding of the tools we are using at my team. Therefore, I intend to dedicate my whole weekend revisiting all the commands and processes we used this week because it will foster my understanding more. 

Comments

Post a Comment

Popular posts from this blog

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