InfraCloud help modernize applications and infrastructure with cloud-native technologies for resilience & scalability

InfraCloud Technologies

infracloudtechnologies

While preparing for the CNCF’s CKAD or CKA certification, there could be numerous doubts, which exam to appear first, what resources to refer to, what common mistakes to avoid, etc.. Especially, if you don’t have previous knowledge or hands-on experience with Kubernetes, this could be a tough situation to be in. At InfraCloud, engineers are highly encouraged to appear for these exams and get certified. This blog post is a collaborative effort from the recently certified Infranauts to share all the insights straight from - before registering for the exam to the next steps after clearing the exam successfully. With around 50% developers CKA and CKAD certified, we share our experiences, study material, Do’s and Dont’s, FAQ, etc. about the exam. If you’re willing to start your journey in Kubernetes and are aiming to be certified, you will find this blog helpful. Shall we begin then? CKA vs CKAD certification! Which one should I take first? First things first! Before thinking of CKA or CKAD, having knowledge of Kubernetes basics is crucial. If you’re a complete newbie and do not know what on earth is Kubernetes? It is highly recommended to get familiar with the basic concepts of Kubernetes before you book your exam dates. If you’re starting out your journey into the cloud native and Kubernetes world, you can opt for course to get yourself comfortable with the basics of Kubernetes. Although one might still get confused about which exam one should go for first - CKA or CKAD? Is CKA harden than CKAD? And what is the exact difference in terms of exam curriculum and the difficulty level of both exams? To keep things simple, you can look at it this way: Kubernetes For The Absolute Beginner - Hands On by Mumshad Mannambeth is for those interested in the design, build & configuration of cloud native applications using Kubernetes. CKAD While exam is mainly for those, who want to build, manage the Kubernetes infrastructure. CKA Some of us started digging deeper over the internet and eventually find out that CKAD is broadly a subset of CKA. A few Infranauts decided to prepare for CKAD first and then for CKA, as they were ultimately aiming to gain all the possible knowledge around Kubernetes. It eventually turned out to be the right decision as CKAD also helped them improve speed and muscle memory over Kubernetes commands, which is critical for both exams. This helped them a lot in the CKA exam as most of us managed to complete almost all questions with 20-30 mins still left with us to solve the only couple of complex questions that had been flagged and skipped for later. Study material Many Infranauts have taken the CKAD course by Mumshad Mannambeth available on Udemy. After clearing CKAD with that course, some of us also opted for another CKA course for the CKA certification. The primary reason to go through these courses was the number of recommendations it had from the community. Few of the certified Infranauts had also watched a few of his videos on YouTube and always found it easy to follow. So yes, these courses are highly recommended to anyone planning to get CKA / CKAD certified. As you might guess, this is not the only course in the market - there are plenty of them. Study materials are available in other formats like blogs, GitHub Repos, YouTube videos containing different scenario-based practice questions/answers. You may choose at your own will like this one that some of us followed from Medium for the CKAD exam. You should also check out the video by Harshit Singhvi on exam experience and tips on YouTube. At the end of the day, what matters the most is how much time you spend practicing different scenarios. We can’t emphasize enough how important the labs are. Irrespective of the course you take, they all have labs and mock tests. Don’t skip any of them. They are all equally important. Mistakes to avoid Don’t get trapped into registering the exam date six months in advance and then start the actual study. If you’re not fully prepared by the time nearing your exam date, you might get nervous and feel to postpone the exam to study more and more. This cycle never ends. Even if you started late, don’t be inconsistent with your study. One would study one day and skip for another two days. Don’t do that. Be consistent and stick to a schedule. Do NOT skip labs. One might get trapped thinking it would be nice to go through all the lectures at once and then come back to labs. Nope, not a good idea! Completing a course is one thing. But you won’t know how much you understand until you take the mock tests. So don’t avoid taking them until you’re left with last 3-4 days to study. Don’t keep postponing till the last day of validity of your particular exam voucher. If you delay it till the last day of voucher, and if you couldn’t clear the exam on the first attempt, you’ll leave no retake option. So, prepare, practice, and appear for the exam at least a week before the last date. Do’s for CKA and CKAD Certification The most obvious one - practice, practice, and some more practice. Make it a habit to take a lecture and do the lab that follows with it. If possible, complete the courses first, and when you think you are ready for the exam, go ahead and apply for the certification. This gives you a year after you have completed the course. It is enough time to test your skills. The discussions in the Slack forum of KodeKloud CKA and CKAD group also helped us play and try different variety of questions/scenarios during preparation. So, keep an eye on it. Plus, feel free to seek suggestions from the forum in case of any doubts. Practice with complete commands instead of binding an alias for like everything. In each mock test, try to complete the test 15 min before the deadline. This gives you time to revisit the questions. Monitor your time as you practice. Do the labs and mock tests repeatedly (at least three times). Identify what is slowing you down and plan accordingly. On the day of the exam, make sure to clean your desk and not have anything (apart from a transparent water bottle). On the exam day, keep an alternative internet source handy in case of Wi-Fi internet goes down (trust me, it happens more than you believe) In the exam, if you analyze that any particular question is going to take more than 6-7 mins to solve, flag/mark it to solve for later and come back once you solve the rest. Don’ts for CKA and CKAD Certification Don’t overwhelm yourself with an alias for everything. Don’t panic if you are stuck; simply flag/mark the particular question and move ahead. You can always come back to it later. Don’t give the exam on the last day (like many folks do). At the time of the exam, other than your system, don’t have anything on the table. Don’t overkill yourself with Kubernetes the Hard Way unless you have time. Don’t ignore the candidate handbook. Read it and follow the instructions. Final tips & tricks Final tips & tricks The exam clusters are set up with mostly in the Ubuntu environment. kubeadm Do check out the details and practice accordingly. CKA and CKAD environment Try to use auto-completion while running Kubernetes commands. It will be much more helpful and effective in the exam. Here is how you can set up the auto-completion: $ k= alias 'kubectl' $ <(kubectl completion bash) source $ >> ~/.bashrc echo "source <(kubectl completion bash)" $ complete -F __start_kubectl k The above commands can be found in the . And, you can use them (some of us have used them ourselves), as they are listed in the docs. kubectl cheat sheet yes As you do your labs, you must search the docs. Especially for resources like PV, PVC, Ingress, RBAC resources etc. This trains your brain to remember the correct links, in case you need to refer to the docs during the exam. Saves a lot of time. If you have time during preparation, take both the courses CKA and CKAD. This will surely help. Get familiar with vi or vim. We’re not sure if nano will be available, so prefer vi or vim. GNU Emacs is available but the usual key bindings like C-p, C-n don’t work inside most of the browsers. You don’t need tmux or screen, if you have saved your aliases or other bash settings in ~/.bashrc. Get used to pasting text using the mouse middle/center key. The mouse secondary key doesn’t work in the exam environment. Useful commands Here is a list of commands that you will definitely need during practice or exam: nonextensive # list running processes $ ps -aux # search string the output for in $ ps -aux | grep -i 'string' # search multiple expressions the output (exp can be plain a string too) for in $ ps -aux | grep -e -e 'exp-one' 'exp-two' # get details about network interfaces $ ifconfig # list network interfaces and their IP address $ ip a # get the route details $ ip r # check service status and also show logs $ systemctl status kubelet # restart a service $ systemctl restart kubelet # reload the service daemon, you changed the service file if $ systemctl daemon reload # detailed logs of the service $ journalctl -u kubelet # list out ports, protocol and what processes are listening on those ports $ netstat -tunlp How to book the CKA and CKAD exams? You can book the exams from page. Linux Foundation Exam experience CKAD exam experience On the exam day, try to log in 15 minutes before the exam. Proctor will make sure to follow their process to check your ID proof as well as room, your desk. The entire process should normally take 15-20 minutes or more, but don’t panic as the proctor will only start the exam after all the verification process is complete and you’re comfortable to start the exam. CKAD exam questions are comparatively quite straightforward, but it would be a race against time, as some of the questions will contain many Kubernetes objects creation and if you fail to create any, would take more time to debug and understand them. CKA exam experience The exam experience was a little rollercoaster ride for some of us, as we lost internet connection almost 4-5 times during the exam. Each time after the connection reset, we made sure that previous work is not lost by checking the answers to some of the previously solved questions. Proctor typically makes sure to hold your exam (to avoid time loss) and stop the timer and resume it once your connection is restored. But this whole experience can make you nervous during and after the exam (with a nightmare of all work might be lost, resulting in failure). Few of us had practiced enough, so we were able to solve 14-15 out of 17 questions in 1.5 hours and spend the rest of almost 30 minutes to try to solve the 2-3 questions which we initially found challenging and had marked (and parked) to solve later. FAQs for the CKA and CKAD Certification Some of the questions which crossed our minds while preparing (apart from the ones available on the ). official FAQ page of the Linux Foundation Yes, we are allowed to use dual monitors 1) Can I use dual monitors in the exam? Yes, we are allowed to use them as long as they are referring to official Kubernetes documentation allowed for the exam 2) Can I bookmarks link and use them during the exam? Results are typically out after the exact 24 hours of your examination but can get delayed till 36 hours in some cases. In case of delay, you can raise a for the same. 3) When would the result be out after the exam? support ticket Yes, your work gets autosaved at frequent intervals. 4) Does our work remains saved in case of internet connectivity loss? Automated scripts most probably evaluate them. 5) Who evaluates the CKA / CKAD / CKS exams? Humans or bots? Focus on solving all the questions and scenarios that you had found difficult in 1st attempt and the topic you found the first time during your exam. 6) What should I be more prepared for if I get failed in my 1st attempt? You can raise a for the same. 7) Whom to reach out in case of any challenges faced during the exam? support ticket Once you’re able to solve all the labs and mock tests in less than 40-45 minutes, consider you’re ready for the exam. You can also book them using the discounts available (up to 50%) during the KubeCon event and Black Friday or Cyber Monday deal sale from Linux Foundation. 8) What is the best time to book the CKA and CKAD exams? Both CKA and CKAD exams are of 2 hours once you start the exam (excluding the time required for identity verification with the proctor before you start the exam). 9) What is the duration of the exam? Both CKA and CKAD contain 17-19 questions (approximately). 10) How many questions does CKAD or CKA exam contain? Questions’ weightage varies from 2% to 13% based on the work required to solve them. 11) What is the minimum or maximum weightage of any question in the exam? Yes, a progress bar available on the top-left corner of your exam console. 12) Is a digital watch available on the exam console? You can practice/focus on the JSON expressions captured as part of the , but don’t spend too much time mastering JSON expressions from an exam perspective. 13) Do we need to be more fluent in jsonpath syntax without any external website reference during the exam? cheat sheet Personally, many of us felt the actual exam was comparatively easier than Killer.sh simulator. 14) Are exam questions as difficult as one available on the killer.sh simulator? Practice and prepare well :) Reference links to useful materials: Bookmark Import the Kubernetes official documentation bookmark into your chrome/any browser as it will help you search required topics faster during the exam. https://github.com/reetasingh/CKAD-Bookmarks Recommended articles before the Exam: Go through the below articles at least once before the exam, as they contain some of the tricky topics from CKA exam perspective. Resize a PVC Kubernetes Volume Basics: emptyDir and PersistentVolume Sidecar containers Ingress Network policy Practice material (Now ) CKAD exercises Repo K8s Practice Training Repo KodeKloud Killer.sh available with exam registration Conclusion Though one finds the Kubernetes exams comparatively hard as these are practical exams, if you practice enough and take note of the above points, you can clear them easily; irrespective of whether you have had previous experience with Kubernetes or not. We hope this helps you plan and prepare better for the CKA and CKAD certification exam. We will be happy to answer any other questions. Connect with us We hope the article was useful. Feel free to drop us a line or share your exam experiences with any one of the authors: , , , , and . Ninad Desai Gaurav Gahlot Yatish Sharma Jaiganesh Karthikeyan Dhruv Mewada All the best folks :)

