WEEK 3: ENTRY 2

 Today at my internship, it must be said that things are now getting into the nitty gritty. Over the past couple of weeks, I have been setting up environments and learning the Go programming language, but today was a little different. Unlike those weeks, I had the opportunity to get started on my project today. My manager finally introduced me to the milestones or project timeline if you would like to put it that way. I was not expecting him to divide my project into different sections like the way he did. My presumption was that I would be given the main components and be told to develop the project from scratch up to the final product. However, it appeared that just like how the Student Software Developer team at Berea College uses the Agile methodology, my project will be using a similar approach. Instead of Trello, my team uses a dashboard called Jira to assign issues to me. It is a very user-friendly interface, where I can mark my current issue as in-progress, or under review, or done. These features are very vital because I can track my progress, while organizing my tasks in a more diligent way. 


My issue today was called “systemlog-119-kubernetes.” What does this mean? This is the generic way that I will be naming the issues throughout my project. The most important part is the last part, kubernetes because it describes the issue/stage that I am currently working on in my project. Thus, it can be inferred that today I was working on setting up my kubernetes on the cluster for the Continuous Integration/ Continuous Deployment, CI/CD. As part of the surprises today, I was not expecting this issue to be the first part of my project because I thought that deployment was going to be the last part of my project. Well, it is the total opposite. It turns out that the setup is needed because I will be continuously building and deploying simultaneously to allow organizing and shipping my application in a more fast and efficient way. This is a very great insight because I could never have imagined that it will be more efficient and faster this way. 

So too, setting kubernetes to connect with my Gitlab was not as easy and simple as it looks on the documentation. I struggled with the Gitlab pipeline building because whenever I committed and pushed my code, not all cases were passing. I consulted my manager, who suggested that I needed certain permissions. But even after the permissions were granted, a couple more were failing. Thus, I had to go through the documentation one more time to make sure that I was actually doing the right thing.  My build-up was still failing still, so I will have to wait until tomorrow and consult the Kubernetes specialist because time could not permit that today. I must say that I was freaked out but my manager said I should not worry because it does pose a problem when setting this all up at once. Overall, I was happy that I wrote code that was about to be deployed, but at the same time disappointed that it could not get built. 

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