Merge pull request #49965 from nate-double-u/update-nokia-logo

update Nokia logo in case-studies

Author: k8s-ci-robot

content/en/case-studies/nokia/index.html

@@ -6,8 +6,8 @@
 logo: nokia_featured_logo.png
 
 new_case_study_styles: true
-heading_background: /images/case-studies/nokia/banner1.jpg
-heading_title_logo: /images/nokia_logo.png
+heading_background: /images/case-studies/nokia/banner3.jpg
+heading_title_logo: /images/nokia-white-on-transparent.png
 subheading: >
   Nokia: Enabling 5G and DevOps at a Telecom Company with Kubernetes
 case_study_details:
@@ -41,7 +41,6 @@ <h2>Impact</h2>
 <p>Looking for a way to allow its teams to build products with infrastructure-agnostic behavior, the company decided to embrace containerization, Kubernetes, and other cloud native technologies, a move that is being made across the telecom industry. Since early 2018, "when people are picking up their phones and making a call on Nokia networks, they are creating containers in the background with Kubernetes," says Csatari. "Now, all the products are doing some kind of re-architecture work, and they're moving to Kubernetes."</p>
 
 {{< case-studies/quote
-  image="/images/case-studies/nokia/banner3.jpg"
   author="Gergely Csatari, Senior Open Source Engineer, Nokia"
 >}}
 "Having the community and CNCF around Kubernetes is not only important for having a connection to other companies who are using Kubernetes and a forum where you can ask or discuss features of Kubernetes. But as a company who would like to contribute to Kubernetes, it was very important to have a CLA (Contributors License Agreement) which is connected to the CNCF and not to a particular company. That was a critical step for us to start contributing to Kubernetes and Helm."
@@ -54,7 +53,6 @@ <h2>Impact</h2>
 <p>That meant that they needed to be able to set affinity and anti-affinity rules in their orchestration tools. "You cannot put all of the functions to the same physical host because physical hosts are failing," Csatari explains. "If you fail with one physical host, then you lose all of the core processing processes. Then there are no calls going through. So we have to divide them among the different physical hosts. At that time, only Kubernetes was able to provide these features. The simplicity of the label-based scheduling of Kubernetes was a sign that showed us this architecture will scale, will be stable, and will be good for our purposes."</p>
 
 {{< case-studies/quote 
-  image="/images/case-studies/nokia/banner4.jpg"
   author="Gergely Csatari, Senior Open Source Engineer, Nokia"
 >}}
 "Kubernetes opened the window to all of these open source projects instead of implementing everything in house. Our engineers can focus more on the application level, which is actually the thing what we are selling, and not on the infrastructure level. For us, the most important thing about Kubernetes is it allows us to focus on value creation of our business."