CKAD and CKA Certifications: Which to Take First and How to Prepare

Let’s talk about Kubernetes security As Kubernetes continues to grow in adoption, it is important for us to know how to secure it. In a dynamic infrastructure platform such as Kubernetes, detecting and addressing threats is important but also challenging at the same time. Falco, the open source cloud native runtime security project, is one of the leading open source Kubernetes threat detection engines. Falco was created by Sysdig in 2016 and is the first runtime security project to join CNCF as an incubation-level project. Falco detects unexpected application behaviour and alerts on threats at runtime. Why is it difficult? Security is one of the harder challenges of running Kubernetes according to . The reason it is difficult is that there are multiple moving layers in a cloud native stack, hence operators may not focus on security early on. Another contributor is that some distributions of Kubernetes may not be secure by default, contrary to what operators assume. this analysis Prevention and Detection Information security is a process that moves through phases building and strengthening itself along the way. Security is a journey, not a destination. Although the Information Security process has multiple strategies and activities, we can group them all into three distinct phases - prevention, detection, and response. Preventive measures Preventive measures include having proper access control, authentication and authorization in place. No matter what level of protection a system may have, it will get compromised given a greater level of motivation and skill. There is no foolproof “silver bullet” security solution. A defense in-depth strategy should be deployed so when each layer fails, it fails safely to a known state and sounds an alarm. The most important element of this strategy is timely detection and notification of a compromise. Detective measures An example of detective measures includes sending logs from security and network devices like host-based intrusion detection systems (HIDS) and network intrusion detection systems (NIDS) to an SIEM and building rules to alert when suspicious activity is seen. According to the defense in-depth approach, we should be auditing and placing detection triggers on multiple layers of the technology stack, from looking at cloud audit logs (like Cloudtrail), the Kubernetes cluster, containers, application code, host OS and the kernel. We will take a look at the detective measures in this blog which will further help us to respond to these threats. Image credit: @leodido Setting Falco up on Kubernetes The most secure way to run Falco is to install Falco directly on the host system so that Falco is isolated from Kubernetes in the case of compromise. Then the Falco alerts can be consumed via read-only agents running in Kubernetes. Falco can also be run directly in Kubernetes if isolation is not a concern. We will be setting Falco up using Helm in this tutorial, but you should be aware of the pros and cons of the method you are choosing. Prerequisite: We need a working Kubernetes setup for this. You can use a cloud Kubernetes offering from AWS/GCP or set one up yourself locally using . We also require kubectl and to be installed on your client machine. Steps minikube Helm Let’s start with the installation of Falco. 1. Add the falcosecurity repo in Helm $ helm repo add falcosecurity https: $ helm repo update
Hang tight we grab the latest your chart repositories...
...Successfully got an update the chart repository
...Successfully got an update the chart repository
Update Complete. ⎈Happy Helming!⎈ //falcosecurity.github.io/charts while from from "falcosecurity" from "stable" 2. Installing the chart $ helm install falco falcosecurity/falco
NAME: falco
LAST DEPLOYED: Mon Nov : : NAMESPACE: STATUS: deployed
REVISION: TEST SUITE: None
NOTES:
Falco agents are spinning up on each node your cluster. After a few
seconds, they are going to start monitoring your containers looking security issues.
No further action should be required. 9 22 09 28 2020 default 1 in for 3. After a few seconds Falco should be running, to verify, you will see the pods you created in a moment. $ helm ls
$ kubectl get pods Setting up the environment We will need an environment to emulate the attacks and detect them. Let us set it up. We will be using Helm for this. Let’s add Helm’s stable repository and install chart from it. mysql-db $ helm repo add stable https: $ helm repo update
Hang tight we grab the latest your chart repositories...
...Successfully got an update the chart repository
...Successfully got an update the chart repository
Update Complete. ⎈Happy Helming!⎈ //charts.helm.sh/stable while from from "falcosecurity" from "stable" $ helm install mysql-db stable/mysql
NAME: mysql-db
LAST DEPLOYED: Mon Nov : : NAMESPACE: STATUS: deployed
REVISION: NOTES:
MySQL can be accessed via port on the following DNS name within your cluster:
mysql-db.default.svc.cluster.local
... 9 22 11 07 2020 default 1 3306 from Let us now monitor Falco logs: $ kubectl get pods
NAME                      READY  STATUS   RESTARTS  AGE
falco rr9r / Running m
mysql-db-d5dc6b85d hrm / Running m
ubuntu / Running m

