Reflection on kubernete usage
- 2 minutes read - 266 wordsToday I explained the current infrastructure fleet configurations to our devops team, I have the thought to make a reflection on the things or lessons I learnt in the past and think about what should I do in the next.
The technologies and tools I used in my projects is as following. There are still a lot of things to learn considering the list in my list and the huge ecosystem of kubernetes.
-
kubernetes
-
kubectl
-
kustomize
-
cert-manager
-
argo-cd
-
istio
-
godaddy-webhook
-
eksctl
-
elk(filebeat, elasticsearch, kibinan)
-
metrics-server
-
sealed-secrets
-
action-runner
-
helm
-
argo-workflows
-
argo-events
-
jsonpatch
-
jsonpath
-
jq
-
yq
-
letsencrypt
-
ACME (HTTP01, DNS1)
-
dapr
In the past, I studied Oracle database and passed the Oracle DBA certificate. When I lead a DBA team for several 24x7 projects, I noticed the knowledges and skills needed to fullfil the role are much more than the certificates such as OS, license management, license terms, storage, SAN, interconnection between SAN and servers, volume manages etc. This time, I didn’t consider to attend the kubernetes exams considering my past experience leading a DBA team. The actual usage kubernetes involved more than the curriculum in the exams.
When systems move to kubernetes, many things change as well and they need to be done differently. I think the whole ecosystem is evolving around this and try to make the process smoother and less painful. However the ecosystem evolve so fast, there are fractions among them. same functionalities may have serveral implementation with their quirks. Those are not covered in the exams as well. The knowledge holes of this needed to be filled by one’s own researches and studies.