OpenShift extends Kubernetes by introducing additional resources and abstractions to simplify application development and deployment. Let's analyze each option:
A . routes
Correct:
Routes are unique to OpenShift and provide a way to expose services externally by mapping a hostname to a service. They are built on top of Kubernetes Ingress but offer additional features like TLS termination and wildcard support.
B . build
Correct:
Builds are unique to OpenShift and represent the process of transforming source code into container images. OpenShift provides build configurations and strategies (e.g., Docker, S2I) to automate this process, which is not natively available in Kubernetes.
C . ingress
Incorrect:
Ingress is a standard Kubernetes resource used to manage external access to services. While OpenShift uses Ingress as the foundation for its Routes, Ingress itself is not unique to OpenShift.
D . services
Incorrect:
Services are a core Kubernetes resource used to expose applications internally within the cluster. They are not unique to OpenShift.
Why These Resources?
Routes: Extend Kubernetes Ingress to provide advanced external access capabilities, such as custom domain mappings and TLS termination.
Builds: Simplify the process of building container images directly within the OpenShift platform, enabling streamlined CI/CD workflows.
JNCIA Cloud Reference:
The JNCIA-Cloud certification covers OpenShift's unique resources as part of its curriculum on container orchestration platforms. Understanding the differences between OpenShift and Kubernetes resources is essential for leveraging OpenShift's full capabilities.
For example, Juniper Contrail integrates with OpenShift to provide advanced networking features, ensuring secure and efficient traffic routing for Routes and Builds.
Reference:
OpenShift Documentation: Routes and Builds
Juniper JNCIA-Cloud Study Guide: OpenShift vs. Kubernetes