$ kubectl logs -f falco rr9r # Replace your Falco pod name here -6 1 1 0 49 -77 1 1 0 47 1 1 0 43 -6 with Analyzing Falco’s logs The first steps when an attacker does after they gain access to a Kubernetes cluster is to enumerate available network hosts. An attacker will try to find their way around a seemingly new environment. They can try to use safe/less noisy commands to gain more insights from the cluster. Let us go through the steps an attacker might do and look at the corresponding detection signals from Falco. We will use the default ruleset which comes with Falco, these rules can be tuned as per your needs in your environment. You can find Falco’s default rules here: https://github.com/falcosecurity/falco/tree/master/rules Terminal shell in container Description: Detecting terminal shells being spawned in pods. We open a terminal shell on a running pod to replicate the scenario. $ kubectl exec -it mysql-db-d5dc6b85d hrm -- bash -il # Replace the mysql pod name you have -77 with Detection: : : : Notice A shell was spawned a container an attached terminal (user=root user_loginuid= k8s.ns= k8s.pod=mysql-db-d5dc6b85d hrm container= fc8155f9d1a shell=bash parent=runc cmdline=bash -il terminal= container_id= fc8155f9d1a image=mysql) k8s.ns= k8s.pod=mysql-db-d5dc6b85d hrm container= fc8155f9d1a 18 08 40.584075795 in with -1 default -77 3 34816 3 default -77 3 Contact Kubernetes API Server From Container Description: We run kube-recon, which is a tool which does initial reconnaissance in a Kubernetes environment. This rule detects attempts to contact the Kubernetes API Server from a container. $ kubectl run kuberecon --tty -i --image octarinesec/kube-recon
/ # ./kube-recon / / : : Testing K8S API permissions / / : : Your K8S API Server is configured properly / / : : Running Nmap on the discovered IPs / / : : Getting local ip address and subnet / / : : Trying to download EICAR file / / : : Downloaded EICAR successfully. No malware protection is place 2020 11 09 18 21 22 2020 11 09 18 21 23 2020 11 09 18 21 23 2020 11 09 18 21 23 2020 11 09 18 21 23 2020 11 09 18 21 23 in Detection: : : : Notice A shell was spawned a container an attached terminal (user=root user_loginuid= k8s.ns= <NA> container=4f63870599d0 shell=sh parent=<NA> cmdline=sh terminal=34816 container_id=4f63870599d0 image=octarinesec/kube-recon) k8s.ns=<NA> k8s.pod=<NA> container=4f63870599d0
18:21:22.657590195: Warning Docker or kubernetes client executed in container (user=root user_loginuid=-1 k8s.ns=default k8s.pod=kuberecon container=4f63870599d0 parent=kube-recon cmdline=kubectl get pods image=octarinesec/kube-recon:latest) k8s.ns=default k8s.pod=kuberecon container=4f63870599d0
18:21:22.723707794: Notice Unexpected connection to K8s API Server from container (command=kubectl get pods k8s.ns=default k8s.pod=kuberecon container=4f63870599d0 image=octarinesec/kube-recon:latest connection=172.17.0.5:56972->10.96.0.1:443) k8s.ns=default k8s.pod=kuberecon container=4f63870599d0 18 20 45.927730981 in with -1 k8s.pod= < > NA Checking if shell is a container environment (Change thread namespace) Description: amicontained is a tool to check whether the shell is a containerized environment. The rule detects an attempt to change a program/thread’s namespace. $ cd /tmp; curl -L -o amicontained https: Output: 
Container Runtime: docker
Has Namespaces:
  pid: user: AppArmor Profile: kernel
Capabilities:
  BOUNDING -> chown dac_override fowner fsetid kill setgid setuid setpcap net_bind_service net_raw sys_chroot mknod audit_write setfcap
Seccomp: disabled    
Blocked Syscalls ( ):
  MSGRCV SYSLOG SETSID VHANGUP PIVOT_ROOT ACCT SETTIMEOFDAY UMOUNT2 SWAPON SWAPOFF REBOOT SETHOSTNAME SETDOMAINNAME INIT_MODULE DELETE_MODULE LOOKUP_DCOOKIE KEXEC_LOAD OPEN_BY_HANDLE_AT FINIT_MODULE //github.com/genuinetools/amicontained/releases/download/v0.4.7/amicontained-linux-amd64; chmod 555 amicontained; ./amicontained true false 19 Detection: : : : Notice Namespace change (setns) by unexpected program (user=root user_loginuid= command=amicontained parent=bash k8s.ns= k8s.pod=kuberecon container=c6112967b4f2 container_id=c6112967b4f2 image=octarinesec/kube-recon:latest) k8s.ns= k8s.pod=kuberecon container=c6112967b4f2
Mon Nov : : : Falco internal: syscall event drop. system calls dropped last second. : : : Critical Falco internal: syscall event drop. system calls dropped last second. (ebpf_enabled= n_drops= n_drops_buffer= n_drops_bug= n_drops_pf= n_evts= ) 18 43 37.288344192 -1 default default 9 18 43 37 2020 9 in 18 43 37.970973376 9 in 0 9 0 0 9 15232 Next steps In this tutorial, we looked at the basics of Kubernetes security monitoring and how Falco allows us to use rules to achieve the detection of security issues. The default detection ruleset of Falco is enough to get yourself up and running, but you will most likely need to build on top of the default ruleset. We will explore building and tuning these rules in the upcoming posts on security. That’s a wrap folks! Do share your thoughts in the comment section below. Previously published at https://www.infracloud.io/blogs/introduction-kubernetes-security-falco/

Kubernetes Security 101: Cloud Native Runtime Security with Falco

How do you develop apps in Kubernetes? Kubernetes is great for operations but ideally speaking, it’s not something developers should concern themselves with. In reality, apps developed for Kubernetes are different because they interact with other services and could be stateful, both of which are tough to replicate in a local setup. Developers are used to the luxury of hot reloading and debugging to quickly test and improve the app. When it comes to developing apps for Kubernetes, the developer needs to build and push the container image to the registry and then update Kubernetes pod. After all the time consuming tasks, developers still can’t hot-reload and debug their apps directly. Over the time, there have been tools which help fasten the process of building the container image, automate the process of pushing to the registry and update Kubernetes with the change. While these tools can be a great addition, they’re quite inadequate from a developer’s perspective. What is Telepresence? Telepresence is a lightweight development tool that can help you to debug and develop apps deployed to Kubernetes seamlessly. Basically, you could have a process running on your local system (without necessarily having to build containers) and telepresence will proxy all the requests back and forth from the cluster to that process. How does it do it? It replaces your existing deployments with it’s own pod which runs a reverse-proxy that connects with our local system to forward and receive requests. This makes it possible for an app running locally to talk to other services which are running inside the Kubernetes cluster. You can find instructions on how to install it . here Demo! Initially, there’s an existing deployment in the cluster which is running an API which returns “Hello World”. In this demo, I am going to replace the “Hello World” API deployed to Kubernetes with a process running locally that interacts with Kubernetes API to list the pods across namespaces with just one Telepresence command. Although I have interacted with Kubernetes API in this example, you could essentially interact with just about any other service. As you can see, following the can be the command to run just about any binary on your local system which would run in context of Kubernetes, at least networking wise. In the demo, I had run the Uvicorn server. –run Hopefully, this demonstrates how simple it can be to develop apps that need to interact with existing services deployed in Kubernetes. There might be times where you might want to forward requests to a container running locally, you can do that too with instead of . Debugging and hot reloading apps in local containers can be done by . You can also find language-specific extensions, here’s for Go. –docker-run –run VS Code’s Remote Development extension one You can find the code used in the above demo . here This looks too good, what’s the catch? There are a couple of limitations as of now : Currently, it can only swap Deployments. Work is being done to swap pods which would make it possible to replace any Kubernetes object that’s controlling pods (DaemonSets, Jobs, etc). Telepresence solves the issues of volumes too, but it’s not so elegant. In the best case, it requires to setup mock data on your local system which might not always be possible. Other tools that are worth a mention: The following tools provide a way for in-cluster development which syncs with your local files. By going where the app resides, this solves both networking and storage issues for development. : This is an absolutely amazing project but only the enterprise version lets you connect with your Kubernetes cluster. Otherwise, you’re limited to a small instance on their cloud. Okteto : Devspace allows you to connect with your own Kubernetes cluster. In most cases, both of these projects may require a bit of configuration to be written but that’s a one time effort which might be worth it. Devspace Conclusion Telepresence is a network proxy that connects with your local system to help develop apps in Kubernetes. A lot of projects are emerging in the space of development tools for Kubernetes. Telepresence is definitely on top of my list since it requires no configuration and simple to use. Please, drop a comment below to let us know which tools you have used and what you liked/disliked about them. Previously published at h ttps://www.infracloud.io/blogs/develop-your-kubernetes-apps-locally-telepresence/

Stories, News & Mentions about INFRACLOUDTECHNOLOGIES

Infracloudtechnologies’s Stories on HackerNoon

Stories, News & Mentions about INFRACLOUDTECHNOLOGIES $infracloudtechnologies logo$